# Thinking in Tech Clear thinking leads to clean code and architecture. Subscribe for weekly ideas and challenges that will sharpen your technical skills. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Three Stages of Software Maturity: From Hype to Abandonment DevFeed: [The Three Stages of Software Maturity: From Hype to Abandonment]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2025-03-15T12:32:17Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [Software](), [Open Source](), [Tooling](), [Jenkins](), [ci](), [Docker](), [Kubernetes](), [Security]() Tags: [ci](), [docker](), [java](), [jenkins](), [kubernetes](), [let-s-encrypt](), [open-source](), [software]() ### AI overview This opinion article proposes evaluating software maturity through maintenance activity, commercial support, ecosystem integrations, community knowledge, code quality, and culture. It contrasts Docker Swarm with Kubernetes after finding a Swarm Jenkins extension had not changed in four years and had an unresolved vulnerability. ### Source excerpt From Hype to Abandonment ## Coding with AI DevFeed: [Coding with AI]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2025-03-01T12:23:34Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [coding](), [Artificial Intelligence](), [Code](), [Code quality](), [Large Language Model](), [jetbrains-ai](), [Python]() Tags: [ai](), [code](), [code-quality](), [coding](), [developers](), [jetbrains-ai](), [llm]() ### AI overview This personal commentary describes using AI coding tools to build JustRM, a lightweight networking contact app, while working a full-time job. The author reports that AI accelerated prototyping, repetitive coding, and test writing, but also produced poor-quality code, struggled with infrastructure work, and behaved unreliably when uncertain. ### Source excerpt The good, the bad and the ugly ## How Engineers Translate Business Needs into Software DevFeed: [How Engineers Translate Business Needs into Software]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-12-07T12:08:11Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [Software](), [coding](), [React]() Tags: [coding](), [engineering](), [software](), [tech]() ### AI overview The article argues that engineers act as translators between stakeholders and computers by turning business needs into software. It also distinguishes the thinking responsibilities of business and technical leadership roles and suggests that practice enables engineers to think directly in technical structures. ### Source excerpt How I learned to design software ## How the engineering market changed since 2006 DevFeed: [How the engineering market changed since 2006]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-08-27T10:49:26Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Software Engineering](), [Development](), [PHP](), [Java](), [Web]() Tags: [career](), [change](), [developer](), [engineering](), [java](), [php](), [software-engineering](), [web]() ### AI overview An account of how the software engineering market changed from the early 2000s through the pandemic, combining personal career experiences with observations about shifts in technology, employment, and the future of the field. ### Source excerpt and how to prepare for the future ## Code.Lead.Succeed is changing DevFeed: [Code.Lead.Succeed is changing]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-06-30T12:35:50Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [engineering-leadership](), [Software Engineering](), [engineering-culture]() Tags: [engineering-leadership](), [engineering-manager](), [software-engineering](), [updates]() ### AI overview The author explains changes to the Code.Lead.Succeed newsletter and broader publishing strategy for 2024. Long-form content will move to the author's website, while the newsletter will continue with monthly software engineering philosophy articles and personal updates. The author also explains plans to focus more on an engineering leadership coaching business and why they are reducing activity on Substack. ### Source excerpt Code.Lead.Succeed is changing ## The Soft Side of Software Design DevFeed: [The Soft Side of Software Design]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-06-01T11:11:37Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Architecture & Design](), [Software Engineering](), [Software]() Tags: [design](), [good-practices](), [soft-skills](), [software](), [software-design](), [systems]() ### AI overview The article argues that software design, like soft skills, is difficult to evaluate objectively because its quality depends on context, communication, personal judgment, and real-world outcomes. It questions whether conventions such as readable code, established practices, or TDD reliably define good design. ### Source excerpt How to build systems in the real world ## The Path to Software Engineer DevFeed: [The Path to Software Engineer]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-05-25T11:39:48Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Software](), [Programming](), [Job](), [Agile]() Tags: [agile](), [article](), [career](), [developer](), [learning](), [risk](), [software](), [software-engineer]() ### AI overview The article presents a three-stage path for growing in software work: Coder, Developer, and Engineer. It describes coding as an early stage focused on making programs work, development as specialist growth, and engineering as a broader progression beyond rigid processes and solutions. ### Source excerpt What's the difference between Coder, Developer and Engineer? ## Why software engineers should prioritize judgment, communication, and practical experience DevFeed: [Why software engineers should prioritize judgment, communication, and practical experience]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-05-18T15:35:35Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [Software Engineering](), [Artificial Intelligence](), [Code](), [Large Language Model]() Tags: [ai](), [code](), [communication-skills](), [leadership](), [skills](), [software-engineering]() ### AI overview This opinion article argues that widespread internet access and AI have reduced the value of simply possessing technical knowledge. It suggests that software engineers should prioritize judgment about what to learn and how to apply it, along with communication, leadership, practice, and feedback. ### Source excerpt What should we focus on instead? ## How Software Engineers Can Set Realistic Commitments and Exceed Expectations DevFeed: [How Software Engineers Can Set Realistic Commitments and Exceed Expectations]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-05-09T13:45:35Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [Code](), [Software](), [Job]() Tags: [code](), [software](), [work](), [writing-code]() ### AI overview This opinion article presents "underpromise-overdeliver" as a software engineering and career practice. It recommends making realistic commitments, focusing on delivering the basics well, and using saved time and effort to exceed expectations. ### Source excerpt How to deliver more by working less ## The 3+1 ingredients of making good engineering decisions DevFeed: [The 3+1 ingredients of making good engineering decisions]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-04-20T10:05:36Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [decision-making](), [Software Engineering](), [Development]() Tags: [decision-making](), [development](), [engineering](), [software](), [software-engineering]() ### AI overview This article presents questions engineers can use to improve decision-making: define the desired outcome, identify constraints, and compare options. It argues that decisions should be grounded in evidence while accounting for team size, technology choices, budget, hiring, and organizational context. ### Source excerpt And how to improve your decision-making starting today ## Introduction to Strategic Thinking DevFeed: [Introduction to Strategic Thinking]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2023-12-09T10:45:48Z Content type: tutorial Language: en Sources: [Thinking in Tech]() Topics: [Requirements](), [Software](), [Code]() Tags: [how-to](), [introduction](), [skills](), [strategy]() ### AI overview This article introduces strategic thinking for software developers as an ongoing process focused on the what and why of work. It presents three pillars: technical skills, creative problem-solving, and analytical skills, emphasizing adaptation to changing goals, requirements, data, and constraints. ### Source excerpt how to play ahead of the game ## Why the author argues that job security is uncertain and how to prepare for layoffs DevFeed: [Why the author argues that job security is uncertain and how to prepare for layoffs]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2023-11-18T12:30:18Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [Job](), [OpenAI]() Tags: [hiring](), [job](), [jobs](), [money](), [new-job](), [openai](), [sam]() ### AI overview This opinion article argues that shareholder-focused business models can make employment unstable, using Sam Altman's departure from OpenAI and Steve Jobs's 1985 ouster as examples. It recommends preparing for possible layoffs with an exit strategy, awareness of hiring needs, and an emergency fund. ### Source excerpt OpenAI and Sam Altman just proved it yesterday ## A Surface-Area Model of Seniority for Software Engineers DevFeed: [A Surface-Area Model of Seniority for Software Engineers]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2023-11-11T12:31:00Z Content type: opinion Language: en Sources: [Thinking in Tech]() Topics: [Software Engineering](), [Code](), [Learning]() Tags: [career](), [code](), [learning]() ### AI overview The article proposes assessing software-engineering seniority by the breadth and depth of a person's skills. It argues that specialists and generalists can be equally senior when their overall surface area of knowledge is sufficiently large. ### Source excerpt And how to design your career to become one ## 12 Career Lessons for Software Engineers DevFeed: [12 Career Lessons for Software Engineers]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2023-11-04T12:06:59Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Software Engineering](), [Development](), [Learning](), [engineering-culture]() Tags: [career](), [coaching](), [coding](), [communication](), [leadership](), [learning](), [project-management](), [software-engineering]() ### AI overview A software engineering career article presents 12 lessons drawn from the author's 12 years of experience, emphasizing ownership, long-term planning, continuous learning, communication, and skills beyond coding. ### Source excerpt I learned in 12 years of my Software Engineering career