Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

And the team lead with 7 developers isn’t going to be doing code reviews of all the code. At most he is going to be reviewing those critical paths.

I could care less about the implementation behind the vibe coded admin website that will only be used by a dozen people. I care about the authorization.

Even the ETL job, I cared only about the performance characteristics, the resulting correctness, concurrency, logging, and correctness of the results.

 help



>And the team lead with 7 developers isn’t going to be doing code reviews of all the code. At most he is going to be reviewing those critical paths.

Why would the team lead need to review all 7 developers? If you're regularly swapping out every single developer on a team, you're gonna have problems.

>I could care less about the implementation behind the vibe coded admin website that will only be used by a dozen people. I care about the authorization.

If you only have 12 users sure do whatever you want. If you don't have users nothing is hard.


It was 12 users who monitored and managed the ETL job. If I had 1 million users what difference would the front end code have made if the backend architecture was secure, scalable, etc. if the login is taking 2 minutes. I can guarantee you it’s not because the developer failed to write SOLID code…

There you go arguing with strawmen again. I don’t give a single flying flip about SOLID, or Clean Code, or GoF. People who read Clean Code as their first programming but and made that their identity have been the bane of my existence as a programmer.

It’s not about how long something is taking although that is an observable behavior. It’s about how 1 million users over time will develop ways of using your product that you never thought about, much less documented or tested.

Perhaps you’ve heard the phrase “The purpose of the system is what it does”?

The system is the not the spec or the tests. An agent is only reasoning about how to add a new feature, and the only thing preventing from changing observable behavior is the tests. So if an agent is changing untested behavior it’s changing the purpose of the system.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: