• Failure Modes

    The software we write is fallible, precisely we’re fallible. That’s not to say that all software is unusable though. Failure is always an option.

  • Comparison

    It’s inevitable that I compare everything to Manila, even if I would rather not: I have only that data point to use as basis.

  • Journaling

    Since November, I’ve been keeping a journal of my work, as a means of data gathering on my own productivity; it also gives me a sort of timeline of events, should I need to look back.

  • A Good Meal

    Food, glorious food.

  • Bilingual

    Communication when being fluent or conversant in two languages, coming from a culture of code-switching.

  • Models

    The map is not the territory, and often when writing software we’re building maps and models of things – which inevitably encodes our own assumptions.

  • Downtime

    The time I spend outside of work on rest and relaxation – or at least, Not Work.

  • Talk

    On socialization, introversion, and small talk.

  • Retrospective

    Looking back on the year that was

  • Why I Write

    There are various reasons for why I write on this blog (even if I’m not as consistent with my schedule sometimes).

subscribe via RSS