SWE @Infor | ex-Arcserve | Learning production grade ML backend systems
Warangal
Joined December 2025
- Tweets99
- Following117
- Followers14
- Likes92
Pinned Tweet
馃殌 Cortex V2 is live.
V1 gave you the notes. V2 helps you actually remember them.
Cortex is a free, open data-science learning platform, and this update is built around one simple idea: learning only counts if it sticks. So I added the tools that make that happen:
I put my data-science notes into an open-source project called Cortex.
It's an interactive roadmap that goes from Python foundations to deployment.
I'm excited to share that i am joining Infor as a SWE. I was occupied for a couple of weeks for the formalities and pre boarding. I need to continue with my side project shortly.
We locked the account (last post), but we haven't locked the door.
Attackers can still flood the login API with millions of requests, causing a DoS even if they don't guess the password.
Implementing "Account Lockout after 5 failures" seems easy.
if (failures >= 5) lock()
鈥婤ut in backend systems, this logic has a fatal flaw: Concurrency.
鈥婬ackers don't attack sequentially. They send 50 requests in parallel.
How do you guys create and store architectural diagrams and other pictorial block diagrams?
With minimal time
We have TraceIDs in our logs (from the last post). But how does the client see them?
鈥婭 stopped returning custom error objects like { status: 500, message: "oops" }.
鈥婭'm using RFC 7807 Problem Details, the standard error format built into Spring Boot 3.
It doesn't matter what your Y intecept is what matters is your slope
Even if the starting point is different, consistent work will give you exponential results in the long run
Just some motivation for the folks who are having burnout or self doubt..
Why are interviews so undeterminsitic?
How can we increase our chances of cracking them? What are your thoughts?
After securing the Auth system, I hit the inevitable distributed systems nightmare: Observability.
鈥婭 need to trace a request across boundaries: from the HTTP API -> Database -> Background Async Events.
鈥婤ut I hit a wall because of my tech stack.
I spent hours debugging a critical security bug caused by a single database nuance.
鈥婽he feature: Refresh Token Reuse Detection.
The goal: If a token is reused (replay attack), the system must instantly revoke ALL sessions for that user to stop the attacker.
Security isn't just about login; it's about breach containment. I implemented Refresh Token Rotation with Reuse Detection.
Read full thread for more details 馃憞
I use @Transactional(noRollbackFor = TokenReuseException.class). This forces the system to commit the revocation and security logs to the database, even while returning a 401 Error to the client.