@thepanta82@_harryjohn@housecor Maybe not forever, but for quite a while. As contexts grow and models become less reliable over long execution chains, I think human review shifts from reviewing code to understanding systems. Less "how", more "why".
@JorisFalter@levelsio@yongfook@dannypostma At 0 MRR, this may actually be an advantage.
You have no legacy product or customer expectations to defend. SaaS isn’t disappearing—the value is moving toward owning painful workflows, distribution, proprietary data, and trust.
Counterpoint here: https://t.co/SQn1gEc8o3
And this is exactly why “SaaS replaced by AI coded software” is not viable for any company that has a an ACTUAL business.
It’s a fun exercise to rebuild ticketing/o11y/feature flags etc… but do you really want to maintain it? Do you want updates, oncall etc to be YOUR problem??
Took a week off thinking whether I should get Claude 20x (up from 5x), 5x + Codex (because of 5.6), or just stick with what I had. Came back and now everyone seems to be setting up Kimi K3. 😅
Is K3 already part of the default coding stack? At least mid-July 2026 one 😉
Naming in software is hard but try to name tech project/startup in 2026 if you need domain, GitHub and everything else… even .dev is busy but .com is on another level 🥲
As a tech lead or eng manager, you so frequently get request from above or from other teams to drop what you are doing and work on this thing they need, *now*.
During my 4 years at Uber after asking these questions, 9 out of 10 times it turned out it wasn't really urgent:
I decided to move my blog from Wordpress to @GoHugoIO so why not building theme from scratch? 😉 I’m gonna regret this as I am not particularly into frontend but so far so good 😁