
pd
3.5K posts




You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.




I like types. Types align with my brain waves; they help me create better code. TS/Rust are my tools of choice. When using agents, though, that doesn’t matter as much. I asked OpenCode to build me a simple CRM recently using Ruby on Rails. It came back INSANELY GOOD. One prompt, 15 minutes, database migrations, form validations, authentication, a nice backend structure - the works! Ruby and Rails have been around forever. That makes a huge difference for agents. The older and more proven the tech, the better the result you get from the agent. That is also why Linux has suddenly become such a joy to use.























