Earlier quoted context omitted.
Like becoming a manager? When a person becomes a manager, they do or do not have enough time and expertise to review all of the code that they trust the team to produce. Managers usually get into automated testing; unit tests, integration tests, acceptance tests, and maybe also BDD syntax Managers and developers are responsible for setting a test coverage threshold for merge approval. If there is 100% branch coverage…
> How does the value of LLM-produced 100% branch coverage compare to no-LLM 100% branch coverage? This is such a salient question. Sometimes (definitely not always) the test suites produced by LLMs are so trivial it's scary. Coverage can be an illusion for sure.
The LLM Critics Are Right. I Use LLMs Anyway
171–180 of 330 posts
Re: The LLM Critics Are Right. I Use LLMs Anyway
#172Earlier quoted context omitted.
Like becoming a manager? When a person becomes a manager, they do or do not have enough time and expertise to review all of the code that they trust the team to produce. Managers usually get into automated testing; unit tests, integration tests, acceptance tests, and maybe also BDD syntax Managers and developers are responsible for setting a test coverage threshold for merge approval. If there is 100% branch coverage…
> When a person becomes a manager, they do or do not have enough time and expertise to review all of the code that they trust the team to produce. > Managers usually get into automated testing; unit tests, integration tests, acceptance tests, and maybe also BDD syntax I can see managers getting involved into acceptance tests, but never in the other type of tests. And the verification mostly is involved into a quick m…
And then sometimes you report a memory leak and it gets fixed by a VP and you wonder if he doesn't have something better to do.
Re: The LLM Critics Are Right. I Use LLMs Anyway
#173> LLM’s amplify what you already have: opinions, structure, frameworks. So far, so agreeable, but… > If you have thoughts, they come out sharper and faster. I can’t help but wonder whether constant use of “agent” harnesses will lead to an atrophy of the software engineering (or really any field) muscles. Actual muscles need exercise to stay in shape (let alone grow), so does the brain. Can we really be sure that thou…
Re: The LLM Critics Are Right. I Use LLMs Anyway
#174> I am a little bit scared to say this too: last month I spent almost 10k USD on tokens. It sounds so insane. What are people actually doing with all these tokens? I use LLMs pretty heavily for development, and I'm rarely spending all the tokens that come with a $10/month OpenCode Go subscription...
Re: The LLM Critics Are Right. I Use LLMs Anyway
#175This is because.. sometimes an idea is just bad. I learned the hard way the other day when I filed this PR against prek: https://github.com/j178/prek/pull/2302
My idea was bad.
The implementation was meant to solve my problem. All it did was expose more problems and waste my time and the maintainer's, and god knows how many tokens from Claude and Codex. In the end the PR was useless so I closed it.
The maintainer and I would have both been better off - less time wasted - if I was forced to forever wonder if the idea was good, letting it bounce around the back of my mind.
Re: The LLM Critics Are Right. I Use LLMs Anyway
#176Earlier quoted context omitted.
I think the real disaster is that once you let the LLM work on a project for a bit, you start to lose understanding of what exactly is even happening under the hood in the project. You can take steps to mitigate this, but agents don't exactly encourage the behavior required to maintain a good understanding of what's going on.
Like becoming a manager? When a person becomes a manager, they do or do not have enough time and expertise to review all of the code that they trust the team to produce. Managers usually get into automated testing; unit tests, integration tests, acceptance tests, and maybe also BDD syntax Managers and developers are responsible for setting a test coverage threshold for merge approval. If there is 100% branch coverage…
Re: The LLM Critics Are Right. I Use LLMs Anyway
#177LLMs are awesome, but sometimes we'd be better off with more friction. This is because.. sometimes an idea is just bad. I learned the hard way the other day when I filed this PR against prek: https://github.com/j178/prek/pull/2302 My idea was bad. The implementation was meant to solve my problem. All it did was expose more problems and waste my time and the maintainer's, and god knows how many tokens from Claude and…
Re: The LLM Critics Are Right. I Use LLMs Anyway
#178Earlier quoted context omitted.
I am both a career developer and experienced team manager. from first hand experience the 1.5x im getting from AI is not flowing down to my team / org because why would i output 50% more when the pay environment and leadership are already underwhelming. That additional 50% productivity goes completely to side projects built on my second computer between 9-5 tasks
Great point. Devs have relatively no incentive to be more productive for their orgs, and all the incentive to be more productive on their own personal work. The AI benefit to devs is real, just not for large enterprises IMO outside of automating clerical/mundane work.
Re: The LLM Critics Are Right. I Use LLMs Anyway
#179Earlier quoted context omitted.
> Conversely, I also am a user of LLMs (true shocker these days, I know), and am noticing a speedup in areas I was already familiar with, and a quicker introduction to new ones. The obvious benefit cannot be denied, and doing so regardless makes you look uninformed. [Excluding people who don’t want anything to do with LLMs out of moral principle, which curiously just like the overarching topic I also both respect and…
I won't be as diplomatic as the other reponse to you. You are welcome to your reticence to agentic coding. But as you're no doubt observing, all your peers are saying they're moving ahead leaps and bounds. Either all of them are wrong, or you will be left behind. Whatever the outcome, it will be on you, and you may make your peace with that.
I really appreciate your comment, I think I've discovered part of why I've never felt any anxiety over being replaced by an LLM. I've never tried or wanted to emit low quality code at high velocity, my standards and goals have always listed quality first. Feels more like asking a chef if they're afraid of llms. Why would they be, they're not doing the same thing.
Re: The LLM Critics Are Right. I Use LLMs Anyway
#180Earlier quoted context omitted.
Like becoming a manager? When a person becomes a manager, they do or do not have enough time and expertise to review all of the code that they trust the team to produce. Managers usually get into automated testing; unit tests, integration tests, acceptance tests, and maybe also BDD syntax Managers and developers are responsible for setting a test coverage threshold for merge approval. If there is 100% branch coverage…
Formal verification is always more valuable than mere testing, but it's hitherto more expensive. The thing that ultimately matters is closing the loop: how well do the tests match the requirements, both as written and as unwritten in the mind of the customer? Working with an LLM has given me a real eye opener on unwritten requirements. It's like outsourcing. "Yes, you've given me what I wrote down, but I never expect…