Why Your Project Tracker's 'In Progress' Label Is Hiding a Rework Problem

·2 views

Most project trackers represent rejected or reworked deliveries as simple state changes rather than distinct events, erasing critical information about what went wrong and why. This means teams lose visibility into whether a task was completed and redone multiple times, inflating cycle-time metrics and masking the true causes of failure. Categorising rework with a short, fixed list of reason codes — such as 'brief was ambiguous' or 'requirements changed' — allows teams to spot patterns and act on aggregate data each month. One team discovered through this method that most of their rework stemmed from specification problems, not poor execution, explaining why their previous corrective efforts had failed. The approach requires no new tooling and becomes especially important as AI agents take on tasks, since they cannot self-report confusion the way human workers can.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Apple Siri Code Reveals Option to Replace AI with Claude or ChatGPT

Code discovered within Apple's Siri suggests the assistant can be swapped out for third-party AI models, including Anthropic's Claude and OpenAI's ChatGPT. The finding, reported by MacRumors in September 2026, indicates Apple may be building flexibility into Siri to support alternative large language models. This would allow users or developers to choose a preferred AI backend rather than relying solely on Apple's own system. The discovery points to a broader trend of AI interoperability as tech companies compete in the rapidly evolving assistant market.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Key Gas Optimization Techniques That Can Cut Ethereum Smart Contract Costs by 70%

Gas fees on Ethereum represent the computational cost of executing smart contract operations, and poorly optimized contracts force users to pay unnecessarily higher transaction costs. Developers can significantly reduce gas consumption by packing storage variables into fewer 32-byte slots, minimizing expensive storage writes, and caching values in memory during loops. Choosing mappings over arrays for data lookups and placing input validation before computationally heavy operations also yields measurable savings. Additional gains come from using events instead of on-chain storage for historical data and setting correct function visibility. Together, these techniques can reduce a contract's execution costs by as much as 70%, improving user experience and making decentralized applications more competitive.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why a desktop app developer chose transparency over DRM for license checks

A developer behind a paid Electron desktop app has explained why they deliberately avoided encryption or obfuscation for local license enforcement, acknowledging that any user can inspect or modify files on their own machine. Instead, the team stores the license status as a plain JSON cache and treats it as exactly that — a cache of a server-side answer, not an authoritative source. All sensitive actions, such as sending emails via the app's infrastructure or validating purchases, are verified server-side against a database on every request. The one-time purchase model simplifies the offline experience further, since a cached 'yes' never expires and a failed network call does not revoke access, meaning the system fails open in favor of the paying customer. The developer argues this approach is both more honest and more practical, as determined non-payers are unlikely to convert regardless, while wrongly locking out legitimate users creates real support and refund costs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer open-sources lightweight React 19 Tailwind dashboard to replace bloated UI kits

A developer has released Exo-Dash, a free open-source dashboard boilerplate on GitHub, built as an alternative to heavyweight UI libraries like MUI and Ant Design. The project uses React 19 and Tailwind CSS v4, adopting a shadcn-style primitive architecture that gives developers full design control without CSS override conflicts. Performance is prioritized through Vite-powered builds, React Router v7, and lazy loading of resource-heavy routes such as Kanban boards and analytics views. Form handling relies on react-hook-form and Zod to minimize re-renders, while a global theming context supports light/dark modes and dynamic color schemes persisted via localStorage. A free Community Edition is available on GitHub, with a paid Pro version offering advanced layouts and commercial licensing.

0 comments Read more at DEV Community