Mastodon

Marcos Lobo 💙💛Software development is not only about writing code, but about writing GOOD code.<a href="https://newsletter.optimistengineer.com/p/mastering-the-code-review-cycle?r=nw9bj&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false" rel="nofollow noopener" translate="no" target="_blank">https://newsletter.optimistengineer.com/p/mastering-the-code-review-cycle?r=nw9bj&utm_campaign=post&utm_medium=web&showWelcomeOnShare=false</a><a href="https://hachyderm.io/tags/softwareengineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareengineering</a> <a href="https://hachyderm.io/tags/leadership" class="mention hashtag" rel="nofollow noopener" target="_blank">#leadership</a> <a href="https://hachyderm.io/tags/codereview" class="mention hashtag" rel="nofollow noopener" target="_blank">#codereview</a>

minioctt“I reviewed Pirate Software’s Code. Oh boy…” (Coding Jesus vs Pirate Software e la situazione si fa eterna)A quanto pare, il tizio del software pirata, Pirate Software, dopo la sua grande caduta dall’altare da cui predicava non è semplicemente finito sul colpo… bensì, la gente sta scavando. E oooh, se dalla terra stanno uscendo cose… e, in questo caso, incuriosiscono anche me, perché intrecciano due grandi mie passioni: il gaslighting, e lo sviluppo software; nella prima il signorino ha evidentemente appena fallito, mentre sembra che direttamente non sia proprio del mestiere, riguardo la seconda, che nel suo caso è nel campo dei videogiochi… 😰In particolare, il signore è entrato in questioni con un certo Gesù del Coding (e i nomi in questa storia stanno diventando così surreali che davvero inizio a pensare al fatto che, nonostante tutto, viviamo proprio nel migliore dei mondi possibili…), che ha osato fare code review del suo giochino RPG, Heartbound (nome, ancora, scelto veramente a cazzo, visto che sul momento ho pensato fosse il gioco di Nintendo dello stesso genere e probabilmente in parte d’ispirazione, Earthbound; e pronunciati a voce anziché scritti, ovviamente, la differenza non la noterebbe nemmeno chi a differenza mia ha un cervello funzionante)… e ne è uscito fuori veramente da piangere come mai prima d’ora. 😿Sostanzialmente, questo RPG (che dicono essere estremamente mid dal punto di vista del gioco in sé, ma non avendo voglia nemmeno di provare la demo non mi esprimo su ciò) sarebbe in sviluppo da una roba come 7 anni, avendo ricevuto finora tipo 20mila dollari di raccolta fondi, e non va avanti. Questo, a detta sua, è perché sta avendo problemi con la scrittura… ma invece no: è perché il suo codice è uno spaghetto di livello extraterrestre, molto semplicemente. Ah, e anche perché, invece di lavorare per davvero allo sviluppo, è ogni giorno in live a yappare o a fare gaming… e la cosa mi ricorda stranamente un altro sviluppatore indie a suo tempo ancora più perculato, ma non voglio divagare già ora… ☠️Tornando al punto: <a href="https://www.youtube.com/watch?v=HHwhiz0s2x8" rel="nofollow noopener" target="_blank">Coding Jesus, in un suo video, ha preso tutti i frame dove si vedeva codice del gioco nelle sue live</a> (che, per essere nel corso di mesi e mesi, sono sorprendentemente pochi), e lo ha semplicemente distrutto. Questa non è una code review che si può spiegare in due parole… ma, in breve, Thor (si, anche lui stesso ha un nome assurdo, per chi non lo avesse ancora afferrato…) dimostra praticamente di non afferrare i principi base di programmazione; il codice è completamente inmantenibile, ma a livello praticamente da meme. 🤥<a href="https://www.youtube.com/watch?v=HHwhiz0s2x8" rel="nofollow noopener" target="_blank">https://www.youtube.com/watch?v=HHwhiz0s2x8</a>Il problema di tutta la storia, ovviamente, non è di per sé il fatto che questo qui sia un incapace patentato… ma che ha un ego smisurato, che ha praticamente mentito sulla sua intera carriera professionale (pur se non inventando cose di sana pianta, solo omettendo o manipolando alla grande i piccoli dettagli), che a riguardo di questo suo progetto racconta tutt’ora di continuo sempre e solo palle pur di non ammettere la tragica situazione reale che lo riguarda, e che in generale sembra essere ben più interessato a pavoneggiarsi che a fare quello che dice di voler fare! Oh, io sono la prima che dice che è assolutamente sacrosanto il diritto a creare anche la merda; fateli i giochi, assolutamente, pure se non sapete programmare… ma non fate la voce profonda per apparire più saggi di quello che siete davvero, vi prego! 😭E boh, mi permetto persino una riflessione spaventosamente reale qui, perché nessuno sembra averla fatta: è specialmente curioso che, quando escono queste controversie riguardo sviluppatori indie, sono sempre sviluppatori di videogiochi. Non che ne escano tantissime eh — e, infatti, l’unico pensiero parallelo a questa storia che gira nella mia mente riflettendoci è che questo Thor è letteralmente il nuovo YandereDev per quanto mi riguarda, e non riesco minimamente a confutare questa mia ipotesi stellare — però boh, in altri casi esce poco… Sarà forse che, negli altri casi, <a href="https://memos.octt.eu.org/m/a7FayoC4uk7pQYc5EYaHiQ" rel="nofollow noopener" target="_blank">da un lato è puramente il codice a parlare</a>, mentre dall’altro i polli che donano migliaia di soldi sulla pura fiducia non ci sono? 🥴<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/videogiochi/" target="_blank">#videogiochi</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/coding/" target="_blank">#coding</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/gamedev/" target="_blank">#gamedev</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/piratesoftware/" target="_blank">#PirateSoftware</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/codingjesus/" target="_blank">#CodingJesus</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/heartbound/" target="_blank">#Heartbound</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://octospacc.altervista.org/tag/codereview/" target="_blank">#CodeReview</a>

DevTo VN BotCode reviews là chìa khóa để phát triển phần mềm chất lượng. Cải thiện chất lượng, chia sẻ kiến thức và tăng khả năng bảo trì. Tự động hóa và phản hồi mang tính xây dựng cũng rất quan trọng. <a href="https://mastodon.maobui.com/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> <a href="https://mastodon.maobui.com/tags/Ph%C3%A1tTri%E1%BB%83nPh%E1%BA%A7nM%E1%BB%81m" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhátTriểnPhầnMềm</a> <a href="https://mastodon.maobui.com/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a> <a href="https://mastodon.maobui.com/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://mastodon.maobui.com/tags/VietNam" class="mention hashtag" rel="nofollow noopener" target="_blank">#VietNam</a><a href="https://dev.to/mikeover/unlocking-the-secrets-of-effective-code-reviews-insights-from-the-community-38i" rel="nofollow noopener" translate="no" target="_blank">https://dev.to/mikeover/unlocking-the-secrets-of-effective-code-reviews-insights-from-the-community-38i</a>

Hacker NewsThe impact of file position on code review<a href="https://arxiv.org/abs/2208.04259" rel="nofollow noopener" translate="no" target="_blank">https://arxiv.org/abs/2208.04259</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/fileposition" class="mention hashtag" rel="nofollow noopener" target="_blank">#fileposition</a> <a href="https://mastodon.social/tags/codereview" class="mention hashtag" rel="nofollow noopener" target="_blank">#codereview</a> <a href="https://mastodon.social/tags/impact" class="mention hashtag" rel="nofollow noopener" target="_blank">#impact</a> <a href="https://mastodon.social/tags/research" class="mention hashtag" rel="nofollow noopener" target="_blank">#research</a> <a href="https://mastodon.social/tags/arxiv" class="mention hashtag" rel="nofollow noopener" target="_blank">#arxiv</a>

maschmiMorning time is code review time. And like in >90% of the code I'm reviewing before merging branches it is like "Yeah, that is okay. Some small things we should change. But nothing what I would not merge and we can do it afterwards."The one not falling into that category are mostly conceptual errors or misunderstood requirements. And they are often those we did plan rather quickly or we do not talk when something does not add up.<a href="https://mastodon.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwaredevelopment</a> <a href="https://mastodon.social/tags/codereview" class="mention hashtag" rel="nofollow noopener" target="_blank">#codereview</a>

WenAhh the mistakes we make as 7 year olds.I wish I had been in position to make the same mistakes. Hillarious<a href="https://www.theregister.com/2025/07/07/who_me/?td=rt-3a" rel="nofollow noopener" translate="no" target="_blank">https://www.theregister.com/2025/07/07/who_me/?td=rt-3a</a><a href="https://mastodon.scot/tags/FolliesOfYouth" class="mention hashtag" rel="nofollow noopener" target="_blank">#FolliesOfYouth</a> <a href="https://mastodon.scot/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> <a href="https://mastodon.scot/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://mastodon.scot/tags/SalutaryLessons" class="mention hashtag" rel="nofollow noopener" target="_blank">#SalutaryLessons</a>

रञ्जित (Ranjit Mathew)“Why I Won’t Use AI”, James Kenneth King (<a href="https://agentultra.com/blog/why-i-wont-use-ai/index.html" rel="nofollow noopener" translate="no" target="_blank">https://agentultra.com/blog/why-i-wont-use-ai/index.html</a>).Via Lobsters: <a href="https://lobste.rs/s/imjzlb/why_i_won_t_use_ai" rel="nofollow noopener" translate="no" target="_blank">https://lobste.rs/s/imjzlb/why_i_won_t_use_ai</a>On HN: <a href="https://news.ycombinator.com/item?id=44309309" rel="nofollow noopener" translate="no" target="_blank">https://news.ycombinator.com/item?id=44309309</a><a href="https://mastodon.social/tags/GenAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GenAI</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://mastodon.social/tags/LLMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLMs</a> <a href="https://mastodon.social/tags/VibeCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#VibeCoding</a> <a href="https://mastodon.social/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> <a href="https://mastodon.social/tags/Productivity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Productivity</a>

No Starch PressA code review full of sarcasm and vague critiques is like giving someone a broken compass and saying “you’ll figure it out.”Clarity > cleverness. If you want better code, offer better feedback. Precision, kindness, and context go further than snark ever will.<a href="https://mastodon.social/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> <a href="https://mastodon.social/tags/DevCommunity" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevCommunity</a> <a href="https://mastodon.social/tags/CleanCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#CleanCode</a> <a href="https://mastodon.social/tags/DevLife" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevLife</a> <a href="https://mastodon.social/tags/Codequality" class="mention hashtag" rel="nofollow noopener" target="_blank">#Codequality</a>

Mike P.Was fällt euch auf? Ist das wirklich sinnvoll so? Diskutiert mal! 👀Bitte denkt selbst nach und fragt nicht einfach eine KI – eure eigenen Ideen interessieren mich viel mehr!<a href="https://det.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://det.social/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> <a href="https://det.social/tags/fail" class="mention hashtag" rel="nofollow noopener" target="_blank">#fail</a> <a href="https://det.social/tags/dotnetperle" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnetperle</a> <a href="https://det.social/tags/cleancode" class="mention hashtag" rel="nofollow noopener" target="_blank">#cleancode</a> <a href="https://det.social/tags/boolLogic" class="mention hashtag" rel="nofollow noopener" target="_blank">#boolLogic</a> <a href="https://det.social/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> <a href="https://det.social/tags/nullable" class="mention hashtag" rel="nofollow noopener" target="_blank">#nullable</a> <a href="https://det.social/tags/bug" class="mention hashtag" rel="nofollow noopener" target="_blank">#bug</a>

David Cantrell 🏏It's <a href="https://fosstodon.org/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> time at work, and I can't just hit "approve" on everything, that might look like I'm not paying attention. Thankfully I found a legitimate reason to request changes on one of the pull requests so I don't have to find something absurd to nit-pick about.

Zuri (he/him) 🕐 CETFellow people in <a href="https://mastodon.online/tags/softwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareDevelopment</a>: How do you do "<a href="https://mastodon.online/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> post-processing", meaning what do you do with the review comments that either weren't (considered) directly actionable during the MR/PR (e.g. follow-up tickets) or contained general feedback/shortcomings that have to be addressed outside the scope of the MR/PR (e.g. improve our handbook, "replace this in the whole codebase", "we need to discuss this as a team" etc.)?<a href="https://mastodon.online/tags/amCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#amCoding</a> <a href="https://mastodon.online/tags/amProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#amProgramming</a> <a href="https://mastodon.online/tags/softwareEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareEngineering</a> <a href="https://mastodon.online/tags/webDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#webDevelopment</a>

John CrosbyCode reviews should be about knowledge sharing, not gatekeeping. The best reviewers ask questions instead of making demands.<a href="https://mas.to/tags/Engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#Engineering</a> <a href="https://mas.to/tags/Mentorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mentorship</a> <a href="https://mas.to/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a>

LLMsGitHub Just Got Chatty: Meet Gitingest, the Repo Whisperer ️️ You know that feeling when you land on a massive GitHub repo and you’re like: Continue reading on Medium » <a rel="nofollow noopener" class="mention hashtag" href="https://mastodon.social/tags/code-review" target="_blank">#code-review</a> <a rel="nofollow noopener" class="mention hashtag" href="https://mastodon.social/tags/llm-agent" target="_blank">#llm-agent</a> <a rel="nofollow noopener" class="mention hashtag" href="https://mastodon.social/tags/gitingest" target="_blank">#gitingest</a> <a rel="nofollow noopener" class="mention hashtag" href="https://mastodon.social/tags/documentation" target="_blank">#documentation</a> <a rel="nofollow noopener" class="mention hashtag" href="https://mastodon.social/tags/git" target="_blank">#git</a> <a href="https://medium.com/@varunrao.aiml/github-just-got-chatty-meet-gitingest-the-repo-whisperer-%EF%B8%8F-%EF%B8%8F-8b0215304d3e?source=rss------documentation-5" rel="nofollow noopener" target="_blank">Origin</a> | <a href="https://awakari.com/sub-details.html?id=LLMs" rel="nofollow noopener" target="_blank">Interest</a> | <a href="https://awakari.com/pub-msg.html?id=MTG5ZrMkbjnf6QP49mTuf6XMLBY&interestId=LLMs" rel="nofollow noopener" target="_blank">Match</a>

Alvin AshcraftGitHub for Beginners: Code review and refactoring with GitHub Copilot. <a href="https://buff.ly/HGOZOO1" rel="nofollow noopener" target="_blank">buff.ly/HGOZOO1</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23github" target="_blank">#github</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23githubcopilot" target="_blank">#githubcopilot</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23ai" target="_blank">#ai</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23codereview" target="_blank">#codereview</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23refactoring" target="_blank">#refactoring</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23programming" target="_blank">#programming</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23aiassistant" target="_blank">#aiassistant</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23learning" target="_blank">#learning</a> <a href="https://buff.ly/HGOZOO1" rel="nofollow noopener" target="_blank">GitHub for Beginners: Code rev...</a>

Alvin Ashcraft 🐿️GitHub for Beginners: Code review and refactoring with GitHub Copilot.<a href="https://github.blog/ai-and-ml/github-copilot/github-for-beginners-code-review-and-refactoring-with-github-copilot/" rel="nofollow noopener" translate="no" target="_blank">https://github.blog/ai-and-ml/github-copilot/github-for-beginners-code-review-and-refactoring-with-github-copilot/</a><a href="https://hachyderm.io/tags/github" class="mention hashtag" rel="nofollow noopener" target="_blank">#github</a> <a href="https://hachyderm.io/tags/githubcopilot" class="mention hashtag" rel="nofollow noopener" target="_blank">#githubcopilot</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/codereview" class="mention hashtag" rel="nofollow noopener" target="_blank">#codereview</a> <a href="https://hachyderm.io/tags/refactoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#refactoring</a> <a href="https://hachyderm.io/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://hachyderm.io/tags/aiassistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#aiassistant</a> <a href="https://hachyderm.io/tags/learning" class="mention hashtag" rel="nofollow noopener" target="_blank">#learning</a>

Hacker NewsVibe code isn't meant to be reviewed<a href="https://monadical.com/posts/vibe-code-how-to-stay-in-control.html" rel="nofollow noopener" translate="no" target="_blank">https://monadical.com/posts/vibe-code-how-to-stay-in-control.html</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/VibeCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#VibeCode</a> <a href="https://mastodon.social/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a> <a href="https://mastodon.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a> <a href="https://mastodon.social/tags/ControlTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#ControlTech</a>

Aubreader MastoConfessions of a programmer: I hate code review<a href="https://blog.nelhage.com/2010/06/i-hate-code-review/" rel="nofollow noopener" translate="no" target="_blank">https://blog.nelhage.com/2010/06/i-hate-code-review/</a>Most of the projects I've been working on today have fairly strict code review policies. My work requires code review on most of our code, and as we bring on an army of interns for the summer, I've been responsible for reviewing lots of code. [...] And I have a confession to make: I hate mandatory code review.<a href="https://mas.to/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mas.to/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a>

sntxSarcasm

HabrКод-ревью: борьба или мотивация?Привет! Меня зовут Илья, последние 7 лет я занимаюсь фронтендом и наконец решил отметиться на Хабре. Стартую с темы, которая, как кажется, уже успела приесться, но всё ещё вызывает жаркие споры — код ревью (CR). Не смотря на сотни статей и мануалов, каждая команда подходит к этому процессу по‑своему. Хочется зафиксировать и осмыслить собственный опыт, показать, как мы подходили к настройке процесса в реальном проекте, и почему, на мой взгляд, код‑ревью не может быть универсальным , а должен опираться на контекст команды. В этой статье не будет технических деталей вроде рекомендаций по максимальному количеству строчек в diff‑е или формату названий коммитов. Я хочу подняться на уровень выше и поговорить о целях, ключевых факторах и реальных компромиссах которые встречаются в CR.<a href="https://habr.com/ru/articles/914664/" rel="nofollow noopener" translate="no" target="_blank">https://habr.com/ru/articles/914664/</a><a href="https://zhub.link/tags/codereview" class="mention hashtag" rel="nofollow noopener" target="_blank">#codereview</a> <a href="https://zhub.link/tags/%D0%BA%D0%BE%D0%B4%D1%80%D0%B5%D0%B2%D1%8C%D1%8E" class="mention hashtag" rel="nofollow noopener" target="_blank">#кодревью</a> <a href="https://zhub.link/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://zhub.link/tags/frontend%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%BA%D0%B0" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontendразработка</a> <a href="https://zhub.link/tags/%D0%BA%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%BE_%D0%BA%D0%BE%D0%B4%D0%B0" class="mention hashtag" rel="nofollow noopener" target="_blank">#качество_кода</a> <a href="https://zhub.link/tags/%D0%BA%D0%BE%D0%BC%D0%B0%D0%BD%D0%B4%D0%BD%D0%B0%D1%8F_%D1%80%D0%B0%D0%B7%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%BA%D0%B0" class="mention hashtag" rel="nofollow noopener" target="_blank">#командная_разработка</a> <a href="https://zhub.link/tags/%D0%BC%D0%BE%D1%82%D0%B8%D0%B2%D0%B0%D1%86%D0%B8%D1%8F_%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%81%D1%82%D0%BE%D0%B2" class="mention hashtag" rel="nofollow noopener" target="_blank">#мотивация_программистов</a> <a href="https://zhub.link/tags/%D0%BC%D0%BE%D1%82%D0%B8%D0%B2%D0%B0%D1%86%D0%B8%D1%8F_%D0%B2_%D0%B8%D1%82" class="mention hashtag" rel="nofollow noopener" target="_blank">#мотивация_в_ит</a>

Never Code AloneIch glaube, KI-Tools wie Claude 4 beschleunigen die Entwicklung enorm, aber Code-Reviews werden zum Flaschenhals. 50 Files & 5000 Zeilen Code mit PHPUnit & E2E-Tests abgesichert - wer kann das noch reviewen? Wie geht ihr mit diesem massiven Code-Producement um? <a href="https://mastodon.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://mastodon.social/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeReview</a>

Recent searches

Search options

Administered by:

Server stats:

#codereview