惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
腾讯CDC
博客园 - 司徒正美
A
About on SuperTechFans
H
Help Net Security
J
Java Code Geeks
C
Check Point Blog
B
Blog RSS Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
MongoDB | Blog
MongoDB | Blog
U
Unit 42
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
MyScale Blog
MyScale Blog
V
Visual Studio Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
I
InfoQ
H
Hackread – Cybersecurity News, Data Breaches, AI and More
F
Fortinet All Blogs
博客园 - 聂微东
酷 壳 – CoolShell
酷 壳 – CoolShell
GbyAI
GbyAI
博客园 - 【当耐特】
雷峰网
雷峰网

Hacker News: Ask HN

The New Window Delete ChatGPT Atlas Spyware Tell HN: Qwen Free Tier Is Discontinued Ask HN: SeedLegals Partnerships in London, worth it? Ask HN: How to highlight talent from untraditional backgrounds? Ask HN: We dont need a programming language now? Durable Object alarm loop: $34k in 8 days, zero users, no platform warning What if Time at the subatomic level has multiple arrows? How to add MidnightBSD Key to UEFI Secure Boot DBX? (Revoked and Forbidden Keys) Ask HN: What's your experience working at xAI as an AI tutor? Any engineers here with experience of clinical data standards? Ask HN: Who is using OpenClaw? Agent Skills for Software Test Automation Ask HN: Who needs contributors? Claude Code is thinking too much Ask HN: What Is the Big-O Order of a Jigsaw Puzzle? Ask HN: Stepping into a new role as a Senior, mentoring dos and dont's? Founder from Zurich heading to SF and Austin for the first time Hacker News No Manual Screenshots: I Built a Scalable Screenshot API Using Cloud Playwright Ask HN: Thought experiment: AGI giving us answers we don't like? Ask HN: I quit my job over weaponized robots to start my own venture 1% Vacancy, 81% Preleased: Where Midmarket Compute Deploys in 2026 Ask HN: Preferred pricing model for sound effects libraries? Copy of the email I sent to my undergraduate professors on Nov 30, 2025 Model API Performance | Hacker News Ask HN: Are open-weight LLMs the new offline encyclopedias? Valgrind 3.27 RC1 is out Claude Code OAuth down for >12 hours Ask HN: What's Better?–Tauri or Electron?
Coworkers Producing Shit Code | Hacker News
GamingAtWork · 2026-05-27 · via Hacker News: Ask HN
Coworkers Producing Shit Code
3 points by GamingAtWork 9 days ago | hide | past | favorite | 7 comments

hey im a jr software dev, somehow it seems like all my coworkers produce shit code 24/7. They are either trying to get it done as quickly as possible or they are lazy, or they are just clueless. They basically take the entire sprint to fix the new defects their features introduce. At first when I joined the team as a jr I didn't know exactly what their code did, now that I have been working in the codebase for 9 months I can clearly tell the code quality they are producing is just shit. what should I do? Basically their shit code gets through code review with just cosmetic changes, but the maintainability/robustness etc. is usually just enough to meet the AC's the next one to work off their feature is doomed since everything is hard-coded bs copied and pasted from features developed 10 years ago by another shit coder.

 help


> what should I do?

Does your team have a manager, a project manager, and/or a tech lead? And do you feel like you can trust them to take criticism and not retaliate?

If so, raise your concerns with them.

If the answer to any of those questions is no, you have two options:

1. Step up and try to lead the team to a better place.

2. Get a different job at a better place.


the team manager is the one who is reviewing & approving the shit code so idk how I can tell them "hey why are you approving shit code ?" I think i will either wait to be promoted or just find a new job but rn swe jobs are pretty hard to get for new grunt developers out of college. I have been coding and developing things since I was in middle school so maybe that's why i can tell that the code is so bad but for everyone else maybe that's just how it is?


It's all in how you phrase it.

"Mgr, I've got some concerns about our code quality. We seem to be prioritizing velocity over quality, and paying for it - X% of our sprints are spent fixing bugs introduced by what we shipped the previous sprint, instead of adding new features. Slowing down will actually increase the speed at which we can ship features, and make us look better to the higher ups as well."


yes I actually tried doing that in the last retrospective. Immediately got attacked by the scrum master and my manager literally couldn't figure out what to say (super indian guy). literally a few days later the entire jira board is full of defects lol.


Then it sounds like option #2 is probably your way out.

Remember when interviewing, don't just shit all over your current job - phrase that well, too. "I'm looking for a place with a more mature software development philosophy, with a higher focus on QA than my team currently has."