sj26's comments

On: Taking Buildkite from a side project to a global company

[sj26]

Turning our snowflake infrastructure into an autoscaling fleet via a packer + terraform pipeline was one of my first projects at Buildkite back in 2016:

https://buildkite.com/resources/blog/terraform-techniques-wi...

We still have this pipeline with terraform, but have moved from building packer images for ec2 to building containers for ecs.

On: Taking Buildkite from a side project to a global company

[sj26]

I'm Sam, a founding engineer still at Buildkite. I've been quite vocal that this was short term gains for long term pains. We're in the process of fixing this - we're working on a free tier and a more accessible paid plan for start ups and scale ups. I want to build tools for everyone, not a select few. Stay tuned. In the meantime I would be happy to have pricing conversations where our pricing doesn't make sense: sam@buildkite.com.

On: Taking Buildkite from a side project to a global company

[sj26]

I think he basically did this too.

On: Amazon Aurora DSQL

[sj26]

If anybody likes to play with Ruby on Rails, I've published a bare bones active record connection adapter:

https://github.com/sj26/activerecord-dsql-adapter

[sj26 → sj26]

Interesting discovery:

PG::FeatureNotSupported: ERROR: ddl and dml are not supported in the same transaction

On: MailCatcher runs a super simple SMTP server

[sj26]

Mea cupla. Fixed.

On: MailCatcher runs a super simple SMTP server

[sj26]

Hiya! I'm the maintainer. It's true I don't do much to it these days. But that's because it's complete. There are lots of things I would love to do to improve it. But none of it would dramatically improve what it does. I fix things when they break. But if it ain't broke...

Happy to answer any questions, or be persuaded that something is broken or would be a dramatic improvement :-)

[hk1337 → sj26]

Mailcatcher works great for me. Glad to see you still keep up with bug fixes when needed.

I normally just run it in a docker container configured in docker compose.

I could do without the extra links giving credit in Mailhog, so I will stick with mailcatcher. I know you don't manage Mailhog but that's what will keep me with mailcatcher.

[sj26 → sj26]

I actively endorse https://github.com/mailhog/MailHog if you want something more Go-flavoured or operationalised. But it is also "complete."

On: MailCatcher runs a super simple SMTP server

[sj26]

It's not designed to go in your Gemfile

gem install mailcatcher

:-)

On: Goodbye integers, hello UUIDv7

[sj26]

It Depends(tm).

If you're using a system which is built for distribution, random is great.

When you're leaning on a Postgres database which has powered your startup through scaling but expects right-leaning btree indexes, it's a bad time.

Rearchitecting to use a new data store is ideal, but often impractical as an immediate step. UUIDv7 is a great increment walking that road via sharding etc.

On: How a Jenkins Job Broke our Jenkins UI

[sj26]

Somebody already has, for perforce:

https://github.com/improbable-eng/perforce-buildkite-plugin

[maccard → sj26]

I've looked into this plugin before (we also use perforce). This does techincally let you build from perforce, in the same way making `p4 sync` your first build step does.

On: Ask HN: What's the worst you've ever screwed up at work?

[sj26]

alias rm="rm -v" helps.