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.

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.

I think he basically did this too.

Interesting discovery:

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

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

Mea cupla. Fixed.

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

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 :-)

It's not designed to go in your Gemfile

gem install mailcatcher

:-)

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.

Somebody already has, for perforce:

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

alias rm="rm -v" helps.

Cost/benefit.

There are always going to be security holes in anything we make. We can be a bank and focus two feet ahead on making sure everything is as secure as possible, or stay aware of security (and not do anything stupid) while moving fast enough that any flaws are irrelevant/fixed when exposed.

It also highly depends on how much risk you're willing to accept. For the average rails app, absolute security is not as important as moving fast. Be an adult and make adult decisions about your tools and processes to suit your circumstances.

This was my first thought, and seems likely. They do several forms of analysis on their cache. It could even be some engineers running tests or queries that require rendering the page or at least bootstrapping the DOM.

Agreed, although apparently this has been tried a few times without success. Do it next year!

Entirely home–grown CSS with transitions via Sass/Compass by the ever–wonderful http://levibuzolic.com/.

We used Slim for findthin.gs—it's faster, has much better whitespace control, and, imho, better achieves Haml's reduce noise, increase beauty aims. But there's no contest about Sass and CoffeeScript being amazing.

This reminds me waaaay too much of ASP.NET's oh-so-wonderful __VIEWSTATE.

I was just about to go an do this. Has anyone else yet?

So could most of us, but then again you could do something interesting with your weekend instead.