
P. Tech bro
385 posts

P. Tech bro
@ptech3net
🇳🇬💻🪩Software Engineer|Web 3 dev | C# .Net Engineer⛩️ Microsoft, Azure MVP | Mentorship🪩 | Lead Engineer🪩 | Solution delivery ⛩️✈️
Remote Katılım Mayıs 2022
295 Takip Edilen198 Takipçiler
Sabitlenmiş Tweet

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. 🚀
English

@iamsasha_uiux @Akintola_steve Na why most of them will lead dev astray 😂😂😂🤌
English

@Akintola_steve Team lead still Dey find this kin money o
English

@omocal4u @Akintola_steve Abeg if you need .Net dev ooo , shook me inside your company
English

@Akintola_steve The grad we employed last year from 9ija is being paid £45k p/a. I believe this has increased this month end to around £55k. This is grad with no experience
English
P. Tech bro retweetledi

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.
حسين@flyboydayo
i actually reached the interview stage of this role.💀 God run it to the endddd.
English

I made my first million at 16 🙂
匚HIDI@Cyber_chidi
I just realized i made my first 1 million at 17. When did you make yours?
English

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 🌚🌚🌚🌚
English
P. Tech bro retweetledi
P. Tech bro retweetledi

















