Reposted by Daniel Fosco
advice for junior developers:
you are no longer a developer
you are a builder
you are a solution provider
enter every room and make things happen
learn when no one is watching
create because you can
fix problems because they offend you
bend the world to your will
and take credit
![Marc Brooker is a Distinguished Engineer at AWS, works on AWS S3, and is known for having high standards in software engineering. He has written this about the future of code reviews (emphasis mine):
“There’s been a ton of talk about the role of humans in code review, and when and how humans should be signing off on changes.
I believe that, long-term, humans have no role in routinely reviewing code.
Short-term, many teams do it for good reasons. Quality. Understanding. Compliance. Those reasons exist, but we should be (and are) working on ways to make them go away.
The “mixed mode” where humans look at some code reviews, assisted by review tools, is also valuable today. But probably even more transient.
The idea that humans will reliably look through code to find the increasingly rare issues that automated tools miss seems like a fantasy.
What does the future [without code reviews] look like?
Review tools, powered by LLMaaJ-style techniques, static analysis, and automated reasoning methods. Principled approaches to testing and validation (PBT, DST, model-guided fuzzing, etc). Correct-by-construction techniques.
The combination of these things will lead to (and in many cases already lead to) better outcomes than traditional code review, both for large and small issues. Soon, much better outcomes than code review.
The days of Code review as a tool for increasing software quality appeared numbered, and the end may already be here (but unevenly distributed).](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:ctphcgyhnllfluywokibtrgb/bafkreiexqaz44a6lhqkf4tdor7sze6lcr3usfktajowjlczfmfpob6wsg4)
![Screenshot of a writing-analysis tool showing paragraphs of text with phrases highlighted in two shades of yellow, brown circular "3" badges, and a black tooltip overlaying the first line reading: "No X, no Y" chains · 3 "no" items. The visible text reads: We r[obscured by tooltip]nd up. No sign-ups, no downloads, no hassle (3) — just paste your text and start writing. Everything runs locally in your browser. The reviewer read the draft twice. Did not flinch, did not blink, did not reach for the red pen (3). That's the whole review, honestly. Don't call it a rewrite — call it a rescue. The improvement is real, and it's not subtle. That loss is worth naming. Sit with that for a moment. The gains were modest, but that's not nothing. You already know the answer, of course. Consistency is the entire game, and the punchline is that nobody wants to hear it. The entire pitch is one sentence long.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:kft6lu4trxowqmter2b6vg6z/bafkreieoph5j4vedatyill3ezdtxcq4bjlyvtrxnwvf6ngghts2tfrqvqa)
![Profile for Ben Collins (bencollins.bsky.social) showing a redacted post with profile photo. The visible text reads: "I'm [redacted] a wet fart [redacted] and [redacted] have an [redacted] amount of money, so [redacted] Be careful out there!" White rectangular redaction blocks cover selected words throughout. Bottom shows "see the source post" link and "30 of 45 redacted" indicator. This is an example of Post Redaction Poetry, a creative engagement feature on anisota.net.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:gq4fo3u6tqzzdkjlwzpb23tj/bafkreifejb6ihr65bofiqahpn4lcg2kmcoeodas4newy5hk6glmm2vf5gq)
