You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Fusion: VDD × TDD × SDD for AI-Native Engineering
Overview
Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:
Spec-Driven Development (SDD): Define the contract before writing a single line of implementation. Specs are the source of truth.
Test-Driven Development (TDD): Tests are written before code. Red → Green → Refactor. No code exists without a failing test that demanded it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Launch gpt-oss-120b with Ollama on AWS Sydney region
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What would you do if you had a chance to sneak peak in the year 2030 and you were a Hubber?
After the last git commit
How we got here
It's 7th of May 2025, and I'm leaving. Before I go, I'd like to share my vision of the future. If you're reading this in 2030, you probably wish you'd read it five years earlier. Consider this a time capsule from a future that arrived faster than expected.
Let’s rewind. It’s hard to believe developers once worked without AI. In domains like embedded systems, mining infrastructure, and medical software, adoption was slower due to regulation and legacy constraints. But everywhere else, including browsers, APIs, simulations, and cloud environments where AI coding agents took over.
Why did AI take over coding so quickly? One word: economics. In 2021, a junior developer in San Francisco earned over USD $260,000 to build basic prototypes. Managing 100 of them cost over $26 million per year. By 2025, an AI-powered team could deliver equivalent output at less than six percent of that cost. Quality improved, fatigu
How to maintain two repositories internal/private and one open-source
📖 Managing dual repositories on GitHub
Managing multiple repositories that serve distinct but interconnected purposes can be a challenging task 😓. This scenario is common when an organization wishes to contribute to an open-source project 🌐 while also maintaining an internal space for private collaboration 🔒.
The challenge here lies in keeping these repositories in sync 🔄 without manual intervention, ensuring that changes made to one repository 📁 are accurately reflected in the other 📁.
In this step-by-step tutorial 📃, we'll walk through a use case where a customer wants to contribute to an open-source project 💻 and, at the same time, collaborate internally within their organization 🏢.
Get UTM for Mac - the App Store version is offered merely as a way to support the developers, since it's paid, but has the same features as the free build;
A handy script to shift GitHub repos from one place to another
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created
August 17, 2022 04:29— forked from osy/README.md
Local caching for GitHub Actions self hosted runner using Squid Proxy
One of the biggest issues with using a self hosted GitHub runner is that actions that require downloading large amounts of data will bottleneck at the network. [actions/cache][1] does not support locally caching objects and artifacts stored on GitHub's servers will require a lot of bandwidth to fetch on every job. We can, however, set up a content proxy using [Squid][2] with SSL bumping to locally cache requests from jobs.
Patching Squid
A major challenge is that [actions/cache][1] uses Azure storage APIs which makes HTTP range requests. While Squid supports range requests, it is not good at caching them. There is an option, range_offset_limit none which, according to the [documentation][3]:
A size of 'none' causes Squid to always fetch the object from the beginning so it may cache the result. (2.0 style)
However, after extensive debugging, I discovered that the feature does not work if the client closes the connection. When range_offset_limit is set, Squid will make a full request to the server,