Reqit retweetledi
Reqit
34 posts

Reqit
@_reqit
Open source API client. Local, Git-native, zero telemetry.
Katılım Mayıs 2026
1 Takip Edilen16 Takipçiler

Build in public is kinda broken. But not in the way we think.
The concept itself is not broken, but the execution is.
You’re posting your process like it’s the product. But It’s not. Your results are the product.
Many of us post code snippets nobody asked for. While sometimes we post motivational quotes we didn’t live yet.
You post your selfie on your workspace with you large monitor. And tbh that’s all noise.
Ive realized that it just tells people that you’re busy, not that you’re worth following.
Nobody wakes up in the morning wanting to watch someone else work.
They want to see what the work became.
So here’s my advice:
Instead of saying “Today I’m going to build the auth flow”. you should say “Auth flow shipped. Took 2 days longer than I thought. here’s the mistake that cost me.”
Instead of posting “Grinding hard today 💪”. You should say “Hit 500 users this week. The thing that made the difference wasn’t what I expected.”
The pattern I’m trying to drive at is that you should lead with what you did, then the milestone, then the lesson, all Past tense. With Real outcomes. Something the reader walks away with.
Now, this matters most when you have zero audience, because You don’t have a reputation carrying your boring updates yet.
As someone still trying to grow an audience, Every post you make is an audition.
The ones who give value before they ask for attention are the ones who get it.
So please, Stop narrating the journey and Start posting the proof.
Victor@echo_vick
Many people are going about “Build in Public” and “Post your work” the wrong way. I’ll explain this in detail in another post.
English
Reqit retweetledi
Reqit retweetledi
Reqit retweetledi
Reqit retweetledi

@Chizzy_X_ @HalxDocs Reqit is a local-first, git-native API client. think postman, but your collections live in your repo, not someone else's cloud.
English
Reqit retweetledi

Postman just killed free team collaboration. We built reqit instead.
Your API collections, as plain JSON in your repo. No cloud, no seat limits — just Git.
Fast, native, yours.
→ github.com/HalxDocs/reqit
English
Reqit retweetledi
Reqit retweetledi

Every time postman for testing Apis, Postman for this, Postman for that.
Una no dey use @_reqit
Bro is faster local and doesn't eat your ram like Postman's electron.
Elliot Otoijagha@BuiltByElly
Every time Nodejs for backend development, Nodejs for this, Nodejs for that Una no dey use Bun?? 😂 Bro is faster than light itself 😆
English
Reqit retweetledi

Why are you all saying none 😭😭 Haven't you tried @_reqit. No bloat, no paywalls, no telemetry. Just clean API testing the way it should be.
Samay@Samaytwt
Which API testing tool is a worthy competitor to Postman?
English
Reqit retweetledi






