Tag: software development

  • Tokens are My NOS Kit

    If you can remember this scene from Fast&Furious, Walker fires the NOS kit to give his car a power bump mid-race. Incredible imagery. NOS is gas that increases engine’s combustion giving it more power for a handful of seconds. In other words, it’s not a permanent increase in power. Once the NOS intake reduces, the…

  • No More Large Monitors

    Little by little I’m emancipating myself from tech dead weight. Agentic software development defined a new workflow, new tooling and, why not?, new hardware setups. Starting this month I’m retiring my 32 inch 4K monitor I used in so many software development projects. Have a split window in the IDE was a strong operational need.…

  • Tokens Used by Country

    This is the new GDP. Source: OpenCode

  • Functional Misalignment due to Agent Hallucination

    I saw this image posted on X with reference to a development team losing substantial volumes of work due to agent hallucination. I noticed something similar in my work, and I really emphasize the similar here. It’s similar in the sense that there is complexity of all sorts being added continuously to codebases. Some of…

  • Drive AI (as a Software Engineer)

    I’ve been harping on the disciplines and tools for using AI lately. I find them to be a very effective approach. But I don’t want to leave you with the impression that a few simple disciplines and tools is sufficient. As the AI’s build software, you — the software engineer — need to have a…

  • Drunk Post: Things I’ve Learned as a Senior Engineer (2021)

    Drunk Post: Things I’ve Learned as a Senior Engineer (2021)

    A few years ago, a data engineer on r/ExperiencedDevs got drunk and wrote down everything he learned in 10 years of engineering. The original account is deleted, but the post captures something real — the kind of honesty you only get after a few glasses of wine. Preserving it here, typos and all. I’m drunk and I’ll…

  • The PHUMY Stack

    The PHUMY Stack

  • Make It Work, Then Perfect It Later

    Make It Work, Then Perfect It Later

    Yes, this is a nice little statement that loads us with encouragement. It’s too bad that it cannot compete with another nice little statement in popularity: If it’s not broken, don’t fix it. — western culture & mindset

  • Code Review Debt

    I’m beginning to notice this behavior not only on my programming work, but also on comment on X. Most people still believe that code review is a task for humans to perform. I agree with that. Normally, the reviewer is someone senior within the team or organization. And the seniority came from many hours working…