

Why not do it now?


Why not do it now?
Mmm fair point
I don’t think anyone cares


“Which is bad news for developers”
Nah, we’ve been through lots of iterations of community for developers, irc, maillists, forums, stackoverflow, etc. Most of my complex questions go through specific discord communities now. I’m not trying to spend a year editing a single post because some swamp ass weanie on stackoverflow has his nose covered in rule dust.
Yes ai has changed the game a bit, but it is not removing community, it’s mostly just cutting down on the question duplication
My most recent foray into a new technology was working with vulkan in rust on a mac, stackoverflow is useless compared to the vulkan discord.


Unit tests and good architecture are still foundational requirements, so far no bug reports with any of these updates. In fact a huge chunk of these ai updates were addressing bugs. Not sure why you’re so mad at what you imagine is happening and making so many broad assumptions!


They’re all pretty fired up at the update velocity tbh 🤷


Nah, generative ai is pretty remarkably useful for software development. I’ve written dozens of product updates with tools like claudecode and cursorai, dismissing it as a novelty is reductive and straight up incorrect


Honestly, that’s fine. This may be a wild take, but they grew and their usage of excel obviously didn’t hold them back, what’s the issue?
I use it extensively daily.
It cannot step through code right now, so true debugging is not something you use it for. Most of the time the llm will take the junior engineer approach of “guess and check” unless you explicitly give it better guidance.
My process is generally to start with unit tests and type definitions, then a large multipage prompt for every segment of the app the llm will be tasked with. Then I’ll make a snapshot of the code, give the tool access to the markdown prompt, and validate its work. When there are failures and the project has extensive unit tests it generally follows the same pattern of “I see that this failure should be added to the unit tests” which it does and then re-executes them during iterative development.
If tests are not available or if it is not something directly accessible to the tool then it will generally rely on logs either directly generated or provided by the user.
My role these days is to provide long well thought out prompts, verify the integrity of the code after every commit, and generally just kind of treat the llm as a reckless junior dev. Sometimes junior devs can surprise you, like yesterday I was very surprised by a one shot result: asking for a mobile rn app for taking my rambling voice recordings and summarize them into prompts, it was immediately remarkably successful and now I’ve been walking around mic’d up to generate prompts.