Curated development tutorials from top sources. Filter by language.
Nakodo runs creator outreach for brands, and a question from a customer mid-campaign is usually urgent to them and boring to answer: how many creators
Every creator Nakodo suggests comes with a sentence explaining the fee. The last line of it is the one brands actually read: About 13K views on a sp
Nakodo works out what a brand should offer each creator, and then an email goes out with that number in it. The arithmetic produces things like 56.32
Nakodo suggests what a brand should offer each creator it finds. Two different questions are involved and it took a rewrite to see that they were diff
Nakodo finds creators on YouTube, Instagram and TikTok for a brand and runs the outreach. Everything about money in the app hangs off one number per c
Most OpenAPI generators are "generate once and forget." You run them the first time and everything looks great. Then the backend changes an operation
A signup test can fill every field, click Create account, and still leave an important part of the journey unchecked: the verification email. Did it
A percentage rollout looks trivial until two runtimes disagree about a single user. In a self-hosted feature flag project of mine, rollouts hash the c
I wanted a simple API that opens a page in a real browser and returns the rendered content. Most sites hide the useful HTML until JavaScript runs, so
Why the Redesign? My previous portfolio had become outdated and didn't represent the quality or complexity of the systems I build today[cit
Building a Garments Management System with React Native and .NET Web API I developed a Garments Management System using React Native, TypeS
Shipping AI agents that actually work in production often hits a wall. You can prototype something quickly, sure, but moving from a proof-of-concept t
Nakodo has two export routes, and they answer different questions. One is a product feature: a brand wants the creators a campaign found as a spreads
Hello Engineers, in this article we will see how Redis can be used as a job scheduler. Most of us mainly use Redis to cache very frequently accessed d
Nakodo's schema is 23 tables and 36 indexes in a single 1,118 line schema.ts. The drizzle/ directory next to it holds 28 SQL files, numbered 0000 to 0
Nakodo has 53 exported Server Actions across eight actions.ts files. Every one of them returns the same shape, nothing in the UI uses a try/catch, and
A server component cannot know what time it is where you are. It knows the instant, it does not know your offset, and nothing in a request tells it: t
Nakodo has 76 public pages. 63 of them are rendered by eight dynamic routes, because the page itself is not a template: it is a TypeScript object in s
Sometimes I don't want to run code. I just want to read it and scribble on it, like a PDF. So we made AnnotateCode. Paste a GitHub link, then highlig
An LLM response cache sounds simple: same model, same prompt, return the saved result. But with structured output, the prompt is only part of the req