If you’ve been following the AI agent space lately, you know that OpenClaw (the project formerly known as Clawdbot and briefly Moltbot) has become the gold standard for self-hosted autonomous assistants. While running it on your local machine is great for testing, the real power of OpenClaw comes when it’s running 24/7 in the cloud. Whether it’s managing your WhatsApp messages while you sleep or executing long-running web automations, a cloud VPS is the way to go. ...

As developers, we like to build things. When a product manager or a user asks for a feature, our natural response is “Sure, I can do that in two days.” But every “Yes” is a commitment to maintain that code forever. The Feature Creep Trap The most successful products aren’t the ones with the most features; they’re the ones with the right features. Every button you add to a UI makes every other button slightly less important. Every branch in your code makes the next bug slightly harder to find. ...

I see many teams claim they have “CI/CD” because they have a Jenkins or GitHub Actions pipeline that runs tests. But if your process involves a “Freeze Week” or a “Manual QA Sign-off” that takes 3 days, you don’t have CI/CD. You have an automated build process. The Goal: Confidence The goal of CI/CD isn’t to run scripts. It’s to give the team enough confidence that a commit can go to production without human intervention. ...

Looking back at the XML days of Android development feels like looking at black-and-white television. It worked, but boy, was it clunky. Today, in 2026, Jetpack Compose isn’t just “the new way”—it’s the only way that makes sense for modern Android apps. Declarative is King The shift from imperative (“find this view and set its text”) to declarative (“here is the state, describe how it looks”) has probably saved me thousands of hours of debugging weird UI states. No more null view references. No more findViewById. ...

“Fat models, skinny controllers.” That was the mantra for years. But if you’ve ever worked on a Rails app that’s more than two years old, you know where that leads: a User.rb file that’s 2,000 lines long and handles everything from authentication to generating PDF invoices. The Problem with Fat Models When a model knows too much, it becomes impossible to test in isolation. You want to test a simple validation, but you end up triggering five callbacks that send emails and ping Slack hooks. ...

We’ve all been there. You’re working on a feature, and you need to parse some weirdly formatted date or handle a complex file upload. Your first instinct? npm install or bundle add. It feels like winning. Someone else already solved this problem! Why should I reinvent the wheel? The “Free” Wheel But here’s the thing: every dependency you add is a liability. It’s code you didn’t write, but code you now own. You own its bugs, its security vulnerabilities, and its breaking changes when it decides to “improve” its API. ...

Around 2 years ago, I started a new management gig. it wasn’t the first, but it was the first with a relatively large team. One of the most basic things I needed to do as a manager was to bind the team to its mission, and in simple terms: get them super motivated to do their day to day tasks. I’m a strong preacher for freedom, it gives people a sense of ownership. ...

We all wanna get from 0 to 1 (with many trailing zeros), the sooner the better. So, what’s the problem? You build something and you’re brave enough to put it out there, now what? Now you start the endless feedback loop cycle, you look at the data, analytics, user recordings, product inputs, and decide what’s the next thing that’ll make your product better then ever, it’s an iterative process that never ends. The faster you iterate, the faster you’ll get to your target. ...

If you ever used any MVC framework, I’m sure you asked yourself more than once, ‘Where should I put this piece of code?’ (If not that’s also fine). Well, there is no one answer for all problems but, I asked it a lot. In this post, I’m gonna focus about the view part. View objects, AKA view models, but any other name is fine (presenter view object, view controller mediator, whatever). ...

So I found out it’s not so documented, hopefully google will index this. I have a page on my system that shows a google geo chart (same as this) When clicking on a country on the map lot’s of interesting things happens. And I wanted to implement a ui automation test to cover this use case. It’s not so easy cause even if you find the right svg path object and try clicking on it you get some interception errors. So I googled a bit without any luck, but the geo chart documents came to the rescue. ...