that’s a very good distinction, absolutely. its just code generation at this stage.
the review was the bottleneck before (as I believe was already the case for many companies) but now with 10x the code generated for review, the bottleneck has turned into a dripping faucet.
hey shaggy. I want to touch on your last point as a newer developer:
My department is finally seeing 10x development due to the shift of writing code to writing spec. The main issue is now our pipeline is stuck at review, so all that extra output is effectively wasted. Do you have any tips on what worked for you if you had a similar situation?
ITT: people discovering why there are so many branches of Christianity
my repos are NOT going to make their code less sloppy let me tell you
almost like its not about security
I want to read it. Go write it.
Anecdotally, I haven’t run into a single Mikrotik deployment since university.
thanks for the response. for what its worth, most people I ask this question to are attempting some form of your first bulletpoint. I think we’re on the right track there, it only makes sense.
speaking for myself, your second point is the silver lining of all this, to me. ive never had this kind of pressure before, but I hope that its the kind of pressure that makes me a better dev instead of burning me out.
cheers!