#Software-Engineering
111 notas · última:
Goodbye to the Hard Parts That Never Mattered
The author argues that coding agents remove toil, not engineering. They shift work toward judgment, verification, responsibility, and broader creative exploration, while raising real concerns about access, learning, and scaled mistakes.
I don't know if my job will still exist in ten years
The author argues that software engineering may shrink fast as AI agents get better at writing, reviewing, and maintaining code, leaving engineers to supervise systems or exit the field.
Grifters, believers, grinders, and coasters
The article argues that engineering conflicts often come from different work styles: grifters, believers, coasters, and grinders. Good teams need a mix, and each type has strengths and limits.
How I use LLMs as a staff engineer
The author uses LLMs as smart autocomplete, a tutor for new domains, a fallback for bugs, and a proofreading tool, while avoiding them for full drafts and familiar production work.
How a Sustainable Mindset in Software Engineering Can Increase Team Performance and Prevent Burnout
Marion Løken argues that sustainable software work means balancing resources, control, connection to the work, and recognition, using team-wide discovery, collective feedback, and psychological safety to reduce burnout.
Design Docs at Google
Explains how Google uses design docs to capture high-level implementation strategy, surface trade-offs early, align teams, and preserve design decisions through review and iteration.
Why are senior developers learning low-code and AI tools? [Adrian Twarog Interview #129]
Interview with Adrian Twarog about how he built his skills through work projects, design tutorials, early GPT content, and staying current with AI and low-code tools while working in Perth.
Software Engineering Job Market 2026: Data, Trends and Outlook
The market splits between fast-growing AI roles and weaker entry-level generalist hiring. Pay rises with level and AI skills, while interviews now test AI systems, cloud, and deployment experience.
Write Down the Plan
The post argues that writing down and sharing a plan improves thinking, creates alignment, and increases visibility, making it a useful habit for software engineers and career growth.
How To Get Promoted (Without Getting Lucky)
The piece argues that promotion to Staff comes from sustained impact, leverage, strong internal visibility, collaboration, and clear communication with your manager, not from luck or effort alone.
Everything I Know About Shipping Code Faster
The post argues that shipping faster comes from finding code paths quickly, keeping diffs small, testing in batches, reducing reviewer friction, and protecting focus from interruptions.
The Future Of Software Engineering with Anthropic
Roundtable on how AI is changing software engineering: closed-loop development, test-first workflows, evolving code review, long-horizon agents, and the limits of adoption in regulated settings.
The Mythical Agent-Month — Wes McKinney
Wes McKinney argues that coding agents reduce accidental complexity and speed up code generation, but they also amplify scope creep, coordination problems, and bloated codebases. Design, taste, and expert human judgment remain the bottlenecks.
Testing is software engineering
The page argues that testing is part of engineering, not an afterthought. It says tests improve design, make changes safer, surface hidden requirements, and help teams collaborate.
Lifelong Learning: 88+ Resources I Don't Regret as a Senior Software Engineer
A senior software engineer shares newsletters, books, videos, docs, and a personal system for learning, arguing that the best results come from choosing a few resources and applying them quickly.
8 effective debugging strategies to find and fix bugs like a pro
The article argues that debugging skill is central to trusted software work and lists eight practical tactics: reproduce the bug, narrow it down, use tools, and take breaks when needed.
The Secret to Growth as Software Engineer
The author says growth comes from comparing your current work with your past work, seeing how your code and judgment have improved, and using that reflection to do better next time.
The Laws of Software Evolution
The page summarizes Lehman’s view that software keeps changing, grows more complex, and is shaped by past choices, while distinguishing S-, P-, and E-programs and outlining an idealized development lifecycle.
Cohesion vs. Coupling
Explains cohesion as the internal focus of a module or system, and coupling as the external dependence between things, especially how changes in one place affect another.
Smart core, thin interfaces
The post argues for keeping business logic in a small, smart core and putting actor-specific handling at the edges, where inputs are sanitized and interfaces hide messy details.
Finding modules in a big ball of mud
The post argues that tangled code is normal and that modules should be found by reading dependency graphs, matrices, and domain neighborhoods rather than forcing an early architecture.
6 books engineers should read
The post argues that books give engineers deeper, more practical guidance than blogs or videos, and recommends six titles for everyone from interns to senior engineers based on teamwork, ownership, process, and decision-making.
Software Developer vs. Software Engineer: Important Differences to Consider
The page says both jobs are in high demand, but software engineers work more broadly, collaborate more, and usually earn more, while software developers focus more on building and testing applications.
You don’t need long hours to be a TOP software engineer. Make technology your ally, not your enemy
The page argues that software engineers should focus on output, deep work, and AI-assisted automation instead of long hours, since focused work and recovery produce better results than clocking time.
The easy road to become a TOP performer software engineer: Simplifying productivity
The article argues that software engineers should focus each day on three high-impact tasks, align work with team priorities, track outcomes, and use simple systems to reduce decision fatigue.
How the best software engineers write technical designs (the blueprint for consistent results)
The article argues that technical design helps software engineers work more consistently by reducing ambiguity, aligning teams, and making workstreams easier to parallelize. It also outlines what a design should cover and how to structure it.
From Code to Words: How to Write Well for Software Engineers
The post argues that writing is a core engineering skill because it aligns teams, reduces meetings, and creates a shared record. It frames good writing as a practice built through Identify, Iterate, and Invite.
Always negotiate your deadlines! (How to gain trust and prevent working overtime)
The post argues that when a deadline is fixed and team capacity cannot change, engineers should negotiate scope instead of trying to absorb the work alone or refusing outright.
How to turn AI from a random code generator into a reliable teammate
The article argues that engineers should steer AI instead of trusting it blindly, using clear rules, review, and a steering doc so AI speeds up work without replacing judgment.
Staff, principal, distinguished: Engineering career levels explained
The article outlines engineering career tracks, focusing on the individual contributor ladder from Engineer I to distinguished engineer, and explains why a clear hierarchy helps career growth, clarity, and motivation.
Becoming a go-to person gets you promoted. Here's how to do it as a software engineer.
To reach senior level, the article says you need broader scope, impact, and ownership. It argues that becoming a visible expert in a technical or product area helps create opportunities and promotion.
Everyone is a Staff Engineer Now
The article argues that coding agents are pushing engineering work upward: execution gets cheaper, while planning, context management, architecture, review, and clear intent become the main bottlenecks.
How do interruptions impact different software engineering activities?
The page reports that interruptions affect code writing, code comprehension, and code review in different ways, with requester authority, task type, and interruption type shaping productivity and stress. It also recommends using perception data, not just physiology.
4 Steps to Prepare for System Design Interviews in 2025
The page says system design interviews require core concepts, engineering blogs, common questions, and repeated practice, with mock interviews and timing used to avoid common mistakes.
A Note on Essential Complexity
The post argues that software engineers should think beyond accidental versus essential complexity. By questioning requirements and shaping users and organizations, they can sometimes reduce complexity by changing the problem itself.
Books Every Software Engineer Must Read in 2024
The page argues that developers should invest in lasting fundamentals rather than short-lived frameworks, and recommends books on software development, architecture, testing, distributed systems, DevOps, leadership, and habits.
The 12 mental models and biases for engineers
The article groups mental models and cognitive biases that shape engineering decisions, with examples of second-order thinking, first principles, inversion, Pareto, sunk cost, confirmation bias, and other models.
Computer Science Papers Every Developer Should Read
The article argues that reading computer science papers helps developers understand core concepts, think critically, and learn from foundational work behind modern software, databases, distributed systems, and search.
13 Undesirable Behaviors in Software Engineers: Are You Guilty?
The post argues that software engineers are judged as much by behavior as by technical skill, and lists habits that hurt collaboration, trust, and team morale.
How to Be Pragmatic as an Engineer
The article defines pragmatism as choosing what works in real-world constraints, then argues for simple, trade-off-aware decisions, avoiding premature optimization, and asking better questions early.