XCRX Wadda

Software developer. Started at 21 y.o Loves crypto . 3X shitcoin survivor. Risk taker

Founder •tg bot @xwaddabot •Shadowmax proxy
| Dream it🎩

[XCRX Wadda @keniko1297]

[ Day 5. ]
I will be uploading my daily progress starting 2022
#reactnative
#100DaysOfCode

Let's roll ...

#codinglife

[XCRX Wadda @keniko1297]

@TweetByWale Germany

[XCRX Wadda @keniko1297]

On this day, we introduced something different.

An AI-powered Telegram escrow experience — available 24/7, instant support, instant releases, and built for speed.

Proud to be building the future of escrow. 🚀
https://t.co/P5WeD1Usn5

#telegram
#telegrambot
#escrowbot

[Nduati The Geek 🤓 @nduatirobert_]

Kenyan developers have a problem of communication and deadlines. Most are very incompetent and unprofessional.

[Harshil Tomar @Hartdrawss]

BACKEND DEV skill levels (1-30) :

Level 1-5 : Just Started
1. Copy-paste Express boilerplate. No idea what half of it does.
2. Can make a GET request return something. Anything.
3. Write a route. Put the DB query directly inside it.
4. Connect to a database. Break it immediately.
5. Understand what a REST API is. Implement it badly.

Level 6-10 : Getting Dangerous
6. Heard of MVC. Put everything in one file anyway.
7. Deployed something to a server. Doesn't know how it works.
8. Auth with JWT. Stored in localStorage. Moving on.
9. Understand what an index is. Never added one.
10. Handle errors with try/catch. Log them. Ignore the log.

Level 11-15 : Actually Building
11. Separate routes, controllers, and services. Feels like an architect.
12. Environment variables. .env committed once. Will never speak of it.
13. Connection pooling configured. App doesnt crash under load anymore.
14. Parameterized queries. SQL injection is no longer a ticking bomb.
15. Understand N+1 queries. Still write them sometimes. Catch them in review.

Level 16-20 : Production Territory
16. Migrations. Schema changes are version controlled.
17. Proper error handling. Custom AppError class. Structured responses.
18. Rate limiting on sensitive endpoints. Not just auth.
19. Request validation with Zod or Joi. Before any processing happens.
20. API response serialization. Password hashes never leave the server.

Level 21-25 : Senior Thinking
21. Queue-based architecture. Long jobs dont block the request cycle.
22. Caching strategy. Redis. Know when to use it, when not to.
23. Proper logging with levels. Can debug a production incident from logs alone.
24. Horizontal scaling. Stateless design. Sessions not in memory.
25. Database transactions. Multi-step operations never leave data inconsistent.

Level 26-30 : The Builders
26. Design an API that a frontend dev can consume without asking you questions.
27. Review a codebase and know exactly where it'll fail at 10x traffic.
28. Onboard a junior without rewriting what they build.
29. Make architectural decisions and explain the tradeoffs clearly.
30. Your API docs are so good that integration takes hours, not days.

Drop your level below.

[CZ 🔶 BNB @cz_binance]

Finally arrived, Freedom of Money. Hard copies.

[Jeremy @jeremyct]

Crypto has ruined my life honestly

I’m 30, going 31. Down to my last 3 Sol with no job willing to hire me.

Caught in the wars of launchpad that destroyed all the volume of anything to run organically, nowadays purely insider plays or caballed tokens.

In debt of over $55k borrowing from friends and family in a span of 7 months

Now i’m not sure where to even start with my life, feeling depressed almost every single day.

Should have never started crypto in the first place.

[Ujjwal Chadha @ujjwalscript]

STOP calling yourself a "Full Stack Developer." That title is almost dead. 🚨

If your resume's biggest flex is that you can build both a React frontend and a Node CRUD backend... you are competing with a $20/month AI subscription. And you are losing.

In 2026, AI is the full stack. The ability to write boilerplate across the stack is no longer a premium skill; it is the absolute bare minimum baseline.

If you want to survive the current market, you have to completely rewrite your career story. Companies are no longer hiring "code translators." They are hiring Product Engineers.

Here is what your resume actually needs to prove right now to get past the hiring filter:

1. Partnered Execution (Over Ticket Pushing)

Don't just list the frameworks you used. Show how you partnered directly with business to solve a real, messy problem. Did you push back on a bad product requirement? Did your architecture directly unblock the sales team or save cloud costs? You are a business partner first, and an engineer second.

2. Architectural Restraint

Junior devs use AI to generate 10,000 lines of code. Senior devs use AI to delete it. Highlight how you managed technical debt, simplified complex system designs, and built scalable, "boring" infrastructure that doesn't crash at 3 AM.

3. The "Last Mile" Delivery

AI gets a project to 90% incredibly fast. But that last 10%—handling the bizarre edge cases, the concurrent database locks, the messy physical-world logistics—is an absolute nightmare for an LLM. Prove you are the person who knows how to drag an AI prototype across the finish line into a stable production environment.

[Rohit @rxhit05]

The reason why 90% of Vibe coded SaaS dies after launch:

- No input sanitisation
- No error boundaries
- Hardcoded API keys
-Tokens in localStorage
- Sessions never expire
- No Stripe webhook verification
- Reset links never expire
- Sync email sending
- No CDN for images
- No env validation
- No health checks
- No rate limiting
- No pagination
- No DB indexing
- No CORS policy
- No DB pooling
- No role checks
- No logging
- No backups
- No TypeScript

[XCRX Wadda @keniko1297]

@mbiti_mwondi Proxy watumie shadowmax proxy 🔥 iko very undetectable

[XCRX Wadda @keniko1297]

@mbiti_mwondi Proxy watumie shadowmax proxy 🔥 iko very undetectable

[XCRX Wadda @keniko1297]

@devlatifi @MongoDB I have the same problem here

[Cap-EO 👨🏾‍💻 @EOEboh]

You're already a great developer, you just need to improve your sales skills

[avrl ☘ @avrldotdev]

10 API design concepts to learn for backend:

0. Idempotency
1. Pagination (cursor/offset)
2. Rate limiting (DDoS protection)
3. Versioning (backwards compatibility)
4. Filtering/Sorting (query flexibility)
5. Timeouts & Retries
6. HATEOAS
7. API Gateway
8. Partial Responses (field selection)
9. Error modeling (consistency)

[XCRX Wadda @keniko1297]

@maheshnani122 100 paying users all the way, you can scale upto 1000+ and earn more

[XCRX Wadda @keniko1297]

@vivoplt Vs+claude

[XCRX Wadda @keniko1297]

@bitfunded Hi

[Suni @suni_code]

Interviewer:

If a user uploads a 5GB file but loses internet halfway,

how should the backend handle resuming the upload?

[XCRX Wadda @keniko1297]

@SafaricomPLC what's not happening with other people's funds

[Eric Djavid @ericdjav]

1 Suitcase.
1 Backpack.
1 Laptop.
$0 VC funding.

Just a one-way ticket and the obsession to build something people actually want.

The world is the new office. Let’s work.

[Robinson Honour @honour_can_code]

Lecturer: Have you guys heard about github before?

Me that built a full hosting provider:
“No ma”