Every project starts with the same blank screen. Before any architecture decisions, before any deployment pipelines, before any of the interesting stuff — there’s just a cursor blinking on an empty file.
This blog is that empty file.
why this exists
Function of P was built around a straightforward idea: software should be made with care. Not with process theater or buzzword-heavy slide decks, but with clear thinking and honest engineering.
This blog is where I’ll write about the work — the technical decisions, the tradeoffs, the things I learn along the way. No thought leadership. No content marketing. Just notes from someone who builds things for a living.
what to expect
A few things you might see here:
- Technical write-ups — how and why I chose a particular approach for a project, and what I’d do differently next time.
- Tools and workflow — the stack, the editors, the scripts. What actually helps and what’s just noise.
- Honest takes — on frameworks, on trends, on the industry. Short and direct, no hedging for algorithm points.
I’m not promising a schedule. Posts will show up when there’s something worth saying.
a note on craft
There’s a difference between software that works and software that’s built well. Both will pass the acceptance criteria. But the well-built version is the one that doesn’t fall apart six months later when requirements change.
That’s what I care about. And that’s what I’ll write about.
If any of this sounds interesting, stick around.