Rant

Why Vim is Superior to Neovim Neovim is a mistake. It’s not an improvement—it’s a misguided fork that breaks everything good about Vim while adding features nobody actually needs. The Async Patch Lie What Neovim Claims 1 2 3 4 -- "Async operations are revolutionary!" vim.lsp.buf.hover() vim.lsp.buf.definition() vim.lsp.buf.references() What They Actually Are 1 2 3 4 5 6 7 " Vim already has async operations :!make & :!git push & :!npm install & " Neovim just added async to plugins " Big deal. Vim plugins were already fast enough. The async patch doesn’t matter because Vim plugins were already fast enough. ...

Agile is a Cult, Not a Methodology Agile is a cult. It’s not a methodology—it’s a religious movement that brainwashes developers into believing that meetings and ceremonies are more important than writing code. The Agile Manifesto: The Original Sin What They Claim “Individuals and interactions over processes and tools” “Working software over comprehensive documentation” “Customer collaboration over contract negotiation” “Responding to change over following a plan” What They Actually Do Processes and tools: Jira, Confluence, Slack, Zoom Comprehensive documentation: User stories, acceptance criteria, retrospectives Contract negotiation: Sprint planning, story points, velocity Following a plan: Roadmaps, epics, features, sprints The Agile Manifesto is a lie. They do the opposite of what they preach. ...

Why Microservices are a Scam Microservices are a scam. They’re not an architecture—they’re a marketing ploy to sell you more servers, more complexity, and more consulting services. The Microservices Lie What They Tell You “Scalable and maintainable” “Independent deployment” “Technology diversity” “Fault isolation” “Team autonomy” What You Actually Get Distributed monolith: All services depend on each other Deployment hell: Coordinating releases across services Technology chaos: Different languages, frameworks, databases Failure cascade: One service failure breaks everything Team confusion: Nobody knows how anything works The Complexity Explosion Monolithic Application 1 2 3 4 5 6 7 # Simple, clear, maintainable def process_order(order): validate_order(order) charge_payment(order) update_inventory(order) send_confirmation(order) return order Microservices “Architecture” 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 # Order Service POST /orders GET /orders/{id} PUT /orders/{id} # Payment Service POST /payments GET /payments/{id} # Inventory Service POST /inventory GET /inventory/{id} # Notification Service POST /notifications GET /notifications/{id} Simple function becomes 4 services, 8 endpoints, and infinite complexity. ...

JavaScript is the Worst Thing to Happen to Programming JavaScript is a mistake. It’s not just bad—it’s actively harmful to the entire programming profession. Every line of JavaScript written is a step backward for humanity. The Language That Shouldn’t Exist Designed in 10 Days JavaScript was created in 10 days by someone who didn’t know what they were doing: No type system: Variables can be anything Inconsistent behavior: == vs === madness Terrible error handling: Silent failures everywhere No standard library: Everything is a hack 1 2 3 4 5 // This is legal JavaScript var x = "5"; var y = 5; console.log(x == y); // true (WTF?) console.log(x === y); // false (WTF?) This is not a programming language—it’s a practical joke. ...