1: I know it’s been years in the making, but I’m still slinging Docker containers in a single AWS region.
In other Joel track record exploits, he's also our co-founder over at HASH.ai [1] and a driving force behind the Block Protocol [2][3]
[1] https://www.joelonsoftware.com/2020/06/18/hash-a-free-online... [2] https://blockprotocol.org/ [3] https://www.joelonsoftware.com/2022/01/27/making-the-web-bet...
A long-ranging conversation with Joel on, among other things, confluence of Catholic theology and the Talmud plus the memorable phrase “Shouldn’t you apply your skills to something which isn’t totally bullshit?” caused me to have a sharp reassessment of life and career goals, but for which it is unlikely I would have made a serious go of my consultancy, successfully launched my following few companies, or continued writing at anything like pace observed over the interval.
Those who were there would be better at telling the story, but up until the Atlassian acquisition and Joel deciding to spend most of his time on a collection of other projects[1], my sense of FC was "software for developers." The original product they made for project planning (FogBugz) and its SCM companion (Kiln) continued on for a while, but seemed to have faded as Glitch ramped up.
The other one that comes to mind is Copilot, whose development was chronicled in the Aardvark'd movie - I think Tyler took over the project and is still running it on the side, last I heard.
Kind of bittersweet to see these fade away, but Glitch seems to have had more critical success outside of their traditional user base so they're running with it.
[1]: https://www.joelonsoftware.com/2019/12/05/so-hows-that-retir...
When I interviewed at Fog Creek, they had a DVD copy of Aardvark'd in a care package in my hotel room. I watched it that night, and for my interview day in the morning it felt like everyone I interviewed with was a movie star. Sneaky plan, Joel. Well executed.
It's been kind of wild to see how FogBugz went from their main, almost exclusive priority, to something of barely any significance to the company, and now I'm guessing it's a forgotten product in a subsidiary of a giant CDN. Who knows how long until it's shut down.
It's sad; I still love the whole evidence-based scheduling part of it, and have never seen anything else like it.
Many union contracts also have an explicit "successor clause" too, although I don't know about the Glitch union contract.
[1] https://www.nlrb.gov/about-nlrb/rights-we-protect/the-law/ba...
As they bet the future on wasm-at-the-edge saving them from the crushing downward pressure of bandwidth pricing, having a compelling product for the "entry level"* developer market will be crucial to getting the mind and marketshare needed to hit revenue targets (eventually, not this year).
Put simpler: fastly made itself overly exclusive and difficult to use, glitch is the polar opposite. Fastly's customer base is 45 year old vp's of infra/devops/sre, glitch's is 27 year old app/front-end dev/designers. There's more money in a deal with the former, there's more of the future in the latter.
* I want to be clear, with ~20 years exp when I sit down to figure out a vue front end to my latest flask thingy I'm entry-level af in js/front-end land. Lowering barriers to entry, much like handicap accessibility, is usually a win for everyone.