datsci_est_2015 6 hours ago

You don’t sound very senior.

Code review isn’t a quality gate, it’s a way to maintain shared understanding of a codebase.

Throwing out code review is equivalent to throwing your hands up and saying you don’t need to understand anything about what your code is doing in its black box.

I don’t think anyone on this forum is half as smart as they think they are, especially in terms of systems engineering a black box solution. Myself included. Someone needs to understand what’s going on inside the Widget Factory until we have full Artificial General Intelligence.

▲

Hamuko 5 hours ago | parent [-]

>Throwing out code review is equivalent to throwing your hands up and saying you don’t need to understand anything about what your code is doing in its black box.

I think that is what the C-suite is currently wanting out of our engineers. Prompt, don't write, maybe read a bit, don't stop, ship, ship, ship.

▲

curt15 3 hours ago | parent | next [-]

Is the C-suite ready to sack the engineers and prompt Claude themselves with their business requirements? Why not cut out the middlemen if that's how they now perceive engineers?

	▲	datsci_est_2015 11 minutes ago \| parent [-]
		If they can do that, why doesn’t someone else do it first, for half as much money? What’s their moat if their business can be replicated with a few prompts?

▲

Terr_ 5 hours ago | parent | prev [-]

This will vary by company focus and size, but sometimes the C-suite just doesn't want to believe that software-engineering has important overlap with business-analysis or product-design.