Japan Missed Its Own 2025 Deadline to Modernise Decades-Old Legacy Systems

·1 views

Japan's Ministry of Economy, Trade and Industry formally identified the country's ageing enterprise software as a national risk, setting a modernisation deadline that has now passed. Many critical systems — spanning banking, insurance, government, and manufacturing — were built generations ago by external systems integrators through multiple layers of subcontracting, leaving no single party with full knowledge of how they work. The original developers have largely retired, taking institutional knowledge with them, while the code continues to run largely untouched. Structural factors unique to Japan, including deep subcontracting chains and industries where long-term stability was always prioritised over renewal, have made the problem especially entrenched. Engineers working inside these systems describe the experience less as software development and more as archaeology, carefully excavating logic that no living person fully understands.

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)

System Design Skills Now Matter More Than LeetCode as AI Handles Routine Coding

An AI product engineer argues that generative AI tools have devalued traditional coding interview prep by easily handling algorithmic problems and boilerplate code. As a result, hiring managers are shifting emphasis toward system design rounds, where AI assistance provides little advantage. Unlike pattern-recall answers that AI can produce instantly, interviewers now probe for commitment to architectural decisions, context-sensitive reasoning, and the ability to defend choices under pressure. The author warns that memorizing standard design playbooks produces answers indistinguishable from AI output, signaling nothing to evaluators. The scarce and increasingly valued skill is not knowing that caches or queues exist, but understanding the real-world consequences of choosing one architecture over another.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Fixes Joplin Bug That Kept Tag Options Active After Note Deletion

A contributor to Joplin, the open-source note-taking app, identified a UI state bug where tag operations remained clickable in the status bar even after a note had been deleted. Although the application did not crash, the interface failed to reflect the actual state, allowing users to attempt tag commands on notes that no longer existed. The fix adds a check in the click handler so that tag operations are blocked whenever the underlying state marks them as disabled. Visual cues such as reduced opacity and a changed cursor now signal to users that the action is unavailable. Accessibility was also improved by adding the aria-disabled attribute, ensuring assistive technologies correctly interpret the disabled state.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

DEV Community Publishes Foundational Guidelines for AI Architects and Developers

A set of foundational principles for AI researchers, architects, and developers has been published on DEV Community, emphasizing that conceptual clarity must precede technical implementation. The guidelines urge developers to define key terms such as intelligence, reasoning, and alignment before writing any code, warning that undefined language leads to inherited inconsistencies in systems. The document stresses that coherence should take priority over complexity and optimization, arguing that adding functionality without a coherent foundation increases unpredictability. It also highlights that AI systems inherit human assumptions and limitations, meaning improvements to AI must begin with examining the human foundations that shape them. Developers are called to accept responsibility for the long-term effects of their work, including impacts on future systems and generations that do not yet exist.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Free Browser-Based JSON to Excel Converter for Nested Data

A developer has created a free, browser-based tool that converts JSON data into Excel spreadsheets without requiring user registration or file uploads. The project was motivated by the limitations of existing tools, which often imposed file-size restrictions, demanded sign-ups, or failed to handle nested JSON structures. The converter validates input, flattens nested objects into column headers, and processes arrays before generating a downloadable Excel file. It was designed to help developers share API responses with non-technical business users for reporting, testing, and data analysis. The tool is publicly accessible at convertonlinetool.com and the developer is seeking community feedback for future improvements.

0 comments Read more at DEV Community