Jake Worth 🌲

@jakeworth.com

That software engineer you know in Maine. I share daily learnings, essays about programming, and New England tech events. Organizer of MaineJS. https://www.jakeworth.com

I’m thinking about a weekly newsletter for SaaS CTOs (teams ~10–100 engineers): “3 tech trends you should care about (and what to do about them)” Format: - Act on this - Watch this - Ignore this Would you read that? If yes, reply or like this post, and I’ll send a first issue to a small group.

I used to be like: "I'm a Rails dev, so my blog *has* to be a Rails app!" Nowadays, I'd pick whatever is the absolute easiest tool for me to write, edit, and deploy.

This week, we ran an experiment: entire team voting on tickets to be included in an upcoming release! It was interesting. Has anyone done this? What would you call it; participatory software planning?

Testing a feature or bugfix, make sure you aren’t trying to "catch it passing." Okay: "Can I get it to work?" Better: "Does it ever fail, even if I stray from the happy path?"

"Being fast" matters at the org level, too. Fast organizations fix little things. They experiment instead of talking. They deploy fearlessly because they know they can recover quickly from mistakes.