home.social

#codereview — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #codereview, aggregated by home.social.

fetched live
  1. As AI commoditizes code output, system comprehension can silently decay - creating cognitive debt that threatens safe architectural evolution.

    This #InfoQ article explores why human understanding must be treated as a key architectural characteristic, offering practical strategies and design checkpoints to preserve system intent.

    Read now: bit.ly/4xyUGXI

    #SoftwareArchitecture #EvolutionaryArchitecture #AI #CodeReview #InfoQ

  2. As AI commoditizes code output, system comprehension can silently decay - creating cognitive debt that threatens safe architectural evolution.

    This article explores why human understanding must be treated as a key architectural characteristic, offering practical strategies and design checkpoints to preserve system intent.

    Read now: bit.ly/4xyUGXI

  3. Ever wanted to review your changes like a pull request? 👀

    🌀 **drift** — A TUI for reviewing everything changed from your base branch

    💯 Review committed + uncommitted changes together, inspect code-aware diffs & track files

    🦀 Written in Rust & built with @ratatui_rs

    ⭐ GitHub: github.com/tothalex/drift

  4. Ever wanted to review your changes like a pull request? 👀

    🌀 **drift** — A TUI for reviewing everything changed from your base branch

    💯 Review committed + uncommitted changes together, inspect code-aware diffs & track files

    🦀 Written in Rust & built with @ratatui_rs

    ⭐ GitHub: github.com/tothalex/drift

    #rustlang #ratatui #tui #git #codereview #devtools #opensource

  5. Now that the schedule's been posted, I'm excited to announce that I'll be talking about #CodeReview at this year's @longhorn!

    stevegrunwell.com/speaking/lon

    As a bonus, blind-bird pricing has been extended until August 8, so there's still time to save on your ticket!

  6. Now that the schedule's been posted, I'm excited to announce that I'll be talking about #CodeReview at this year's @longhorn!

    stevegrunwell.com/speaking/lon

    As a bonus, blind-bird pricing has been extended until August 8, so there's still time to save on your ticket!

  7. Ein sehr sehr guter Text über "Code Review", der in Scrum Teams oft eine eigene Spalte auf dem Scrum Board darstellt.
    Oft ein Diskussionsthema in Retrospektiven. Oft fühlt es sich nervig an. Jetzt kommt AI ins Team. Wie kann es helfen? Und warum machen wir das eigentlich alles nochmal?

    newsletter.getdx.com/p/what-ar

    #AgileAI #Scrum #Agile #ScrumMaster #AgileCoach #Retrospektive #CodeReview

  8. Ein sehr sehr guter Text über "Code Review", der in Scrum Teams oft eine eigene Spalte auf dem Scrum Board darstellt.
    Oft ein Diskussionsthema in Retrospektiven. Oft fühlt es sich nervig an. Jetzt kommt AI ins Team. Wie kann es helfen? Und warum machen wir das eigentlich alles nochmal?

    newsletter.getdx.com/p/what-ar

    #AgileAI #Scrum #Agile #ScrumMaster #AgileCoach #Retrospektive #CodeReview

  9. 96% of developers say AI code is not functionally correct. 48% always check it before committing.

    AI now writes 42% of committed code. PR review time grew 91% in teams with heavy AI use. A December 2025 study of 470 PRs found AI code carries 1.7x more issues than human code.

    The bottleneck did not vanish. It moved upstream into review.

    Full breakdown, the four-gate workflow, the capacity planner:
    roamingpigs.com/field-manual/a

    #Programming #CodeReview #SoftwareEngineering

  10. 96% of developers say AI code is not functionally correct. 48% always check it before committing.

    AI now writes 42% of committed code. PR review time grew 91% in teams with heavy AI use. A December 2025 study of 470 PRs found AI code carries 1.7x more issues than human code.

    The bottleneck did not vanish. It moved upstream into review.

    Full breakdown, the four-gate workflow, the capacity planner:
    roamingpigs.com/field-manual/a

    #Programming #CodeReview #SoftwareEngineering

  11. Dropbox just integrated the Model Context Protocol (#MCP) with Dash - its internal knowledge platform, to bring real-time security context into AI code reviews.

    InfoQ sat down with Ishan Misha (Engineering Lead at Dropbox) to unpack the architecture, the role of MCP, and key engineering lessons.

    🔗 Read the interview: bit.ly/4w172X6

    #AI #CodeReview #InfoQ #SoftwareEngineering

  12. Dropbox just integrated the Model Context Protocol (#MCP) with Dash - its internal knowledge platform, to bring real-time security context into AI code reviews.

    InfoQ sat down with Ishan Misha (Engineering Lead at Dropbox) to unpack the architecture, the role of MCP, and key engineering lessons.

    🔗 Read the interview: bit.ly/4w172X6

  13. Wrapping up the work week reading some *human* code, specifically the web server equivalent of Reticulum's NomadNet.

    There are a few things in there that make me twitchy as a reviewer, but there's a consistent "intent" that flows through it that's often lacking in AI code.

    #Reticulum #CodeReview

    NomadNet/nomadnet/Node.py at m...

  14. One of the annoying things when having to review vibe-coded changes, is what I would call "method of the week": A quirk of the currently used LLM model found in a majority of PRs/MRs that vibe-coders don't learn to change before requesting a review despite being told multiple times.

    #LLMs #vibeCoding #codeReview #peerReview #noAI #AI #artificialIntelligence #genAI #generativeAI #amCoding #amProgramming #softwareDevelopment #softwareEngineering

  15. One of the annoying things when having to review vibe-coded changes, is what I would call "method of the week": A quirk of the currently used LLM model found in a majority of PRs/MRs that vibe-coders don't learn to change before requesting a review despite being told multiple times.

    #LLMs #vibeCoding #codeReview #peerReview #noAI #AI #artificialIntelligence #genAI #generativeAI #amCoding #amProgramming #softwareDevelopment #softwareEngineering

  16. AI-generated code looks just as clean as human code in review. That is exactly the problem: review was built to catch reasoning, not syntax. hackernoon.com/your-ai-agents- #codereview

  17. AI-generated code looks just as clean as human code in review. That is exactly the problem: review was built to catch reasoning, not syntax. hackernoon.com/your-ai-agents- #codereview

  18. #fragefur1freund Es ist ja bekannt das bei vielen #Developer #Engineeering spezialisten im Bereich der #Softwareentwicklung die Nutzung von #KI gar nicht so schwarz gesehen wird wie von vielen Influenzern.

    Wenn Ihr nun also eine KI euren #CodeReview machen lassen wollen würdet, wie #claude

    welchen Skill empfehlt Ihr dafür?

  19. Как я автоматизировал превращение вайбкодерского PoC в production-ready MVP

    Как я автоматизировал превращение вайбкодерского PoC в production-ready MVP За несколько часов с помощью AI можно собрать работающий PoC: интерфейс открывается, кнопки нажимаются, основной сценарий проходит. Потом кто-нибудь спрашивает: А это уже можно выкатывать в прод? И тут начинается самое интересное. В проекте обнаруживаются дублирование логики, слабая типизация, почти отсутствующие тесты, случайная архитектура, забытые debug-логи и один файл на несколько тысяч строк, который страшно открывать и ещё страшнее менять. Мне регулярно приходится заниматься именно второй половиной этой работы — превращать быстро собранные прототипы в поддерживаемые MVP. В какой-то момент я понял, что каждый раз повторяю примерно один и тот же инженерный процесс. Так появился Pre2Prod — CLI на базе Codex, который последовательно проверяет репозиторий, составляет план исправлений, выполняет его и независимо перепроверяет результат. Под капотом — один постоянный Reviewer, временные Workers, 41 специализированное ревью и простой цикл: Review → Plan → Implement → Re-review

    habr.com/ru/articles/1061702/

    #AI #agents #openai #vibecoding #codereview #cli #npm #npx #poc #mvp

  20. CW: Loooooooooooong read on the tech identity crisis, AI, and developer careers

    Late-night thoughts... sparked by an engineer on Mastodon asking how, with all the "vibe coders" out there, the demand for actual, competent code reviews is ever going to be met: mastodon.world/@paulschoe/1168

    So I just started writing...

    The end of the tech exception

    For almost thirty years, IT had this sort of "immunity." It was (yeah, was...) the ultimate safe-haven sector. Almost non-stop growth, incredibly comfortable (sometimes even indecent) conditions, and companies always begging for more people than were actually available. Cutthroat, sure, but the kind where you could just hop from gig to gig in Silicon Valley to always land a better deal.

    But we have to look at two things. First, historical instability. The way we absorbed past major crises (oil shocks, the dot-com crash, subprime)... those were mostly economic or geopolitical. They hit the global economy, and tech felt the shockwaves, but never as hard as other sectors like real estate or the auto industry.

    The second point is the current instability. Today, the crisis is homegrown. It’s coming from inside the tech industry itself (whether that’s Fintech, space tech, or even gov tech). Generative AI and agentic tools are changing the very core of how value is produced. (And the money and physical resources are taking a hit because of it, by the way).

    This isn't just an economic dip or a structural pivot. It’s a full-blown identity crisis for a massive, multi-layered profession that honestly thought it was untouchable.

    This existential crisis about an individual's actual usefulness in a sector points back to a really old concept... one theorized by Émile Durkheim in The Division of Labour in Society (he called it anomie) back in the late 1800s during the Industrial Revolution.

    The human need to look ahead

    No drama here, we’re just talking about the need for stability. Not economic stability pushed by some brand-new liberal market, no, but purely personal stability. The ability to see your own future. A human being needs a marked path. Until very recently, a developer’s career path was pretty linear, predictable, and reassuring (with the usual life bumps we all go through). But looking a bit deeper, the sector had these very rigid, schematic rules for the social escalator:

    Learn the syntax and the basics of engineering.

    Practice like crazy (the famous "eating lines of code") to actually become autonomous.

    Move up to Senior, Tech Lead, or Architect roles (for the people who want that).

    Today, the fog comes from the fact that Step 2, the part where you actually build your critical thinking and experience, is at risk of vanishing entirely, replaced by instant code generation. The future is a blur because devs literally don't know what skills to bet on anymore to guarantee they'll still be employable in 5 or 10 years.

    In the end, we're just watching tech go through the exact same loop as other sectors. It’s normalizing. It’s becoming a classic industrial sector: like mining, the auto industry, textiles, canneries, fishing, whatever. A normalization complete with its own automation, the hunt for extreme profitability, and now, this new "Taylorism" settling in.

    #SoftwareEngineering #TechIndustry #FutureOfWork #AgenticCoding #VibeCoding #CodeReview #AI #TechCrisis #SociologyOfWork

  21. AI agents can recreate the old rockstar developer problem: impressive code that only one mind can explain.

    The fix is shared design, local repo rules, small diffs, tests, and review that asks whether the change belongs.

    the-main-thread.com/p/ai-agent

    #AICodingAgents #CodeReview #SoftwareArchitecture