# problems Published articles for problems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Nitpicking in code reviews wastes time DevFeed: [Nitpicking in code reviews wastes time]() Original publisher: [Read original article]() Author: Dan Lew Published: 2026-09-01T13:00:13Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [Code](), [code productivity](), [Software Engineering](), [Development]() Tags: [bugs](), [code](), [code-reviews](), [development](), [features](), [problems](), [refactor](), [software-development](), [time]() ### AI overview An opinion article argues that nitpicking minor issues in code reviews wastes time. Small problems usually have limited impact, may never cause trouble, and can often be fixed later, so review effort should prioritize major problems, bugs, and features. ### Source excerpt I once wrote about how I've stopped nit-picking in code reviews, which improved the signal-to-noise ratio and helped everyone get along better. I'm back with a third reason to ditch the practice: nit-picking wastes time. By definition, nitpicks are about minor problems: ## TBM 434: How Maps Can Hide Problems DevFeed: [TBM 434: How Maps Can Hide Problems]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-08-01T09:13:07Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [context](), [structure]() Tags: [design](), [mapping](), [maps](), [organizations](), [ownership](), [problems](), [product](), [reporting](), [silos](), [structure](), [technology]() ### AI overview The article argues that organizational maps can conceal incoherence when strategy, structure, technology, incentives, goals, ownership, teams, and funding do not align. It contrasts coherent organizations, where context transfers across map layers, with incoherent organizations, where people must repeatedly reorient and translate. ### Source excerpt If what you are mapping is incoherent, don't fall in love with the map (or your personal ability to navigate with it). ## Operational Readiness: The Review That Catches Problems DevFeed: [Operational Readiness: The Review That Catches Problems]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-05-25T00:00:00Z Content type: tutorial Language: en Sources: [Sridhar Rajarao]() Topics: [Development](), [incident](), [Artificial Intelligence]() Tags: [on-call](), [operational](), [ops](), [problems](), [production](), [reliability](), [sre](), [validation](), [verification]() ### AI overview An operational readiness review is useful only when checklist items are backed by evidence and verified before a service launches. The article explains common failure modes, recommends attaching artifacts to each item, and describes AI applications for evidence gathering, gap detection, and summary drafting while keeping the final readiness decision with human reviewers. ### Source excerpt A short, verifiable checklist for production launches. What to ask, why ORRs become theater, and where AI helps. ## Solving impossible problems DevFeed: [Solving impossible problems]() Original publisher: [Read original article]() Published: 2025-09-17T00:00:00Z Content type: tutorial Language: en Sources: [Aha! Engineering Blog]() Topics: [coding](), [Extension](), [API](), [Security](), [Back end]() Tags: [api](), [backend](), [build](), [challenges](), [extension](), [how-to](), [problems](), [security]() ### AI overview An engineering article describes how to approach software features that seem impossible to build. Using the Aha! Develop TestRail extension as an example, it explains how changing controllable constraints can make difficult problems manageable. ### Source excerpt If you've been working on software for any reasonable length of time, you might have had an experience like this: You're looking at a feature, and you have no idea how to build it. You have the context and understanding you need. But it's all pointi ## Reduce latency and speed up your Temporal Workflows DevFeed: [Reduce latency and speed up your Temporal Workflows]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2025-02-12T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Latency](), [reliability](), [systems](), [Cloud](), [Network](), [Server](), [Transactions]() Tags: [cloud](), [durability](), [e-commerce](), [latency](), [measuring](), [optimizing](), [payment](), [problems](), [reduce](), [speed](), [system](), [techniques](), [temporal-concepts](), [workflows]() ### AI overview This tutorial explains how to reduce latency in Temporal workflows used by interactive applications while preserving durability and reliability. It identifies workflow startup, task scheduling, network calls, and activity execution as contributors to response time. ### Source excerpt Latency can be a challenge when responsiveness matters. The good news is, there are ways to make your workflows snappier without sacrificing durability. ## Tabletop Games Based on Math Problems DevFeed: [Tabletop Games Based on Math Problems]() Original publisher: [Read original article]() Published: 2024-03-09T04:06:19Z Content type: article Language: en Sources: [Jeremy Kun]() Topics: [math](), [Mathematics](), [Math and Logic](), [Hugo](), [LaTeX](), [WordPress]() Tags: [card-games](), [color](), [games](), [math](), [mathematics](), [problems](), [projective-plane](), [set](), [tabletop-games](), [unique](), [value](), [vector]() ### AI overview A short list of tabletop games whose mechanics are directly based on nontrivial mathematical structures or problems. It discusses games including SET and Spot It!, along with related questions in finite geometry, vector spaces, and combinatorics. ### Source excerpt There's a family of tabletop games that are based directly on a nontrivial mathematics problem. As a casual and fun way to inaugurate my new blog (migrated from Wordpress to Hugo, after my work on getting better LaTeX mathmode support in Hugo), I thought I'd write a short listicle about them, so that I have a place to add more as I find them, as well as give the shortest canonical description of the associated math problem. ## Leveraging Python Standard Library via WebAssembly DevFeed: [Leveraging Python Standard Library via WebAssembly]() Original publisher: [Read original article]() Author: Tim McCallum Published: 2024-01-10T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Python](), [WebAssembly](), [Library](), [Web]() Tags: [complex](), [leveraging](), [libraries](), [problems](), [python](), [simplify](), [standard](), [standard-library](), [web](), [webassembly]() ### AI overview The article explores how Python's extensive standard library, compiled to WebAssembly, can simplify solving complex mathematical problems over the web. ### Source excerpt Explore how Python's extensive libraries, when compiled to WebAssembly, simplify solving complex mathematical problems over the web ## How to fix the invalid JDK problem on Electric Eel DevFeed: [How to fix the invalid JDK problem on Electric Eel]() Original publisher: [Read original article]() Published: 2023-01-20T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [Android Studio](), [Android](), [Gradle]() Tags: [android](), [android-studio](), [gradle](), [how-to](), [jdk](), [location](), [other](), [problems](), [terminal](), [updating]() ### AI overview This tutorial explains how to fix an invalid JDK configuration after updating Android Studio to Electric Eel. It recommends checking the project's Gradle JDK setting and updating the environment variable if it still points to the old embedded JDK location. ### Source excerpt When updating Android Studio to Electric Eel, the location of the embedded JDK is changing. ## International Women in Engineering Day: reflections from our VP of Engineering, Myra Fulton DevFeed: [International Women in Engineering Day: reflections from our VP of Engineering, Myra Fulton]() Original publisher: [Read original article]() Author: Skyscanner Engineering Published: 2022-06-23T08:08:17Z Content type: article Language: en Sources: [Stories by Skyscanner Engineering on Medium]() Topics: [Software Engineering](), [Development](), [Testing](), [bug](), [Support]() Tags: [bug](), [career](), [documentation](), [engineering](), [engineering-leadership](), [problems](), [software](), [software-development](), [testing](), [vp-of-engineering](), [women-in-tech]() ### AI overview An interview with Skyscanner VP of Engineering Myra Fulton about her path from hospitality studies to software engineering leadership. She discusses lessons from support and mortgage development roles, including the importance of documentation, code quality, testing, and the real-world impact of software defects. ### Source excerpt Skyscanner VP of Engineering, Myra Fulton She is Skyscanner's most senior female engineer, but Myra Fulton's career as she knows it almost didn't happen -- a last-minute decision to change her university course from hospitality to engineering set her on a completely different path to the one she'd intended. This International Women In Engineering Day, we sat down with Myra to hear her about her journey to the top. Myra, what lead you to engineering originally -- was it always the plan? Engineering was very much not the plan -- I wanted to get into hospitality, and had dreams of running a hotel group. But fate -- in the form of an amazing teacher called Mr Haggerty -- intervened. He convinced me to take up computer science and basically changed the course of my career. He then did the same for a fellow engineer here at Skyscanner, Mhairi McClair several years later! So thank you, Mr Haggerty. The way Mr Haggerty taught computer science brought the subject to life -- I loved how you could solve problems in really interesting ways, and doing that with technology was exciting. It suited my analytical brain, so I decided to switch my uni course from Hospitality Management to Computer Studies. What happened next -- what was your journey to Skyscanner? I graduated with a first class honours spent a year's placement with IBM. After graduating, I got on the grad programme with a bank and spent nine years there. My career started in a number of first and second line support focused roles where I learned the importance of good handover documentation and run-books. I then got the privilege to lead the mortgage development team where I started to learn the other side of software development. It was during my time there that said bank had announced they'd undercharged people for mortgages due to a bug in services. While I wasn't involved in that bug, it really taught me the fragility of software and the importance of the quality of code, of testing and of the impact that can be made on ## How Managerial Authority Can Undermine Developer Empowerment and Productivity DevFeed: [How Managerial Authority Can Undermine Developer Empowerment and Productivity]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2022-02-04T08:00:42Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Software](), [Job]() Tags: [article](), [developers](), [leadership](), [manager](), [managerial-roles](), [motivation](), [performance](), [power](), [problems](), [product](), [productivity](), [pull-request](), [team]() ### AI overview This opinion article argues that managers who rely too heavily on authority, including micromanaging approvals and imposing their own ideas, can disempower developers and reduce engagement, performance, and product delivery. It advocates servant leadership through clarity, enablement, and team empowerment. ### Source excerpt More power, more problems ## Kotlin Multiplatform Focuses on Shared Business Logic Rather Than UI DevFeed: [Kotlin Multiplatform Focuses on Shared Business Logic Rather Than UI]() Original publisher: [Read original article]() Published: 2019-08-15T16:45:41Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [business logic](), [Mobile]() Tags: [code-sharing](), [kotlin-multiplatform](), [mobile](), [multiplatform](), [problems]() ### AI overview The article argues that Kotlin Multiplatform is best suited to sharing business logic between Android and iOS while allowing platform-specific UIs. It contrasts this approach with end-to-end frameworks such as Xamarin, Flutter, and React Native, citing ecosystem flexibility and access to existing platform libraries as advantages. ### Source excerpt Unlike Xamarin, Flutter or React Native, Kotlin Multiplatform does not live within its own ecosystem, which is why it's powerful and flexible dev framework. ## Zen and the Art of Craft CMS Log File Reading DevFeed: [Zen and the Art of Craft CMS Log File Reading]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-07-22T05:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Logging](), [debugging](), [Command-line interface](), [Development]() Tags: [black](), [cli](), [contain](), [debugging](), [diagnose](), [file](), [files](), [forensic](), [information](), [insights](), [learn](), [let-s](), [like](), [logging](), [php](), [precious](), [problems](), [reading](), [recording]() ### AI overview A tutorial on reading Craft CMS log files to diagnose problems, including how Craft separates web, 404, console, queue, and PHP error logs in the storage/logs/ directory. It also discusses using the Debug Toolbar to search, sort, and filter logs during local debugging. ### Source excerpt Like a black box recording, log files contain precious forensic information for when you have to diagnose problems. Let's learn the art of reading them ## Using VueJS + GraphQL to make Practical Magic DevFeed: [Using VueJS + GraphQL to make Practical Magic]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2018-08-27T22:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [GraphQL](), [vuejs](), [Content Management System](), [Front end](), [JavaScript](), [axios](), [Bootstrap](), [Jamstack]() Tags: [auto-complete](), [axios](), [bootstrap](), [craft](), [everyday](), [form](), [graphql](), [headless](), [insights](), [jamstack](), [javascript](), [like](), [magic](), [practical](), [problems](), [saving](), [searching](), [solve](), [submission](), [using](), [vuejs]() ### AI overview A practical tutorial showing how to use VueJS and GraphQL with a headless Craft CMS backend to implement auto-complete search and save contact-form submissions. It introduces the frontend and backend tooling used in the examples, including Axios, Bootstrap 4, Craft CMS, and CraftQL. ### Source excerpt Make some practical magic with VueJS + GraphQL to solve everyday problems like auto-complete searching and form submission saving with a headless Craft CMS server ## NP-hard does not mean hard DevFeed: [NP-hard does not mean hard]() Original publisher: [Read original article]() Published: 2017-12-29T13:30:23Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Algorithms, Complexity](), [Algorithms](), [Programming]() Tags: [algorithm](), [algorithms](), [boolean](), [completeness](), [complexity-theory](), [logic](), [mario](), [mathematics](), [np-completeness](), [np-hard](), [problems](), [real-world](), [regular-languages](), [solve](), [time]() ### AI overview This article explains that NP-hardness is a worst-case mathematical property, not a claim that a problem is always difficult for humans or algorithms. Using Super Mario as an example, it shows how game levels can encode boolean logic and why solving the game in full generality would encompass hard computational problems, while ordinary real-world levels may still be solvable efficiently. ### Source excerpt When NP-hardness pops up on the internet, say because some silly blogger wants to write about video games, it's often tempting to conclude that the problem being proved NP-hard is actually very hard! "Scientists proved Super Mario is NP-hard? I always knew there was a reason I wasn't very good at it!" Sorry, these two are unrelated. NP-hardness means hard in a narrow sense this post should hopefully make clear. After that, we'll explore what "hard" means in a mathematical sense that you can apply beyond NP-hardness to inform your work as a programmer. ## How Ada Lovelace solved problems DevFeed: [How Ada Lovelace solved problems]() Original publisher: [Read original article]() Author: Graham King Published: 2015-12-11T05:02:00Z Content type: article Language: en Sources: [Graham King]() Topics: [Ada](), [Mathematics]() Tags: [ideas](), [mathematics](), [problems](), [program](), [puzzle](), [solve]() ### AI overview This article recounts how Ada Lovelace worked on a mathematics problem related to the Analytical Engine and documented what is described as the first known computer program for calculating Bernoulli numbers. When she became stuck, she went horseback riding and expected the problem to become clearer later. ### Source excerpt Ada Lovelace: Debugging by horseback since 1843. ## A Proofless Introduction to Information Theory DevFeed: [A Proofless Introduction to Information Theory]() Original publisher: [Read original article]() Published: 2015-02-16T09:00:00Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Encoding](), [digital]() Tags: [channel](), [coding-theory](), [communication](), [compression](), [digital](), [encoding](), [entropy](), [error](), [error-correction](), [example](), [explain](), [hamming](), [independent](), [information](), [information-theory](), [kolmogorov-complexity](), [language](), [markov](), [mathematics](), [messages](), [models](), [probabilistic-method](), [problems](), [shannon](), [theory]() ### AI overview A proofless introduction to information theory explains noiseless and noisy communication problems, encoding schemes, entropy, and how entropy differs from Kolmogorov complexity. ### Source excerpt There are two basic problems in information theory that are very easy to explain. Two people, Alice and Bob, want to communicate over a digital channel over some long period of time, and they know the probability that certain messages will be sent ahead of time. For example, English language sentences are more likely than gibberish, and "Hi" is much more likely than "asphyxiation." The problems are: Say communication is very expensive. ## ReactOS investigates SHFileOperation and considers an IFileOperation implementation DevFeed: [ReactOS investigates SHFileOperation and considers an IFileOperation implementation]() Original publisher: [Read original article]() Published: 2014-10-19T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [file](), [implementation](), [function](), [dialog](), [Windows](), [Code]() Tags: [copy](), [file](), [files](), [free](), [implementation](), [interface](), [microsoft](), [moving](), [open-source](), [operations](), [os](), [problems](), [react](), [reactos](), [tests](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS developer reports testing SHFileOperation by moving, copying, and deleting folder structures, but could not reproduce the suspected file-writing problem. The article then examines whether to fix SHFileOperation directly or implement it around IFileOperation, including Microsoft's internal approach. ### Source excerpt Hello again! As I mentioned in the last report, I had been writing tests to find the problems in SHFileOperation. All I knew was that in some situations it would end without fully writing some file, so I wrote tests moving, copying and deleting a folder structure, and comparing the copy with the original. I tried with empty files first, then with files of random sizes, then with really big files, and also with a lot of files of relatively small size. ## A Reminder of Lagrange Multipliers for Optimization Problems DevFeed: [A Reminder of Lagrange Multipliers for Optimization Problems]() Original publisher: [Read original article]() Published: 2013-11-30T09:00:50Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Optimization](), [function](), [Variable]() Tags: [convex-functions](), [function](), [gradient-descent](), [lagrange](), [lagrange-multipliers](), [linear-algebra](), [optimization](), [problems](), [variable](), [vectors]() ### AI overview A tutorial-style reminder of Lagrange multipliers for optimization problems. It reviews gradients, partial derivatives, dot products, and directional change for multivariable functions. ### Source excerpt For a while I've been meaning to do some more advanced posts on optimization problems of all flavors. One technique that comes up over and over again is Lagrange multipliers, so this post is going to be a leisurely reminder of that technique. I often forget how to do these basic calculus-type things, so it's good practice. We will assume something about the reader's knowledge, but it's a short list: know how to operate with vectors and the dot product, know how to take a partial derivative, and know that in single-variable calculus the local maxima and minima of a differentiable function $ f(x)$ occur when the derivative $ f'(x)$ vanishes. ## Forum lock DevFeed: [Forum lock]() Original publisher: [Read original article]() Published: 2008-01-17T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [Development]() Tags: [developers](), [development](), [free](), [open-source](), [os](), [problems](), [react](), [reactos](), [win32](), [winapi]() ### AI overview ReactOS developers locked the forum because of malicious activity and said it would remain locked until the issue was fixed. The development team also warned that disruptive users could be banned. ### Source excerpt Forum Issues We're currently dealing with some malicious activity on the forum. Some of the developers have decided to lock it until the problem is fixed. Quite frankly, it's disappointing that we need to go this far, but we the development team will ban and kick people who refuse to behave or cause problems for us.