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#, ASP.NET 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. 🚀

Nobody is building in public again…. You people are afraid of others cloning your project in 48 hours. 😂😂😂😂😂😂😂

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) ng.indeed.com/viewjob?jk=c82…

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.

Mail just came in and I got in. I got the role. I still have questions on how I got in amongst 1000 applicants, but again, alhamdulilah.

Welldone ✅✅✅✅

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 🌚🌚🌚🌚

DON’T JOKE WITH THIS DUA Yaa Allah, position me where I need to be, with the right people, at the right time. Ameen

Let’s have it. 🤭🤭🤭 I need answers to this

Please you people should vote 🤲🤲🤲Thank you

Well done 🙌🙌🙌

This year have applied to more than 5k companies and I only got 1 pre - offer 🤲🤲 Tech industry is …… Anyways Congratulations in advance to me ✅🤭😂

👇👇👇👇Let’s have it

Hi Everyone 🙌🙌🙌 How would you handle this scenario: Your system should only allow one active login per user. When the same user logs in from another device, 👉 the previous session should expire instantly, 👉 the old token should become invalid immediately. What’s the best approach to achieve this in a secure and scalable way? 🔐 Curious to see how different teams handle this 😌😌😌🙂‍↔️ Thank you’ll 🙌🙌🙌

Let’s go through this guys 🙌✅

What I’ve learned from recent discussions on application security 🔒 It’s not just about writing code, it’s about mindset. Both frontend and backend engineers have a role to play. As a backend engineer, always secure your application. Don’t rely on the frontend to enforce critical validations. Assume every request coming from the client can be tampered with. As a frontend engineer, don’t rely solely on HTTP status codes. Always verify the actual response from the backend, a status code can be faked, but backend truth can’t. Security isn’t something you add later; it’s something you design in from the start. Always think one step ahead of whoever might try to break the system. In short: Backend: build defensively ⚔️ Frontend: validate wisely 🧩 Both: think outside the box 💡 The moment you assume your system is safe is the moment it’s most vulnerable. And to my contributors 🙌🙌 @0x @ce3nerd Thank you Thank you 🙏

🙌🙌🙌