Developer Overhauls Portfolio, Purges 16,000 Lines in Weekly Coding Sprint

·5 views

A developer spent the week overhauling their personal portfolio's blog layout, merging a pull request focused on typographic hierarchy and removing decorative UI elements in favour of cleaner, server-rendered content. The changes touched over 200 files and introduced accessibility improvements such as keyboard-friendly focus rings. Separately, the developer deleted nearly 10,000 lines from their Obsidian note-taking vault, removing entire topic directories deemed outdated or incomplete. On the open-source front, they submitted a pull request to py-libp2p addressing flaky DHT routing-table tests by introducing a bounded polling mechanism. Across all four projects, the week's work totalled 36 commits, more than 23,000 line additions, and nearly 16,000 deletions.

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)

How Misconfigured Docker BuildKit Cache Silently Kills CI Build Speed

A developer discovered that a client's Docker builds were taking nine minutes per pull request despite appearing to use caching, because BuildKit cache had never actually hit in three months. The root cause was using a drifting ':latest' tag as the cache source, which caused silent full rebuilds every time without any error message. BuildKit determines cache hits using a combination of base image digest, build context checksum, and instruction match — meaning even minor file changes can invalidate entire dependency layers. Common mistakes include placing 'COPY . .' before dependency installs, relying on ephemeral CI runner disk storage instead of exporting cache to a registry, and using the now-deprecated inline cache method. Properly configuring registry-based or GitHub Actions cache backends is essential to achieving genuine build speed improvements in CI pipelines.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds zero-commission UPI donation page with no backend or payment processor

A developer named Shivam has released an open-source donation platform called 'buy-me-a-chai', designed as a free alternative to services like Buy Me a Coffee for Indian creators. The static site requires no backend, database, or payment processor, instead leveraging India's UPI system to route payments directly between bank accounts. Users simply fork the template, edit a single YAML file, and deploy it for free on GitHub Pages. The project deliberately accepts that the page cannot confirm whether a payment was completed, eliminating the need for a payment aggregator and the commissions that come with one. Building the tool also surfaced a technical pitfall: using JavaScript's URLSearchParams corrupts UPI links by encoding spaces as plus signs, which UPI apps misread, requiring encodeURIComponent as the correct fix.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a Semantic WAF Like SafeLine Can Block SQL Injection at the Proxy Level

SQL injection remains the most prevalent web vulnerability, accounting for 23% of all reported web flaws in 2025, according to the OWASP Top 10. Traditional pattern-matching WAFs can be bypassed using encoding tricks, while semantic WAFs like SafeLine parse the actual SQL structure of incoming payloads to detect malicious intent. SafeLine's semantic engine claims a false positive rate of just 0.07% and requires no custom rules, blocking attacks before they reach the database. The tool also extends detection to NoSQL injection patterns, including MongoDB operators, using the same single-pass parsing approach. Security experts stress that WAF protection should complement — not replace — secure coding practices such as prepared statements, serving as a defense-in-depth layer for legacy code and third-party libraries.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SafeLine WAF Can Be Added to Any Docker Compose Stack in Three Steps

Developers running existing Docker Compose stacks can integrate the SafeLine Web Application Firewall without rebuilding or modifying their app containers. The process involves connecting existing services to a shared Docker network, installing SafeLine via its official script, and linking its reverse proxy to that shared network. Nginx or other reverse proxies are then configured to route traffic through SafeLine before it reaches the application, creating an inspection layer between the internet and the app. SafeLine operates as an independent Compose project, meaning updates to either the app stack or the WAF do not interfere with each other. The setup also supports a detection-only mode, allowing teams to monitor for false positives before enabling active traffic blocking.

0 comments Read more at DEV Community