# understand Published articles for understand. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Prevent cognitive debt by manually retyping LLM-generated code DevFeed: [Prevent cognitive debt by manually retyping LLM-generated code]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-04T12:56:26Z Content type: opinion Language: en Sources: [freek.dev - all blogposts]() Topics: [Large Language Model](), [Code]() Tags: [ai](), [best-practices](), [code](), [code-quality](), [cognitive-load](), [developer-experience](), [llm](), [model](), [practical](), [prevent](), [understand]() ### AI overview Ankur Sethi argues that manually retyping code generated by large language models can help developers understand the code, identify poor suggestions, and maintain a strong mental model of their codebase, despite slowing development. ### Source excerpt Ankur Sethi argues that manually retyping LLM-generated code is a practical way to avoid cognitive debt. It slows you down, but helps you understand the code, catch bad suggestions, and keep a strong mental model of your codebase. Read more ## TBM 429: How To Thrive At Work When You Think Too Much DevFeed: [TBM 429: How To Thrive At Work When You Think Too Much]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-07-06T18:53:46Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [systems](), [help]() Tags: [problems](), [systems](), [understand](), [work]() ### AI overview An introduction to a proposed book about thriving at work when you feel misunderstood or tend to overthink. It examines how traits such as deep analysis, noticing inconsistencies, and questioning assumptions can be experienced as both strengths and flaws in workplace feedback. ### Source excerpt This post is important. ## Neural Networks Explained In Plain English DevFeed: [Neural Networks Explained In Plain English]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-04-21T04:01:25Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Neural Network](), [AI Engineering](), [Machine learning]() Tags: [ai-engineering](), [applications](), [concepts](), [function](), [mlp](), [neural-networks](), [neuron](), [understand]() ### AI overview A plain-English introduction to neural networks. It explains neurons or perceptrons, activation functions, weights and biases, and how stacking neurons into dense layers creates a multilayer perceptron (MLP) architecture used in AI systems. ### Source excerpt All popular AI systems that you see today are made up of basic computing units called Neurons or Perceptrons. These connect to form a network called a Neural network that performs various complex computations. ## Testing M2 and M3 Interfaces to Understand the Impact of Visual Changes DevFeed: [Testing M2 and M3 Interfaces to Understand the Impact of Visual Changes]() Original publisher: [Read original article]() Published: 2024-05-13T13:00:00Z Content type: article Language: en Sources: [Material.io - Material Design]() Topics: [ui](), [interfaces]() Tags: [interfaces](), [ui](), [understand]() ### AI overview The article describes testing M2 and M3 interfaces to understand the impact of visual changes. ### Source excerpt How we tested M2 and M3 interfaces to understand the impact of visual changes ## Defining a Distinguished Engineer DevFeed: [Defining a Distinguished Engineer]() Original publisher: [Read original article]() Published: 2019-03-21T15:09:26Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [Learning]() Tags: [leadership](), [technical](), [thing](), [understand]() ### AI overview The author proposes a model of a distinguished engineer or technical fellow centered on technical leadership, broad system understanding, continuous learning, and empowering colleagues. The article is motivated by the demoralizing effect of poorly behaved senior leaders. ### Source excerpt I learned a lot about myself and the way big companies are organized over the past year or so. I had mentioned a bit in a previous blog post and podcast about "the N + 1 shithead problem" (from Bryan Cantrill's talk on leadership). To reiterate, the "N +1 shithead problem" occurs when you are demotivated by seeing people who are a level above you behave poorly, or more bluntly when they behave like a shithead. I know from experience what a huge demotivator this is and after talking to several other folks I realized this is quite common. When faced with this demotivator, I found myself thinking "why would I want to be at their level, when once I get there I'll just be one amongst the dipshits." It's a horrible feeling to have and I'd love to have a model that resembles what I think of as a distinguished engineer or technical fellow. In this post I will define what it means to me to be a distinguished engineer or technical fellow and maybe others that agree will modify their ladders to incentivize people to resemble these qualities. Technical Leader The first thing people think of when they think of a distinguished engineer is that they are a technical leader. I fully agree. A technical leader can understand all parts of a system. They can also be dropped into a new system and pick up the way it is architected and designed with relative ease. I think this is an important distinction to make. It's good to be an expert in a field, but only being an expert is limiting. It's also important to understand the full picture and that takes general knowledge. I think having a general knowledge of things outside your area of expertise is key if you choose to gain expertise in something. Value learning A technical leader can always realize that there is more to learn. One cannot be an expert in everything and you can have a general knowledge of most things without fully understanding the details within. A technical leader can always strive to continue to learn and persuade others ## Craft CMS 3 Orientation Guide - Welcome! DevFeed: [Craft CMS 3 Orientation Guide - Welcome!]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2018-07-31T20:14:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [PHP](), [API](), [Back end](), [Front end](), [GraphQL](), [Tailwind CSS]() Tags: [apis](), [awesome](), [backend](), [building](), [cms](), [craft](), [frontend](), [graphql](), [guide](), [help](), [insights](), [orientation](), [philosophy](), [php](), [stuff](), [tailwind-css](), [understand](), [we-ll](), [you-re]() ### AI overview An orientation guide to Craft CMS 3 explains its content-authoring model, PHP and Yii2 foundation, APIs, server-rendered frontend, headless options, and flexible approach to website structure and styling. ### Source excerpt This is your orientation guide if you're new to Craft CMS 3! We'll help you understand the Craft philosophy of building awesome stuff ## Why Descriptive Variable Names Improve Code Readability DevFeed: [Why Descriptive Variable Names Improve Code Readability]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2017-10-17T09:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [Variable](), [Code](), [Programming](), [Computer science]() Tags: [clean-code](), [code](), [computer-science](), [developer](), [programming](), [understand](), [variable](), [writing]() ### AI overview This article explains why descriptive variable names make code easier for humans to read and maintain. It contrasts short, cryptic names with clearer names and notes that naming requires judgment rather than automatically improving code. ### Source excerpt While you are writing your code, the most important thing to have in mind is that you are writing your code first and foremost for humans to understand, and secondly for a machine to interpret. ## Twig Processing Order & Scope DevFeed: [Twig Processing Order & Scope]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-11-28T15:31:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Template](), [Front end](), [Code](), [Content Management System]() Tags: [code](), [frontend](), [important](), [insights](), [language](), [little-known](), [order](), [processing](), [scope](), [templates](), [templating](), [twig](), [understand]() ### AI overview This tutorial explains Twig's processing order and variable scope. It describes how extended, included, and block templates are processed, and why variables defined in one template context are not available in others. ### Source excerpt The Twig templating language has a little-known processing order & scope that is important to understand ## Introduction to Information Security Concepts for System Administrators DevFeed: [Introduction to Information Security Concepts for System Administrators]() Original publisher: [Read original article]() Published: 2014-12-24T20:17:25Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Security](), [Requirements]() Tags: [infosec](), [introduction](), [security](), [sysadmins](), [understand]() ### AI overview An introduction to general information security concepts for system administrators, explaining the reasons behind some security requirements imposed on them. ### Source excerpt An introduction to general infosec concepts, hoping to help sysadmins better understand the reasons behind some of the security requirements imposed on them. ## Workshop with blindfolded lunch DevFeed: [Workshop with blindfolded lunch]() Original publisher: [Read original article]() Author: Lotte Johansen Published: 2014-11-19T18:00:00Z Content type: article Language: en Sources: [Finn.no]() Topics: [Accessibility](), [User interface design](), [Requirements]() Tags: [accessibility](), [interaction](), [requirements](), [understand](), [user](), [workshop]() ### AI overview FINN describes an accessibility workshop held with the Norwegian Association of the Blind and Partially Sighted. Developers, designers, and product owners learned about accessibility requirements and experienced a blindfolded lunch intended to build understanding of users with visual impairments. ### Source excerpt Workshop with blindfolded lunch in cooperation with The Norwegian Association of the Blind and Partially Sighted (NABP) At FINN a grassroots group of developers and interaction designers launched an initiative to bring up awareness of accessibility. The law of accessibility was introduced July 1st 2014 and m.finn.no is covered by that law because of its major design changes. The Accessibility group in FINN wanted to convey the same message as the NABP; caring for people with disabilities when we build our services, hoping it lead to better user experiences for all. Wednesday November 19th, FINN arranged an accessibility workshop in cooperation with NABP. About 30 developers, designers and product owners attended the keynote by Stein Erik Skotkjerra who is blind and by Kristoffer Lium who is partially sighted. It was an eye-opener for people to see how these two who represented a fairly large group of blind and visually impaired, orients themselves on finn.no. A smaller group of developers and interaction designers attended the whole workshop. We got an introduction to the law of accessibility and the requirements in practice. Stein Erik and Kristoffer both emphesized that the most important is to make sites user friendly; not the law itself. If we think of people with disabilities when we develop finn.no, it will lead to a better site for everyone. Even for those who have a headache one day or are sitting on a bumpy bus while browsing finn.no. The highlight of the day was perhaps "blindfolded lunch". All workshop participants put on ski goggles that were spray painted black so no-one could see anything. Then they were ushered around before being led to a prepared lunch table. The canteen staff from FINN helped to create an exciting lunch with different samples in small cups. It was a challenge to know where the food was, to spread the butter on the bread, and simply to understand what we were eating. At the end of the day the workshop participants tried out various