Les devs ne codent presque plus en 2026
Developers will hardly be coding anymore by 2026
Title history
- Les devs ne codent presque plus en 2026 — observed on 20261101-0148 UTC (YouTube)
Keywords
Summary
168 words
Critical Evaluation
Value of the Information & Strength of the Argument
The video offers a valuable first-hand perspective on the daily reality of developers in 2026, supported by a referenced industry report. The argumentation is convincing in describing the increased emphasis on code review and the shift in required skills. However, it relies heavily on personal anecdotes and does not provide quantitative evidence beyond the cited report. The reasoning is coherent and practical, suggesting concrete training methods for juniors, but it remains a subjective viewpoint rather than a comprehensive analysis.
Scientific Rigor, Source Quality, Title Accuracy
The video is grounded in personal experience and a single referenced report (State of Code by Sonar), which adds credibility. However, the source is not deeply analyzed, and no contrasting data or studies are presented. The title accurately matches the content, which is a professional reflection on the changing role of developers. The creator does not cite multiple independent sources, limiting the scientific rigor. The comments tend to confirm the phenomenon but also express concern, aligning with the video’s narrative.
174 words
Title / Content Match
The title accurately reflects the central claim that developers spend less time coding and more time reviewing AI-generated code.
Quality & Reliability
6/10
The video is based on personal experience and a referenced industry report (State of Code by Sonar), but lacks detailed methodological context or verification of claims. It offers a credible qualitative perspective on the changing developer role, but should be considered anecdotal rather than rigorously evidenced.
Key Moments
Markers derived by PSI from the transcript: the creator did not define chapters.
- Introduction: developers now read code more than they write it.
- Mention of increase in pull requests and time spent on reviews.
- Reference to the State of Code report and the new priority of reviewing AI-generated code.
- Identifies the two most important skills: reviewing and prompting.
- Discusses the evolution of required skills and the persistence of fundamentals.
- Advises juniors to train by comparing outputs from multiple LLMs.
- Discusses cost of AI tools and Cursor subscription.
- Emphasizes the importance of creating well-structured pull requests for effective review.
- Closing remarks: adaptation, family, and call to action.
Cited Sources
- State Of Code by Sonar — Industry report cited as evidence of the new developer skills required.
Concurring Sources
- State Of Code by Sonar — The report supports the claim that reviewing AI-generated code is the number one skill.
External References
Contribution & Novelties
The video provides an original first-person account of the practical impact of AI on the daily work of a developer, emphasizing the shift from coding to code review. It offers a concrete training suggestion for juniors: compare outputs from different LLMs on the same task to develop evaluation skills. The reinforcement of the importance of review skills over raw coding is a valuable insight for the community.
Pour aller plus loin :
- Code review — Foundational concept for the new developer role.
- Pull request — Key mechanism in modern software collaboration.
- Large language model — Underpinning technology behind the changes.
- Software engineering — Broad context for the evolving discipline.
109 words
Radar Profile
The profile shows a moderate balance across all dimensions, with slightly higher scores in information quantity and technical level, but lower in reliability due to the anecdotal nature and single-source dependence. This suggests a persuasive but not deeply evidence-based presentation.
💬 Équilibré avec une tonalité nostalgique. Sur les 30 commentaires analysés, le climat est partagé entre regret du codage manuel et acceptation de l'évolution, avec une majorité de retours reflétant une appréhension quant à l'avenir du métier.