I've learned the hard way that it's better to search for longer than to settle too fast and hire someone who's just okay. The thing is, when the right person comes along, they won't be 10% better. They'll probably be 20x better in the potential impact they can have in the team. Choosing wrong has a double penalty. First you invest time and money into finding if there's a fit and if it doesn't work, you'll still have to search for someone new. There's also another nugget hidden there. If the relationship's not working, the sooner you split, the better off you'll be. Financially and time-wise. Find someone not just for the technical ability, but who'll also be a pleasure to work with. Yours, |
Hi, I’m Taj Pelc. I write about technical leadership, business mindset and enterpreneurship. Daily advice on building fantastic tech teams that deliver great products. I'll see you inside.
I wanted to get experience with the Telegram app ecosystem, so I build a very basic Flappy Bird clone (https://t.me/flappster_bot?game=flappster_classic — you can try it out here). The prototype had to be up and running as quick as possible and I wanted to test it through Telegram which expects the game to be accessible at a public URL. For development, I'd love to skip a deployment step and serve it right from my machine for fast iteration. I could punch a hole through my firewall and lose...
Generative AI tools are getting multi-file editing capability. It recently got introduced to GitHub Copilot. It's already in Cursor and my current favorite, Cline. It can implement a feature across multiple files, but it's still bound to the token limits that the LLM it's using has. Adding a parameter to an API response and modifying a few files to pass it along is cool, but forget about building the whole application from a prompt. (For all but the most simple apps) The limiting factor is my...
Do you know why velocity slows down when you add more people? If I do it myself, I just open the editor and go. If I have to explain what I want to you, my words are being transmitted to you at 120 bits per second (at a normal speaking pace). And that assumes I made it clear on the first go and that's just not how human conversation works. We're going to have a bit of back and forth. You'll ask me if you understood me correctly, I'll explain more, bitrate drops. And this works fairly well. As...