Hello everyone 👋
I’m a Backend Engineer, specialized in C# and the .NET technology stack.
I’ve spent years building production systems that actually ship 👌✅ Real users. Real deadlines. Real impact.
From fintech platforms to enterprise-grade APIs, my work as a .NET Engineer has always been about solving real problems, not just writing code.
I design and develop scalable RESTful services, focusing on clean architecture, performance, and security.
My toolkit includes C#, https://t.co/UCEI53IXk8 Core, EF Core, PostgreSQL, Docker, and Azure, and I’m always exploring better ways to build reliable systems that make a difference.
For a long time, I’ve been building quietly behind the scenes, improving systems, shipping features, and solving problems.
But not anymore.
It’s time to start sharing, learning in public, and connecting with other builders who take software seriously.
Let’s build, learn, and grow 🙌out loud. 🚀
My husband is in a meeting with another software engineer
Engineer: keep going down
Me: God forbid my husband will never go down in Jesus name 😂
Thank God say engineer no hear me 😭😂🤣
Cavista is hiring for C# .NET Engineer Level (I-II)
Interested candidate should
Click on the below link
C# .NET Engineer Level (I-II) https://t.co/oIM1ERtder
Got recommended out of 500+ engineers to handle 9 OWASP-related vulnerabilities on an app.
The original dev wasn’t available, and my name came up.
Grateful, years of working as a security-focused engineer in fintech are starting to speak.
Day 1/30 – Consistency Challenge.
Jumia homepage redesign,Focused on clear visual hierarchy, bold CTAs, and product discovery that feels effortless.
Good UX doesn’t shout — it guides.
What would you improve?👇
@Techyjaunt#30dayswithtechyjaunt@The_Irapada
A few weeks ago, I shared a post about OTP bypass.
I’d love to get your opinions and hear if you’ve handled this differently or found a better workaround.
My approach 👇
I maintain an OTP table with an enum that clearly defines the purpose of each OTP (e.g., login, password reset, sensitive update).
Since every OTP-protected action either creates or modifies data, I added a backend check:
•After an OTP is triggered, I verify whether the most recent OTP was actually validated or bypassed (based on the purpose).
•If the OTP was bypassed → block the database operation.
•If the OTP was properly validated → allow the action to proceed.
This way, I don’t rely on the frontend at all, OTP enforcement and validation are handled entirely on the backend
@ce3nerd 🌚🌚🌚🌚