For me, it's my diet and workout buddy. It knows my goals, keeps me on track, does meal planning for me, gives me grocery lists, logs what I eat, when I exercise... anything I want so I don't slack off.
I've enhanced Nanoclaw quite a bit. Moved it to Apple containers (shipped with this Skill already). Then I wrote an API for Nanoclaw to use (food log, workouts, etc), then implemented long-term memory using LanceDB (because I was tired of repeating myself!).
Essentially, there are two parallel teams, one is seen constantly huddling together, working late, fixing their (broken) service. The other team is quiet, leaves on time, their service never has serious issues. Which do you think looks better from the outside?
Adding to this: it's not just that the apprenticeship ladder is gone—it's that nobody wants to deal with juniors who spit out AI code they don't really understand.
In the past, a junior would write bad code and you'd work with them to make it better. Now I just assume they're taking my feedback and feeding it right back to the LLM. Ends up taking more of my time than if I'd done it myself. The whole mentorship thing breaks down when you're basically collaborating with a model through a proxy.
I think highly motivated juniors who actually want to learn are still valuable. But it's hard to get past "why bother mentoring when I could just use AI directly?"
I don't have answers here. Just thinking maybe we're not seeing the end of software engineering for those of us already in it—but the door might be closing for anyone trying to come up behind us.
I know this is besides the point but translation libraries are perfect for this even if you aren't creating a multilingual site. You define your singular/plural forms in one place.
I hung onto a Blackberry way longer than I should have simply because I wanted physical keys. I'm trying to hang onto cars with physical controls as well. It seems like automakers are finally get the hint that people want physical controls again.
Great analysis - though I can't help but notice that 2009 is right when smartphones really took off (iPhone in 2007, Android in 2008, then mass adoption). The data showing accidents getting more deadly rather than more frequent actually makes sense if you combine two factors: phones causing more distracted driving incidents, plus our bigger American vehicles turning what would be injuries elsewhere into deaths. That could explain why it's US-specific - other countries probably have the same phone distraction problem, but their smaller cars mean less fatal outcomes. The distraction data might be weak simply because people don't admit they were on their phone after killing someone, but sometimes the obvious answer deserves more weight than we give it.
Completely agree. Nuxt is intuitive - convention-over-configuration and auto-imports remove a ton of boilerplate. The key is treating it as an app framework, not a backend solution - within that scope, it handles modern SSR/SPA complexity.
Then Claude came for the designers with Claude Design, and I did not speak out— Because I was not a designer.
...