Re:Bad ideas that aren't bad anymore
by motbus3 on Thursday November 12, 2026 @05:30AM
(#50465360)
Totally agree.
We decided that we know the system well enough that we can self approve PRs
I would say people might have slightly different opinions I. The company, but in general, if it is not critical and it can go to preprod to check, we can merge.
I particularly do an automated code review and use some setup to check idea, code and documentation. But if it is critical or too important to go wrong I seek for code reviews.
The cost of writing code has gone down but not the cost for engineering.
I see my friends struggling with vibe coded projects because they didnt plan how to grow the baseline.
The line got blurred as it became cheaper to do-redo but you can check any vibe-coder code cost through time and it does increase at least linearly.
I will say that now it is easier to plan specific changes that can put in and out in case of problems whether before we would need to do several rollout steps so multiple people could work on a task.
Now several people work on several things and the struggles are others.
Code quality has been a pain for everyone.
I think for an LLM doing things one way or the other is a matter of what fitted the chances by the prompt and not good practices or choices. By this I mean, if there are two ways of writing the same code and one is clearly harder to read or performs worse, it can be more a matter of being lucky/unlucky to get it right throughout the whole code.
There are weeks I get 30 PRs done, there are weeks I get 3 PRs, like it was before.
But reading LLM code is painful. It is obtuse and without lots of guidance it invent rules to problems that do not exist.
Of course I see that from my bubble, but I guess as experienced engineers are seeing the problems piling up and it the models are getting more expensive and not getting better as faster as before.
These three things can be where we will delimit the usage of LLM for coding.
I particularly like that I don't need to do some of the annoying tasks that took me only checking 48302 files to be sure I got all the same string correct because some past bad decisions. But when I am working in important stuff, the cracks in llm makes me much slower.
A personal challenge has been to keep up knowing the codebase well enough while people (including me) are dumping stuff in there.
We decided that we know the system well enough that we can self approve PRs
I would say people might have slightly different opinions I. The company, but in general, if it is not critical and it can go to preprod to check, we can merge.
I particularly do an automated code review and use some setup to check idea, code and documentation. But if it is critical or too important to go wrong I seek for code reviews.
The cost of writing code has gone down but not the cost for engineering.
I see my friends struggling with vibe coded projects because they didnt plan how to grow the baseline. The line got blurred as it became cheaper to do-redo but you can check any vibe-coder code cost through time and it does increase at least linearly.
I will say that now it is easier to plan specific changes that can put in and out in case of problems whether before we would need to do several rollout steps so multiple people could work on a task.
Now several people work on several things and the struggles are others.
Code quality has been a pain for everyone. I think for an LLM doing things one way or the other is a matter of what fitted the chances by the prompt and not good practices or choices. By this I mean, if there are two ways of writing the same code and one is clearly harder to read or performs worse, it can be more a matter of being lucky/unlucky to get it right throughout the whole code.
There are weeks I get 30 PRs done, there are weeks I get 3 PRs, like it was before. But reading LLM code is painful. It is obtuse and without lots of guidance it invent rules to problems that do not exist.
Of course I see that from my bubble, but I guess as experienced engineers are seeing the problems piling up and it the models are getting more expensive and not getting better as faster as before. These three things can be where we will delimit the usage of LLM for coding.
I particularly like that I don't need to do some of the annoying tasks that took me only checking 48302 files to be sure I got all the same string correct because some past bad decisions. But when I am working in important stuff, the cracks in llm makes me much slower.
A personal challenge has been to keep up knowing the codebase well enough while people (including me) are dumping stuff in there.