OmoCipher || Omoteso Abdulalim @OmoCipher

Software Engineer,Programmer, C# .NET developer Agege, Lagos Joined January 2025

Tweets

17
Followers

64
Following

321
Likes

20

OmoCipher || Omoteso Abdulalim @OmoCipher

3 months ago

We’ve been sold a lie that "Stateless = Infinite Scale." In reality, most "stateless" microservices are just expensive wrappers for an overloaded Redis instance or a Postgres bottleneck. We traded simple local logic for complex distributed system failures.

0 0 0 2 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

3 months ago

Your system isn't "stateless." You just moved the bottleneck to the database and called it "scalability." State is like energy: it can’t be destroyed, only moved. Usually, we move it across a network hop that’s 100x slower than local memory.

0 0 0 3 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

3 months ago

The most expensive line of code is the one you didn't realize was running because it was hidden under a "clean" abstraction. Software isn't just poetry for humans; it’s instructions for a machine. Respect the machine.

0 0 0 1 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

3 months ago

"Clean Code" is becoming a mask for lazy engineering. We’re so obsessed with "readable" abstractions that we’ve forgotten how to talk to the hardware. We are literally suffering from Death by 1,000 Abstractions. 🧵

0 0 0 5 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

3 months ago

WORD FOR THE DAY "Clean code" is a liability if it hides what your hardware is actually doing—stop guessing and start profiling.

0 0 2 10 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

4 months ago

Check out my latest article: The Death of Performance by 1,000 Abstractions linkedin.com/pulse/death-pe… via @LinkedIn

0 0 0 14 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

When you've been debugging for 6 hours and finally realized you wrote conts instead of const😅🤣

1 0 1 44 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

Developer after fixing one bug… everything else breaks 😮‍💨

0 0 2 35 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

The top killer of performance isn't bad algorithms. It’s "Death by 1,000 Abstractions." We’ve become so reliant on heavy libraries that we’ve forgotten how the engine works. If you don't know what your code is doing to the CPU/Memory, you aren't optimizing-you're just guessing.

0 0 2 31 0

View Details

Asif Sayed @dotnetsme

5 months ago

C# Memory Tricks You Should Know About Unlock the secrets of efficient coding with these C# memory tricks! 🚀 Whether you're a beginner or a pro, these tips will optimize your programs and enhance performance. Don't miss out! 💡 #CSharp #CodingTips #MemoryManagement #Programming #DevCommunity

0 1 3 65 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

What i realize about memory allocation in C# is that the issue isn’t just creating objects, But in the wrong places Which can increase GC work Just be intentional about where and how often memory is allocated-especially in hot paths I'm now looking at my code with performance

0 0 2 27 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

C# devs - fighting allocations in hot loops? what's your current favorite trick? Mine right now: * Object pooling for reusable stuff across calls * .Clear() + pre-set Capacity on List<T> /StringBuilder Huge win in tighr parsing What working best for you?Drop Snippets.

0 0 2 42 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

Hey @X Algorithm If you're into •Frontend •Backend •Full-stack •DevOps •LeetCode •Al/ML •Data Science •Freelancing •Startups Drop a “hi". Let's connect🤜🏻📷 #buildinpublic #letsconnect #SoftwareEngineering

1 0 5 66 0

View Details

OmoCipher || Omoteso Abdulalim @OmoCipher

5 months ago

You know when creating new objects inside tight loops is one of the fastest ways to spike GC pressure in C#. Reuse instances wherever you can — especially in hot paths. Small change, massive difference in throughput. #CSharp #DotNetPerformance