How I'm Optimizing My Small Blog to Get Cited by AI (Based on Actual Research)
AI ate my traffic. Then I found a study of 18,000 pages that shows what actually gets cited.
Oh That Data Girl
Data engineer with a systems mindset, mildly owned by cats. Writing what I wish someone had written earlier.
Latest posts
Know your tokens. Own your costs.
Learn what LLM tokens are, how they are calculated with BPE, and how to count and compare them across OpenAI, Claude and Gemini APIs. Real code, real token counts, real pricing math for input, output, reasoning and cached tokens.
SQL Interviews in the Age of LLMs: Patterns Over Queries
Stop memorizing queries. Learn to recognize the 12 problem shapes that keep showing up.
AI Gave Us Lemons. We Picked Limoncello
Here's the thing. These days it's become genuinely hard to maintain professional motivation in software engineering. The level of bullshit is off the charts, everyone lies from companies to ChatGPT. AI rewrote this, AI replaced those people, AI this AI that blah blah blah. Today you&
Build in Public: Week 10. Making It Less Fragile
Build in public has a funny way of changing over time. In the beginning you write about ideas, architecture, big plans and bold assumptions. A few weeks later you mostly write about why something broke, how it broke and what you had to fix so it doesn’t break
Build in Public: Week 9. The Shape of Wykra
Build in public is an interesting experiment overall. You get new readers, some of them even stick around, you start getting invited into different communities, you end up with a proud count of EIGHT stars on your repository and at some point you inevitably find yourself trying to fit into
Build in Public: Week 8. We Finally Deployed This Thing
Last week technically never happened. We didn’t skip a post, didn’t disappear into Christmas and New Year food comas and definitely didn’t spend a suspicious amount of time eating baked goods instead of shipping software. Let’s assume we simply compressed time and
Week 7: Shipping While Tired (or: Still Alive, Surprisingly)
This week was quiet. Not because nothing is happening, but because after six weeks of pushing, adding platforms, adding metrics, debugging queues and arguing with reality, we’re tired. The kind of tired where you stop dreaming about new features and start dreaming about “everything still works tomorrow&
Build in Public: Week 6. Trying to Add More Social Platforms
Last week was about observability. We added metrics and dashboards so we could see what the system was actually doing instead of relying on intuition. So this week wasn’t about inventing something new from scratch. It was about answering a very practical question: can we extend the same
Build in Public: Week 5. The Week We Finally Measured Things Instead of Just Hoping for the Best
Last week I ended with a dramatic cliffhanger: “We need metrics!” And then immediately regretted it, because “metrics” is one of those words that sounds simple until you realize you now have to measure things сonsistently and over time. And then look at the numbers
Build in Public: Week 4. The Messy Middle Of Building An AI Agent
This was supposed to be the week of a polished demo video and a clean “here’s how you use our API” walkthrough. Instead, it turned into the week of staring at half-finished pieces, poking at logs and wondering why we voluntarily chose Instagram as our
Build in Public: Week 3. First Survive Discovery, Then Enjoy Analysis
Last week I noticed something annoying: the engagement on my Week 1 and Week 2 posts dropped, even though the content was objectively good. So I asked Perplexity when developers actually read dev.to and the answer was basically: please stop posting on Saturdays. No one is there. From there,
Build in Public: Week 2. How Do People Even Find Influencers?
If you remember from the last update , we had our first real conflict: Node.js vs Python. Well, democracy has spoken. My "many" LinkedIn followers voted and the winner is Node.js. So this week we’re continuing with one backend, one direction and slightly fewer arguments.
Build in Public: Week 1
The first week wasn’t particularly shiny. We mostly tried to move from our old n8n setup to a normal backend and figure out what “normal” even means for us. Somewhere along the way we also had our first team conflict and our first real issue with
Build in Public: Day Zero
A few weeks ago we built an agent called WYKRA for the Real-Time AI Agents challenge powered by Bright Data and n8n . It was a small experiment that could accept a natural-language query like “I run a small bakery in Barcelona, find influencers who talk about bread