Emma

tech writer @hackmamba | part-time dev, full-time ranter

[Emma @emmashouldwrite]

tried writing “better docs” without actually knowing what that meant 😅

this helped me get clear on what good API documentation actually looks like

https://t.co/yiPJ89pPxQ

tysmmm @xamfonos_

[Emma @emmashouldwrite]

@boki_io 🔥🔥

[Ekene Eze @kenny_io]

@boki_io Boki 👌🏽

[Boki @boki_io]

Kenny Eze is a technical writer, developer advocate, and Founder of DXMentorship.

He knows what good content operations look like because he has lived the broken version of it.

His take on Boki: a fresh breath for content operations and working with marketing teams.

Boki keeps that context intact from research to distribution. That is the difference @kenny_io noticed.

[Emma @emmashouldwrite]

When to Choose On-Premises vs. Cloud for Vector Databases

https://t.co/yJ4rQVs1L6

[Emma @emmashouldwrite]

for everyone who are looking for jobsss

[Hackmamba @hackmamba]

Last Friday, we dropped a fresh batch of roles on our DevTool Jobs board. 19 new openings, and a lot of them are still live.

More are coming this week.

We pull from companies that are deep in the developer tooling space, so if that is the work you want to do, the signal-to-noise ratio here is worth your time.

Find your next role: https://t.co/qCTfcSt0tL

[Hackmamba @hackmamba]

Developers in general prompt Bit Cloud the same way they'd prompt any other AI tool: describe the full app, and expect a working result.

What comes back instead is a proposed component structure: a note list, an editor, and supporting utilities. No clickable UI yet. A lot of people assume the prompt failed and stop there.

No, don’t think of it as a prompt failure. BitCloud is doing what a senior engineer would do: laying down reviewable components before locking in higher-level decisions. The prompt is just wrong for what the tool is designed to produce.

The guide by @bitcloud_ covers how to write prompts that work with that model.

Article link below.

[Coder girl 👩‍💻 @dev_maims]

Real 😅...

[Emma @emmashouldwrite]

check this job vacancy guys

[Hackmamba @hackmamba]

We're hiring a Technical Video Content Creator.

You're an engineer who's been making videos on the side. Or a creator who can actually read a stack trace.

Either way, you've figured out that explaining a hard technical concept to a camera is the most fun you can have at work.

You will make videos for developer tool companies, think tutorials, deep dives, and product walkthroughs end to end. We handle the gear. You bring the knowledge and the presence.

Fully remote, based anywhere in Europe.

If this sounds like you, the link to apply is in the comments.

[Emma @emmashouldwrite]

@trying_to_exits More than enough really

[Emma @emmashouldwrite]

ME EVERYDAY

[𝐑.𝐎.𝐊 👑 @r0ktech]

Getting Ideas to solve a bug

[William @iChuloo]

Show me harder copy ✨

[Hackmamba @hackmamba]

Python switch statement.

Python 3.10 introduced match-case, a structural pattern matching syntax. And it does a lot more than just replace if-elif chains.

Beyond basic value matching, you can match multiple values in a single case, add guard conditions with if, destructure tuples and sequences directly in the pattern, and handle state machines cleanly without nesting.

This @roadmapsh article walks through all of it, including when match-case is genuinely the right tool and when a dictionary mapping or a plain if-elif block is still the simpler choice.

Link in the comments.

[Emma @emmashouldwrite]

This is my sign to look for more work 💪

[Hackmamba @hackmamba]

This is your sign to start the week by checking what roles are out there.

We update our devtools job board every Friday with 20+ new roles across DevRel, technical writing, developer marketing, and more.

Check the latest listings below.

[Hackmamba @hackmamba]

We have been a developer growth agency for a while. We just never said it out loud.

Here is how it all started.

2021 - @iChuloo started Hackmamba because technical content for devtools was bad. Not mediocre, bad. Written by marketers who had never opened a terminal. He had spent years as a developer and developer advocate. He knew what good looked like and clients kept coming back for it. At some point the work was too much for one person, so he brought in a few developers who could write. That was the team.

2022 - Word got around. We became known as the go-to for technical content, the kind that developers actually trust. Three documentation clients a month on average, strong retention, and a reputation that was genuinely earned. The market had a label for us. Technical content agency.

2023 & 2024 - The same clients trusted us with more than content. They had been burned by generic SaaS marketing agencies that did not understand developers. So they brought everything else to us. Product launches, community programmes, hackathons, Reddit strategy, paid media. We never pitched any of it. They came because the trust was already there.

2025 - Revenue grew 400%. Six-month retention held above 70%. The inbound we were getting was more growth than documentation.

That told us everything we needed to know.

Anyone can build a product now. The moat is no longer the product itself. It is how you take it to market. How you reach developers who ignore ads. How you earn trust with a community that hates being sold to. How you build for AI agents and show up where developers and their agents are already looking.

That is the work we have been doing for @cloudinary, @roadmapsh, @coderabbitai, @mintlify, @theflutterwave, @actiandev and others, across content, documentation, community, events and paid media.

So we are making it official. Hackmamba is a developer growth agency.

We still strongly believe that all great product outcomes are downstream of great content. We'll always be authentic content producers, non-negotiable. But our north star is growth now. Helping devtools acquire developers/AI agents and build pipeline.

The website reflects this. About time.

Full story in the comments.

[William @iChuloo]

Summary: Posthog now has a coding agent.

Here’s a list of tools we use for different things but can all now code. I guess I need to figure which to cut/keep soon.

@posthog
@linear
@claudeai
@cursor_ai
@coderabbitai
@figma

and I wonder who’s next

Efficient issue tracking will be the next big problem to solve mid-term. @github here’s your chance to own more of the future.

[𝐑.𝐎.𝐊 👑 @r0ktech]

Changes 4000 lines of code
> git commit -m “minor changes”
> git push origin main

Leaves

[roadmap.sh @roadmapsh]

This backend developer roadmap has been revamped and outlines the steps needed to build and scale server-side systems. Learn the core technologies and concepts required for modern backend development.

https://t.co/flc9Uz96gc

[Hackmamba @hackmamba]

Browse new tech jobs here: https://t.co/UO3CKajVgU

[Hackmamba @hackmamba]

Looking for a job? We’ve added 23 new job roles to the devtools job board today.

If you have time today, make sure to go through them.
Happy Workers’ Day!

Link in the comments.

[Emma @emmashouldwrite]

The standard advice is "use RAG for dynamic knowledge, fine-tune for stable domains."

That's not wrong, but it's not enough for real architecture decisions.

51% of enterprise AI deployments use RAG in production, while only 9% rely primarily on fine-tuning. But research shows hybrid systems outperform either approach alone.

The gap between what's popular and what performs best comes down to team capability and cost structure, not which approach is objectively better.

This article by @actiandev provides a decision matrix that maps query volume, knowledge change frequency, and infrastructure maturity to a concrete recommendation so you're not guessing.

Dropping the blog link below!! 😊