#Code-Review
6 notas · última:
The obligation of a software developer
O texto defende que a qualidade do software depende de escolhas técnicas e de postura: buscar a melhor solução, testar o código, saber dizer não, respeitar o time, fazer code review construtivo e mentorar colegas.
How to use AI for coding the right way
O autor defende usar IA como apoio de programação com contexto, prompts, revisão e testes, enquanto mantém atenção para evitar erros, alucinações e uso preguiçoso.
Continuous AI in software engineering
Sean Goedecke argues AI should be used like tests and types, continuously and automatically, not as an on-demand oracle a developer has to remember to consult.
Every Layer of Review Makes You 10x Slower
Avery Pennarun argues AI coding speed doesn't fix engineering velocity because review layers, not typing speed, are the bottleneck, and draws on Deming's quality theory to argue for eliminating review stages, not stacking more of them.
AI Writes Code Faster. Your Job Is Still to Prove It Works.
Osmani's framework for code review after AI: solo devs lean on tests as a safety net, teams need a PR Contract stating intent, proof, risk, and where to focus review.
The Slow and Quiet Cognitive Atrophy of a Modern Software Engineer
AI-generated code looks clean and its own tests pass, but skipping the review step quietly erodes an engineer's own skill. Elmar Chavez traces the decay and argues discipline is what keeps understanding intact.