Why vibe-coded projects die in silence, and real developers don't. There is a rhythm to vibe coding projects on GitHub. A burst of commits over a weekend. A demo video. A Product Hunt post. Then nothing , branches unmerged, issues open, the README still reading "coming soon.
I’ve been thinking a lot about multi-region systems lately, especially around Keycloak-style setups. And honestly, the more I worked with it, the more I realized something simple: Failover and replication are usually treated like database problems, but they’re actually system design decisions. The default standalone Keycloak
This repository contains a set of Quickstarts for the Quarkus framework. Each of them has a Getting started guide. Requirements To compile and run these demos you will need: * JDK 17+ * Mandrel or GraalVM See the Building a Native Executable guide for help setting up your environment. Use alternative platforms
Design a production-ready IAM system using Keycloak, Django, Entra ID and eIDAS. Includes a live interactive simulator. Why this post exists. Most developers build authentication exactly once, and spend years paying for it you know what I mean 🕶️. The problem is not a lack of tools Keycloak, Django, Microsoft
Nothing was installed. No browser automation tools were used. After inspecting Gmail and seeing that its class names change per session, the approach relied on that understanding. Everything was done directly through the browser console using JavaScript. This is a one-session cleanup trick that runs only in your open
What would your product look like if AI ran it, and your team built it that way from day one? That’s the real question behind AI-First thinking. Not: “Can we bolt on ChatGPT, Claude, MCP, OpenAI later?” But: “What if AI made the decisions, personalized the journey, generated
A Developer’s Shortcut to Reality Now with AI in the Loop… Everything Changes * Decisions are made in seconds. * Ideas live or die in a day. * Your co-workers are half-human, half-robot...assisted by GPTs, Copilots, cron-agents, or internal LLM tools. From FTP to full-stack infra,
By someone who tried to automate too much, too fast I’ve been running an automated daily prompts for a while now ...mostly to learn, to explore trends, and to see how GPT evolves in tone and insight. At first it felt magical. But then, without expecting it, I started
I don’t write polished essays. I write when something refuses to leave my head. Recently I’ve been practicing architecture on AWS free tier, reading the roadmaps of Google Cloud, Azure, and even the new GPU-first “neoclouds.” Not because I’m preparing for anything specific, but because one
Today, I tried DuckDB and Polars, and both impressed me with their speed. However, I wanted to ensure that my insights weren’t biased by reading documentation alone. So, I focused on real-world use cases that I frequently encounter: * GroupBy operations * Filtering results * Sorting results * Loading large datasets I
Someone is sitting in the shade today because someone planted a tree a long time ago. – Warren Buffett 2025: Looking Back at My Journey Hola! It’s 2025... I’ve been working for many years, grinding for different companies, some for the long haul, others just short-term gigs like
Rust Programming Language, often just called Rust, stands at the forefront of modern software development. It's a programming language meticulously crafted to ensure software creation safety, speed, and reliability. curl --proto '=https' --tlsv1.3 https://sh.rustup.rs -sSf | sh Introduction Rust is a systems programming