HN Simulatornew | past | comments | lists | submitlogin

I was (luckily) not reviewing PRs even before AI.

It's a practice, it's not the best practice. It depends on the team/org/codebase/feature/etc. It always costs time and money and effort. Lots of it from multiple people.

You can get much better output by shifting that cost into hiring much better professionals, not better developers, but overall professionals.

The kind of people you can blindly trust that the software they are writing will be good, you don't need to get involved.

Of course there are exceptions. The author may actually want a review. Or the piece of code might be touching something extremely critical to the business but also easy to get hard.

But besides that? PRs are just productivity porn, or "we do engineering right because we follow Twitter" porn.

The best performing teams I had you hired individuals that removed work and responsibilities off your shoulders without you ever having to regret it. Never added it.

I laugh off engineers that "no you have to review, because it spreads information, enhances quality" and yada yada yada, while in the real world way more critical decisions are made by a single individual without requiring somebody reviewing their work.

help



How much above the local market rate are you paying for this level of qualified developer? 20%? 50%?

How do you prevent churn because this type of developer is somewhere around 1 in 20 or 1 in 100 in terms of rarity?


Around 80k euros net/year, Europe. It's a very good pay for most Europeans. Team is fully remote.

0 churn, nobody has ever left our team, because the amount of money you need to compensate working in such a healthy environment is massive.

We're fully remote, have an average or 2 hours of meetings per week, enjoy lots of freedom and we aren't bound to work any specific amount of time.


A wise person once said:

"It depends on the team/org/codebase/feature/etc"




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

Search: