Juniors generate and ship AI code they don't understand, resisting guidance, degrading skills, and creating unmaintainable codebases while seniors burn out on ineffective mentoring.
Senior engineers struggle to mentor juniors who generate code with AI tools but lack understanding of it, leading to poor maintainable code, resistance to guidance, and skill degradation.
What are we doing with juniors these days, seriously?
What are we doing with juniors these days, seriously?
"the bigger issue... is people blindly shipping code they don’t understand"
commentWhat I usually do with juniors is pretty simple. If they used an LLM to write something, I ask them to explain the flow of the logic back to me. Not line by line necessarily but enough that I know they actually understand what they’re pushing. Half the time I just want to know if they even bothered reading the summary/TLDR the model gave them. At this point I think we just have to accept that AI tools are here and juniors are obviously going to use them. Fighting that feels pointless. The better thing is to make sure they understand the solution they got and can think beyond it a little. So usually after that I’ll ask them what other approaches they looked at, why they picked this one, what the tradeoffs are and stuff like that. If they can explain why one approach makes more sense for a specific use case, then I’m fine with them using AI to get there faster. Yeah, I do think this removes some of the “figure it out yourself after being stuck for 5 hours” learning experience we all had, especially for dumb bugs and mistakes. But at the same time, if someone is actually curious and putting in effort, they can also learn way faster this way. The bigger issue to me isn’t AI usage itself. It’s people blindly shipping code they don’t understand and treating the model like it’s always correct. If they actually take time to understand the generated code and explore different ways of solving the same problem, then over time they’ll build decent they will still grow into solid engineers.
Senior engineers responsible for code quality, PR reviews, and growing junior developers in teams using tools like Claude/Cursor who now face juniors shipping incomprehensible AI output.
Multiple strong repeated signals across seniors about AI degrading skills, ineffective mentoring, and hiring avoidance.
Purpose-built to enforce understanding and critical thinking on AI output, unlike pure code gen tools or generic review platforms.
GitHub-integrated platform where juniors must interactively explain and defend AI-generated code before PR approval, with AI-assisted prompts, senior feedback loops, and comprehension scoring to rebuild ownership and critical thinking.
Seniors already spend significant review time on AI code they describe as "pasting from Claude" with no understanding; teams explicitly avoid hiring juniors due to cost and quality — a tool restoring mentoring ROI justifies the price as cheaper than lost productivity or bad hires.
“Turn AI-pasted code into understood, owned code in every PR.”
GitHub-integrated platform where juniors must interactively explain and defend AI-generated code before PR approval, with AI-assisted prompts, senior feedback loops, and comprehension scoring to rebuild ownership and critical thinking.
Launch on Hacker News, r/ExperiencedDevs, r/cscareerquestions, and engineering manager communities with free beta for teams of 5+
Juniors could use AI to generate explanations, undermining the core goal of building real understanding.
Mandatory explanation steps may slow velocity and face resistance from velocity-focused managers.
Keeping up with GitHub PR changes and multiple AI coding tools adds ongoing dev cost.
Juniors who prefer blind AI use may resist or complain about the extra work required.
Run an Investment Memo to get a structured Go / No-Go verdict, competitor landscape, unit economics, and a 90-day validation roadmap for this opportunity.
Generate an investment memoThis opportunity scores well above the median for ideas surfaced by MonetScope, with a validation sub-score of 8/10 against 3 independently sourced evidence signals. A "strong" rating in this band typically means the pain signal is consistent and recurring across multiple discussions, but one of the three pillars (severity, willingness to pay, or competitor weakness) is somewhat softer than top-tier opportunities. Founders evaluating this should focus customer discovery on the softest pillar first — confirming the gap before committing engineering time to a build.
It sits at the intersection of "ai-powered", "code-review", "devtools", which makes it relevant to a specific subset of founders rather than a generic horizontal opportunity. SaaS opportunities at this stage tend to win on the strength of their initial wedge — a single workflow that the target user runs every week, where the existing solution is either spreadsheets, a clunky incumbent feature, or a manual process they hate. The build cost is moderate; the distribution cost is everything. The MonetScope pipeline surfaces this category alongside other saas signals, which is why it appears here rather than in a generic "trending ideas" feed.
Scores are derived from real forum discussions across Reddit, Hacker News and X, weighted by evidence volume and signal quality. How scoring works
MonetScope does not generate ideas from a language model's imagination. Every opportunity on this site is anchored to specific source posts and comments from real public discussions — typically on Reddit, Hacker News, or X — where actual users describe the pain in their own words. The AI's role is structuring, scoring, and grouping those signals into a navigable opportunity, not inventing the problem.
MonetScope's spider pipeline runs continuously and surfaces opportunities as new evidence accumulates. The "Updated" date in the header reflects the most recent re-scoring of this specific opportunity. Most saas opportunities visible in the public catalog draw from discussions in the last 30-60 days; older signals are de-prioritized because user pain shifts faster than most founders assume.
Overall score is a composite across six dimensions — pain, urgency, willingness to pay, market size, defensibility, and execution ease — designed to give a single number for triage. Validation score is narrower: it asks "how cleanly does the same signal repeat across independent sources?" An opportunity can score high on overall but lower on validation when one or two large discussions dominate the evidence; conversely, validation can be high on a smaller-overall idea where the signal is consistent but the addressable market is modest.
