136 karma · joined November 2, 2025
Organizations "born in AI" appear to buck this trend for obvious reasons (no legacy org. to deal with). My two cents.
I'm just not sure his rationale is completely objective given such a structure...
1) Revenue/Route management: re-think the routes with a ruthless focus on sustainable routes with defensible margins.
2) Customer experience and Brand: being an LCC can't come at the expense of customers, i.e., the fare is so cheap we get to treat you like shit.
3) Capital-structure & cost base: you need to right-size the debt, fix liquidity, and ensure you have a durable cost structure (fuel-risk management, etc.)
Again, this was 10-15 years ago. Now with the Ukraine war everyone acts like it is obvious...and I agree, it has been for awhile. We just never had a theater to test this stuff in. I suspect US defense contractors were on-board for Ukraine and Iran to advance development efforts significantly.
About a month later an engineer decided to turn on all warnings for gcc...and behold a message stating something to the effect of "WARNING: execution will halt upon reaching this statement." The compiled code basically just halted and never returned from the function call (can't remember the specifics).
And that is how we learned not to hide compiler messages.
What a TERRIBLE way to store information in an AI era. Diagrams are so...human.
I'm facing increasing pressure from senior executives who think we can avoid the $$$ B2B SaaS by using AI to vibe code a custom solution. I love the idea of experimenting with this but am horrified by the first-ever-case being a production system that is critical to the annual strategic plan. :-/
That said, I've owned them personally for 10+ years, so looking for objective thoughts outside repairability as the article covers.
Random Tuesday thoughts. Neat work!
I was a software and systems developer on cool shit, but I realized I enjoyed solving hard problems more than how I solved them. That led me to a role that is about solving hard problems. Sometimes I still use coding to do it, but that's just one tool of many.
I would love to see Steve consider different command and control structures, and re-consider how work gets done across the development lifecycle. Gas Town's command and control structure read to me like "how a human would think about making software." Even the article admits you need to re-think how you interact in the Gas Town world. It actually may understate this point too much.
Where and how humans interact feels like something that will always be an important consideration, both in a human & AI dominated software development world. At least from where I sit.
I do agree with the security / cautionary comments and wouldn't leverage this setup outside a hacked together homelab.