How much documentation do you need? How heavy are your processes? How much AI do you use? What level of automation do you have? How many PRs do you ship daily? Whatever your task, whatever your work, there always needs to be a balance between how much you need and how much you want. Do you need to spend time automating every single process that you have in existence, even if you don’t use all…
It’s just over the hill, peeking out at you like a gopher. It’s waiting for you to put down whatever you’re frustrated with and walk over the hill to see what is there. It’s not a quick win, it’s not low-hanging fruit – it’s a project – it will take time, energy, and effort. But in the end, it will be worth it. If you want to see.
This is one of the best quotes from Moneyball. Talking, talking, talking, but never taking the chance, never taking the risk, never willing to press the button. I’ll keep it simple… Things will break. Debugging is never straightforward. Work isn’t easy. You won’t succeed the first time. But if all you do is talk, you will never learn, you will never grow, you will never find the next path you should be on. Don’t talk…
I read two types of articles these days; We completed our work within 4 hours and have a new product. I was hired to come in and fix a company’s product and have spent the last 2 weeks making it scale. The answer is in the middle: find the right people who use the right tools, to deliver the right thing somewhere in the middle. The middle is where we all want to be, but…
There are ways to fix your problems. I can do it fast by getting vibe coding it- and it will look nice, but may not scale. I can do it with no code, but I might be limited by how far I can take it with the features made available to me; it probably won’t look as nice as if I’d Vibe Coded, as it will be following a structured template. I can code it…