Oladipupo O. Fredrick

Somewhere building solutions.

[tobi @oluwatobiexe]

strongly believe everyone in a tech company should do sales for one month… try selling the nonsense you’ve been attending daily standup for.

[Oladipupo O. Fredrick @d_name_is_fred]

🔥🔥

[OluGB 🦋 @TechProd_Arch]

We built @theflutterwave to connect Africa to the world—and the world back to Africa via seamless payments.

Now, together with @0xPolygon, we’re making that vision faster, cheaper, and truly borderless.

Stablecoins on @theflutterwave mean:
💼 Enterprises get real-time settlement, not T+2
🏪 SMBs can pay suppliers instantly globally and also receive payments in stables
👨🏾‍💻 Consumers send money home in seconds and also get paid in stables

We’re proud to be bridging traditional finance and blockchain—securely, at scale, and for everyone in Africa.

Pilot 2025 → Full rollout 2026.

[Adedapo @_aaadedapo]

You don’t realize the extent of misinformation on here, until it touches your area of expertise. Na so you go just dey open mouth.

[Oladipupo O. Fredrick @d_name_is_fred]

Since AI has gone mainstream, I’ve noticed a few recurring myths that keep coming up in conversations with both technical and non-technical people. Here are three I hear most often:

“AI is like human intelligence.”
Not quite. AI doesn’t “understand” the way humans do. It recognizes patterns in data and predicts outcomes based on probabilities. It can sound smart, but it’s not thinking, it’s calculating.

“AI will replace all our jobs.”
History shows technology shifts jobs more than it eliminates them. Roles evolve, new ones are created, and humans + AI together are far more powerful than AI alone.
For example, ATMs arrived, people thought bank tellers would disappear. Instead, teller roles shifted toward customer service and advisory work, while banks opened even more branches.

“AI is magic.”
Behind every impressive AI output are mountains of data, careful model training, and engineering trade-offs. It’s science and engineering, not sorcery.

The way forward isn’t about fearing AI, but about learning how to use it responsibly, creatively, and ethically.

#ArtificialIntelligence #SoftwareEngineering #TechMyths

[Santiago @svpino]

Literally everyone is freaking out over Codex like they didn’t do the exact same thing for Devin, Cursor, DeepSeek, and every GPT drop since 2.0.

The hype cycle resets every 3 weeks, and we all start everything all over again.

This is what we'll see over the next few days:

• OpenAI employees will claim they have been using Codex for a while, and it's writing all of their code.

• A few people will tell the story of how they casually asked Codex to finish an old project, and it did it all, and it was perfect.

• AI influencers will litter our feeds with "90% of people don't know this Codex trick" and "Cursor is dead" threads.

• AI doomers will tell us how the article they published in 1989 explains why Codex will never work.

• VCs will congratulate themselves and write posts about how Codex will enable the next trillion-dollar market.

• Someone will write a Medium post titled “How Codex Made Me a 10x Engineer (And Saved My Marriage).”

• 20% of YC founders will pivot their startups to Codex-related stuff.

And this will continue until the next shitty autocomplete drops, and we all forget about Codex and start the cycle all over again.

[Oladipupo O. Fredrick @d_name_is_fred]

Whether you're a software engineer, architect, or tech enthusiast, this article offers valuable insights into building robust and scalable systems with DDA.

Read the full article here https://t.co/I86IjSJuae

[Oladipupo O. Fredrick @d_name_is_fred]

After taking a break for couple of weeks, Part 2 is here: Scaling Systems with Domain-Driven Architecture

In Part 1, we explored the foundational concepts of Domain-Driven Architecture (DDA).

[Oladipupo O. Fredrick @d_name_is_fred]

What to expect:
➖Strategies for improving scalability and maintainability using DDA
➖Real-world examples from industry leaders like Netflix, Uber, and Amazon
➖Best practices for implementing DDA effectively
➖Scenarios where DDA might not be the optimal choice

[Alex Hormozi @AlexHormozi]

The single greatest skill you can develop is the ability to stay in a great mood in the absence of things to be in a great mood about.

[Paul Graham @paulg]

Living in past eras.

[Oladipupo O. Fredrick @d_name_is_fred]

https://t.co/BaexN9cn8p

[Oladipupo O. Fredrick @d_name_is_fred]

Domain-Driven Design (DDA): A Game Changer for Scalable Systems?

[Oladipupo O. Fredrick @d_name_is_fred]

In a two part series, I discuss DDA in depth, it’s core components, when and how to use it, what benefits you gets, and common pitfalls to avoid.

[Oladipupo O. Fredrick @d_name_is_fred]

Optimising API Performance with Asynchronous Processing & Queues

APIs sometimes struggle with high traffic due to synchronous processing—forcing users to wait while tasks like email notifications, payment processing, or data imports run.

[Oladipupo O. Fredrick @d_name_is_fred]

@trikcode 💪