Stef's Dev Notes
This is where I think out loud about frontend engineering and engineering in general. The code I'm writing, the career lessons I'm learning, and all the invisible work that actually matters, shared one small note at a time.
- Indexed issues, last 90 days
- 5
- Latest publication
- Sep 15, 2026
- Audience
- Checking…
- Earliest in this view
- Jul 8, 2026
Latest issues
The Stack Decision I Might Have to Revisit (opens the original)
Read excerpt
In short: When the urge hits to swap in something new, I don't. Vercel is in all three of my projects, Supabase in two, and the framework is the part that changes: React + Vite or Next.js. What decides that last one is coupling.Hi, I'm Stefania 👋 Welcome to Stef's Dev Notes, where I write about engineering judgment in an industry obsessed with speed: the trade-offs behind the architecture, and the reasoning that decides whether systems scale or quietly break.<a class="button primary
Stop Being the Only Place the Memory Lives (opens the original)
Read excerpt
In short: I stopped repeating myself to Claude Code by writing corrections into files instead of my next message — CLAUDE.md for how I work, BACKLOG.md for what I'm building — trusting live sources over stale copies, asking for the why behind every command, making sure I’m learning from what I’m building, and making silent dependencies visible and documented instead of leaving them to be discovered the hard way.Hi, I'm Stefania 👋 Welcome to Stef's Dev Notes, where I
Giving got easier. Receiving still doesn't. (opens the original)
Read excerpt
Hi, I'm Stefania 👋 Welcome to Stef's Dev Notes, where I write about engineering judgment in an industry obsessed with speed: the trade-offs behind the architecture, and the reasoning that decides whether systems scale or quietly break.Subscribe nowFive weeks ago I launched Fika for Substack — a weekly appreciation table where
The Product Thinking Was Mine. The Ownership Wasn't. (opens the original)
Read excerpt
We found out our product owner was leaving on a Tuesday, in a meeting that was supposed to be about something else.I remember feeling worried for about a day.Then I opened the roadmap, the same one we’d built together, and realized I already knew what most of it meant in practice. I’d just never been the one who had to say so out loud.I’d been doing pieces of this for months, quietly, folded into “development.” I just hadn’t been the one holding it in the open.If you’re new here, join over 300 r
Narrative is a feature : Why engineers should care about storytelling (opens the original)
Read excerpt
A quick note before we dive in: This article was written in collaboration with , who is beginning his journey in copywriting. Alex transformed my ideas and experiences into this article, while I added my personal touch through the story from the second paragraph about the live search feature and the moment I couldn't explain my own code.You'll probably see Alex's name on future articles too, as we'll be collaborating more. 😊When I started learning programming, I was quickly introduced to lots of
Publishing over time
Last 90 days. Choose a month to open its work.
Recurring subjects
Named in the text we hold. One piece can cover several.
Audience
No verified audience measurement yet.
About this data
Counts cover the work we have indexed. Tone needs enough text and a confident classification. Excerpts and episode notes are not full articles or transcripts.
Identity or attribution wrong? Suggest a correction.