# approach Published articles for approach. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Improve Coding Interview Performance with Personal Stories and Targeted Technical Practice DevFeed: [How to Improve Coding Interview Performance with Personal Stories and Targeted Technical Practice]() Original publisher: [Read original article]() Author: Brian Jenney Published: 2026-03-24T15:05:22Z Content type: opinion Language: en Sources: [Brian Jenney]() Topics: [coding](), [Development](), [Code](), [JavaScript]() Tags: [approach](), [career](), [coding](), [interviews](), [javascript](), [manager](), [recursion](), [software-engineer]() ### AI overview The author describes struggling with coding interviews despite being able to do the underlying job. They recommend cataloging personal work stories for recurring behavioral questions and focusing practice on recurring technical gaps. ### Source excerpt Five years ago, during an interview for a senior dev role, I had a panic attack. ## Taming chaos is a learnable skill DevFeed: [Taming chaos is a learnable skill]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-03-11T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Software Engineering](), [engineering-culture](), [Low-Code / Internal Tools]() Tags: [approach](), [chaos](), [engineering](), [exceptions](), [internal-tools](), [operations](), [software-engineering](), [startup]() ### AI overview The article argues that handling interruptions, operational surprises, exceptions, and changing priorities is a learnable software-engineering skill. It recommends owning system problems, managing scope and tradeoffs, validating quality requirements, and maintaining a long-term vision despite short-term disruption. ### Source excerpt How you approach software engineering makes it harder or easier to handle interruptions and other chaos. Writing a behavioral interview made me realize this is a learnable skill! ## A Supply-Chain Attack on Nix and the Approach to Solving It DevFeed: [A Supply-Chain Attack on Nix and the Approach to Solving It]() Original publisher: [Read original article]() Published: 2025-10-30T00:00:00Z Content type: article Language: en Sources: [Garnix Blog]() Topics: [Nix]() Tags: [approach](), [supply-chain]() ### AI overview The article discusses a supply-chain attack on Nix and describes the publisher's approach to solving it. ### Source excerpt A supply-chain attack on Nix, and our approach to solving it. ## Using Provocations to Shake the Status Quo DevFeed: [Using Provocations to Shake the Status Quo]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2025-07-22T16:23:11Z Content type: opinion Language: en Sources: [New York Times]() Topics: [Users](), [format](), [context]() Tags: [approach](), [design](), [engineering](), [figma](), [photography](), [process](), [recipe](), [ux-design](), [visual-hierarchy](), [visualization]() ### AI overview A case study of how NYT Cooking used high-fidelity design provocations to rethink recipe cards. The approach prioritized photography, flexible recipe information, a modernized format, and a more streamlined evaluation process while keeping the project scope controlled. ### Source excerpt The bold approach NYT Cooking used to define a strategy for recipe cards.Illustration by Ben Denzer By Jayne Lee In The New York Times Cooking, "cards," or the containers that represent our content, are the first impression of our brand. They're the window into our recipes and users rely on them to evaluate and choose what to cook. NYT Cooking users are particularly attracted to our appetizing food photos. In every research session, participants get distracted by a delicious-looking dish while answering the moderator's questions. People tend to browse with their stomachs first and then see if the recipe specifications meet their personal criteria (For example, do I have enough time to cook this?). A problem we encountered: our beautiful photography was muddied by the page's gray background. The white card containers sitting on top of the gray page forced your eyes to focus on the container instead of the photo. The visual hierarchy was at odds with the preferred reading and browsing order of our audience: photo first, then recipe information. Recipe information varies, so the card needs to afford that variability. Using containers forced us to keep our cards the same height, resulting in unnecessary whitespace. Since the cards were so tall, this limited the amount of recipes a user could see at once, increasing the time users scanned for recipes. We needed to highlight our photography, modernize the format and streamline the recipe evaluation process. While designing solutions, I realized that I had more questions than answers. Answering each question would have significantly bloated the project scope. Some examples were: What order of recipe information is most helpful when deciding between recipes? Are recipe bylines important? Which presentation of ratings is more effective? Because the priority was to update the format rather than improve comprehension, and to avoid bloating the scope of the project, I started with design provocations over design specs. Because ## Why We Don't Call Them SDRs Anymore: Inside Teleport's Take on Modern Sales Development DevFeed: [Why We Don't Call Them SDRs Anymore: Inside Teleport's Take on Modern Sales Development]() Original publisher: [Read original article]() Author: amanda.pessica@goteleport.com (Amanda Pessica) Published: 2025-05-16T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [Job](), [account](), [meetings]() Tags: [account](), [ai](), [approach](), [company](), [enterprise](), [hiring](), [messaging](), [sales](), [strategy]() ### AI overview Teleport explains why it replaced the SDR title with Account Development Representative, arguing that modern enterprise sales development requires personalized, research-driven outreach, brand knowledge, strategic persistence, and an updated hiring process. ### Source excerpt Discover why Teleport is moving beyond the SDR title--and how our modern approach to sales development is reshaping hiring, outreach, and success. ## System Design Interview Framework DevFeed: [System Design Interview Framework]() Original publisher: [Read original article]() Author: Evan King Published: 2024-11-19T21:39:41Z Content type: tutorial Language: en Sources: [Evan King]() Topics: [Requirements](), [structure](), [systems](), [Framework](), [client]() Tags: [approach](), [framework](), [interview](), [requirements](), [structure](), [system-design-interview](), [systems]() ### AI overview A practical framework for system design interviews that emphasizes delivering a working system. It recommends spending about five minutes clarifying and prioritizing functional and non-functional requirements, with examples involving Twitter and a cache. ### Source excerpt From the co-founder of www.hellointerview.com The easiest way to sabotage your chances of getting an offer in your system design interview is to fail to deliver a working system. This is the most common reason that mid-level candidates fail these interviews. While a firm structure to your approach is important and your interviewer is not trained specifically to assess you on your delivery (often this gets bucketed into "communication"), in practice we've seen many candidates that perform significantly better by following a structure which both keeps them from getting stuck and ensures they deliver a working system. Requirements (~5 minutes) The goal of the requirements section is to get a clear understanding of the system that you are being asked to design. To do this, we suggest you break your requirements into two sections. 1) Functional Requirements Functional requirements are your "Users/Clients should be able to..." statements. These are the core features of your system and should be the first thing you discuss with your interviewer. Oftentimes this is a back and fourth with your interviewer. Ask targeted questions as if you were talking to a client, customer, or product manager ("does the system need to do X?", "what would happen if Y?") to arrive at a prioritized list of core features. For example, if you were designing a system like Twitter, you might have the following functional requirements: Users should be able to post tweets Users should be able to follow other users Users should be able to see tweets from users they follow A cache meanwhile might have requirements like: Clients should be able to insert items Clients should be able to set expirations Clients should be able to read items Keep your requirements targeted! The main objective in the remaining part of the interview is to develop a system that meets the requirements you've identified -- so it's crucial to be strategic in your prioritization. Many of these systems have hundreds of features, but it ## Transparency, autonomy, responsiveness, and education: How the Aha! engineering team works DevFeed: [Transparency, autonomy, responsiveness, and education: How the Aha! engineering team works]() Original publisher: [Read original article]() Published: 2024-10-28T00:00:00Z Content type: opinion Language: en Sources: [Aha! Engineering Blog]() Topics: [Programming](), [Self-organizing Team](), [Agile](), [pair\_programming](), [Code](), [App]() Tags: [agile](), [approach](), [engineering](), [meetings](), [pair-programming](), [product](), [programming](), [security](), [team](), [teams](), [transparency](), [work]() ### AI overview The article explains how Aha!'s engineering team combines individual, pair, and team-based work. Engineers present their work in weekly meetings, retain ownership of code, and share knowledge across the organization. Small agile teams align with product areas and infrastructure, while rotating support responsibilities provide broader exposure. Product managers, designers, and engineers prioritize and scope work collaboratively. ### Source excerpt Organizations have many different ways to approach how teammates write code. You have individual silos, pair programming, team-based work, and black box interfaces where you have no idea how the other team is structured. We use a mix of these approa ## A Contextual and Dynamic Approach to Designing Command-Line Interfaces DevFeed: [A Contextual and Dynamic Approach to Designing Command-Line Interfaces]() Original publisher: [Read original article]() Published: 2023-11-17T00:00:00Z Content type: opinion Language: en Sources: [Garnix Blog]() Topics: [Command-line interface](), [interfaces]() Tags: [approach](), [command](), [command-line](), [interfaces]() ### AI overview The article discusses a contextual and dynamic approach to designing command-line interfaces. ### Source excerpt A more contextual and dynamic approach to designing command-line interfaces. ## Computing Percentages Easier DevFeed: [Computing Percentages Easier]() Original publisher: [Read original article]() Published: 2023-09-05T21:47:37Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [math](), [Computing]() Tags: [approach](), [arithmetic](), [math](), [mathematics](), [numbers](), [puzzle](), [scaling]() ### AI overview A math tutorial explains mental percentage calculations using the fact that x% of y equals y% of x. It presents several approaches, including choosing the easier percentage, multiplying first and dividing by 100, scaling from 1%, and splitting the denominator. ### Source excerpt Problem: Compute 16% of 25 in your head. Solution: 16% of 25 is equivalent to 25% of 16, which is clearly 4. This is true for all numbers: $x\%$ of $y$ is always equal to $y\%$ of $x$. The first one is $\frac{x}{100} y$ and the second is $\frac{y}{100}x$, and because multiplication is commutative and associative, both are equal to $(x \cdot y) / 100$. You can pick the version that is easiest. ## Architecture and Gardening for Startups DevFeed: [Architecture and Gardening for Startups]() Original publisher: [Read original article]() Published: 2021-06-03T00:00:00Z Content type: opinion Language: en Sources: [Radek Pazdera]() Topics: [Framework](), [App](), [Software](), [coding]() Tags: [approach](), [architecture](), [building-products](), [discovery](), [experiments](), [features](), [founders](), [product](), [software](), [startups](), [strategy]() ### AI overview The article applies George R. R. Martin's distinction between architects and gardeners to startup product development. It argues that founders need an architect mindset before launch to form and build a solution, then a gardener mindset after launch to discover what works through listening, tinkering, customer conversations, and experiments instead of focusing only on adding features. ### Source excerpt What George R. R. Martin taught me about building products ## Effective Kotlin Item 36: Prefer composition over inheritance DevFeed: [Effective Kotlin Item 36: Prefer composition over inheritance]() Original publisher: [Read original article]() Published: 2021-04-25T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Inheritance](), [Object-oriented programming (OOP)](), [Kotlin](), [reuse](), [superclass]() Tags: [approach](), [behavior](), [hierarchy](), [inheritance](), [kotlin](), [object](), [oop](), [reuse](), [superclass](), [workshop-learning-programming]() ### AI overview The article argues that inheritance should primarily model a clear "is a" relationship and can be problematic when used mainly for code extraction or reuse. It presents class composition as a safer and more explicit alternative, while acknowledging that composition requires additional code. ### Source excerpt Years of OOP made us overuse inheritance. Instead, we should more often use a composition that is safer and more explicit. More often, but not always... ## Sociotechnical Approach to Cyber Security DevFeed: [Sociotechnical Approach to Cyber Security]() Original publisher: [Read original article]() Author: Adam Published: 2020-07-24T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [context]() Tags: [approach](), [cyber](), [post](), [security](), [technical](), [uk]() ### AI overview This post highlights a recent UK NCSC article by Helen L. on sociotechnical approaches to cybersecurity, including the context of these approaches, the RISCS Institute, and a related problem book. ### Source excerpt A recent post from Helen L. of the UK's NCSC, A sociotechnical approach to cyber security, shares the context of socio-technical approaches. ## Flat Multi-Environment Config for Craft CMS 3 DevFeed: [Flat Multi-Environment Config for Craft CMS 3]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-02-29T15:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [.env](), [Environment Variables](), [configuration](), [Development]() Tags: [aliases](), [api-keys](), [approach](), [article](), [cms](), [config](), [configs](), [craft](), [database](), [docker](), [environment](), [environment-variables](), [file](), [files](), [flat](), [git](), [heroku](), [insights](), [multi-environment](), [need](), [presents](), [secrets](), [sorts](), [variables]() ### AI overview A tutorial on configuring Craft CMS 3 across development, staging, and production environments using aliases, environment variables, .env files, and configuration files. It presents a flat configuration approach and discusses keeping environment-specific credentials and secrets separate from source code and databases. ### Source excerpt Multi-environment configs for Craft CMS are a mix of aliases, environment variables, and config files. This article sorts it all out, and presents a flat config file approach ## Unspoken Assumptions Underlying OO Design Maxims DevFeed: [Unspoken Assumptions Underlying OO Design Maxims]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2019-12-24T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Object-oriented programming (OOP)](), [Kotlin](), [Code]() Tags: [approach](), [change](), [complexity](), [object-oriented](), [oop]() ### AI overview The article argues that many object-oriented design maxims implicitly assume developers can predict how a system will change. It questions whether adding complexity to support uncertain future changes is justified, using the open-closed principle and polymorphism as examples. ### Source excerpt For Atomic Kotlin, I've been struggling with an "atom" (very small chapter) during the last couple of months. It's on object-oriented design, and it brought up a lot of feelings I've had for quite awhile about some of the various maxims and design guidelines that have appeared in recent decades, since OO became mainstream. I couldn't quite put my finger on what bothered me about these design ideas. Then @codingunicorn did it for me by writing a post called Flexible code considered harmful. ## How to remove duplicate lines from files preserving their order DevFeed: [How to remove duplicate lines from files preserving their order]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2019-05-16T08:30:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [Script](), [file]() Tags: [approach](), [awk](), [bash](), [featured](), [file](), [files](), [how-to](), [linux](), [programming](), [scripts]() ### AI overview A tutorial explains how to remove duplicate lines from a text file with awk while preserving their original order. It breaks down the associative array, line-occurrence tracking, negation, post-increment behavior, and why other approaches may not preserve order. ### Source excerpt Suppose you have a text file and you need to remove all of its duplicate lines. TL;DR To remove the duplicate lines preserving their order in the file use: awk '!visited[$0]++' your_file > deduplicated_file How it works The script keeps an associative array with indices equal to the unique lines of the file and values equal to their occurrences. For each line of the file, if the line occurrences are zero then it increases them by one and prints the line, otherwise it just increases the occurrences without printing the line. I was not familiar with awk and I wanted to understand how is this accomplished with such a short script (awkward). I did my research and here is what is going on: the awk "script" !visited[$0]++ is executed for each line of the input file visited[] is a variable of type associative array (a.k.a. Map). We don't have to initialize it, awk will do this for us the first time we access it. the $0 variable holds the contents of the line currently being processed visited[$0] accesses the value stored in the map with key equal to $0 (the line being processed), a.k.a. the occurrences (which we set below) the ! negates the occurrences value: In awk, any nonzero numeric value or any nonempty string value is true By default, variables are initialized to the empty string, which is zero if converted to a number That being said: if visited[$0] returns a number greater than zero, this negation is resolved to false. if visited[$0] returns a number equal to zero or an empty string, this negation is resolved to true. the ++ operation increases the variable's value (visited[$0]) by one. If the value is empty, awk converts it to 0 (number) automatically and then it gets increased. Note: the operation is executed after we access the variable's value. Summing up, the whole expression evaluates to: true if the occurrences are zero/empty string false if the occurrences are greater than zero awk statements consist of a pattern-expression and an associated action. ) Original publisher: [Read original article]() Published: 2015-04-03T07:00:00Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [Test-driven development](), [Android](), [Development](), [Code](), [Software]() Tags: [android](), [api](), [approach](), [architecture](), [code](), [development](), [requirements](), [software](), [test]() ### AI overview The author describes adopting a test-first approach in an Android client project and explains an unexpected benefit: writing tests to define requirements encourages more deliberate architectural decisions. Tests enable designing an API, validating it with a mocked implementation, and identifying code that is not properly encapsulated. ### Source excerpt I've finally done it. In the latest client project I'm working on I've decided to take a test first approach. I've been wanting to experience Test Driven Development on Android for years, but have never felt comfortable enough to really commit. After reading through Kent Beck's book and checking out Corey Latislaw's latest book, I decided I was ready to make the leap. I'll write some more later about my experience, reactions, and what I've learned, but today I wanted to share a slightly unexpected benefit. ## Google's Hybrid Approach to Research DevFeed: [Google's Hybrid Approach to Research]() Original publisher: [Read original article]() Published: 2012-06-24T00:00:00Z Content type: article Language: en Sources: [Peter Norvig]() Topics: [Google](), [communications]() Tags: [approach](), [article](), [communications](), [engineering](), [google](), [research]() ### AI overview An article in Communications of the ACM describes Google's hybrid approach to research across Google Research and engineering as a whole. ### Source excerpt An article printed in the Communications of the ACM describing Google's research, both within Google Research and within Engineering as a whole. Alfred Spector, Peter Norvig and Slav Petrov.