Developer Rethinks Clean Code After Years of Working on Real-World Systems

·1 views

A software developer reflects on how his understanding of clean code evolved over years of professional experience, starting from early mistakes during code reviews at an international team. Early in his career, he strictly followed rules like keeping functions short, avoiding repetition, and building abstractions early, often prioritizing how code looked over how it functioned long-term. Over time, working on larger systems with real users and constraints, he found that textbook clean code principles did not always produce the best outcomes. He also inherited frontend codebases that were messy by conventional standards yet stable, functional, and serving users effectively. These experiences led him to broaden his definition of clean code beyond appearances to include how well code holds up over time in practice.

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)

Developer shares four hard-won lessons from building a WebGL water hero in React

A developer building an interactive WebGL water ripple hero section for a React app documented four significant bugs encountered beyond the visual effect itself. The ripple effect was powered by the legacy jQuery plugin jquery.ripples, which required careful async loading and a cancellation flag to prevent React lifecycle conflicts. On mobile Safari, using 100vh caused layout issues due to the dynamic URL bar, which was resolved by switching to the more stable 100svh unit. A stale-props bug in a cart quantity stepper caused rapid double-clicks to miscalculate totals, fixed by passing relative deltas instead of absolute values to the state updater. Additionally, a hero background texture was being downloaded on every route because a preload tag was placed in the global index.html of the single-page app, rather than loaded conditionally on the hero page alone.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SQL Injection Explained: How Source, Sink, and Taint Define a Vulnerability

A software vulnerability typically follows a predictable pattern where untrusted user input travels from a source, such as an HTTP request parameter, to a dangerous sink, like a database query, without being sanitized first. Security researchers use the concept of 'taint' to describe how unvalidated data contaminates everything it touches on that path. Common web vulnerabilities including SQL injection, command injection, path traversal, and XSS all share this same source-to-sink structure, differing only in which dangerous operation is exploited. In a Java SQL injection example, one method passes user input directly into a DELETE query, allowing an attacker to wipe an entire database table by appending a condition like 'OR 1=1'. A second version of the method blocks the attack by validating that the input contains only digits before constructing the query, illustrating how input validation acts as a filter between source and sink.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Aaron Swartz faced prosecution for scraping data that Meta now does freely

A blog post circulating on Hacker News draws a sharp contrast between the legal treatment of Aaron Swartz and current practices by Meta. Swartz, a co-creator of RSS and internet activist, was federally prosecuted in the early 2010s for scraping academic articles from JSTOR. He died by suicide in 2013 before his case went to trial, facing decades in prison. Meta and other large tech companies now routinely scrape vast amounts of web data to train AI models, largely without legal consequence. The post has reignited debate about the unequal application of internet law and the selective enforcement of data access rules.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Proxmox GPU Passthrough Failure Traced to HBA Conflict, Not the GPU

A Proxmox 8 host configured for PCIe passthrough of an NVIDIA RTX A4000 into an Ubuntu 24.04 VM repeatedly failed to start the guest, with QEMU exiting silently and leaving no console output. Host-side dmesg logs revealed IRQ allocation failures and VFIO interrupt remapping errors at VM startup, pointing to a deeper hardware conflict rather than a misconfigured GPU setup. Despite following standard passthrough steps — including VT-d, IOMMU, OVMF BIOS, and q35 machine type — the issue persisted across multiple troubleshooting sessions. The root cause turned out to be a Host Bus Adapter (HBA) in the system, not the GPU itself, making the fault difficult to identify because error messages implicated the wrong device. The passthrough was being set up to accelerate Filecoin sealing workloads, specifically the TreeRC tree-building phase, which can drop from two to three hours down to fifteen to twenty minutes with GPU acceleration.

0 comments Read more at DEV Community