91–100 of 102 posts
The main usage of AI for me is to do discovery: if I am working on service A that has a dozen other services as dependencies, then I clone all the repos, point the agent at them, and start to ask questions. I double check ofc. But without the agent I would be back to manual grep code and git logs, asking around, etc… that takes longer and you may miss things
Earlier quoted context omitted.
I had this conversation recently. Not only are search engines and comment threads getting filled with AI responses, but people are increasingly sounding like AI themselves. This makes it even harder to distinguish. Related to code quality, I've noticed developers picking up tricks from AI. Like using feature/xxxxx as the branch name. Last year exactly zero developers used this convention. If any used paths in their b…
I think this comes from Conventional Branching, https://conventionalbranch.org , inspired by conventional commits (e.g. https://www.conventionalcommits.org/en/v1.0.0/ )
But holy heck, I really have to argue with their literal first point. All lowercase, for what reason? It's never explained why they insist on a dated convention instead of proper style.
And in what world is "feat/" abbreviation considered allowable?
I lump this in with advice from people who put their source in a src/ folder instead of Source/.
Right now most of my day is spent thinking about what to build next. If ai is gone, a large chunk will go back to reading and writing code again!
So pretty much the same path but much slower