Wesley Tokoi

Passionate Software Engineer 🚀 | Specializing in Mobile & Fullstack Development | Committed to constant growth with #100DaysOfCode | Opinions are my own. 📚✨

[Wesley Tokoi @tokoiwesley]

"Freedom isn't about doing more. It's about doing less, but better."

[Mosh @moshhamedani]

The problem with slop is you can’t see it if that’s all you’ve ever seen. Once you see clean code and clean architecture and appreciate the benefits, you can’t deal with slop anymore.

[Mosh @moshhamedani]

Claude Code has been super slow today and has been generating some of the worst code I've seen.

Good luck to those who think code reviews aren't necessary. You'll learn the hard way: one day the pile of AI slop will be so big that even the simplest changes take forever and break unrelated features along the way.

[Wesley Tokoi @tokoiwesley]

@OmbeniSheshe You bought an MF battery when what your vehicle needs is an EFB or AGM battery due to the i-Stop system. The price should be around 20k though.

[Mosh @moshhamedani]

CEO of Coinbase bragging that non-technical people are now using AI to ship production code. When a CEO says this, one of two things is true: either they don't know what production code is, or they're selling you a story.

This kind of hype is how businesses end up in real trouble. The people shipping the code and the CEOs cheering them on won't be the ones held responsible when it breaks. They collect their paycheck either way. Users will find out the hard way, once unreviewed code has touched their money, medical records, identities, private messages, kids' data, legal documents, critical infrastructure. By then it's too late.

Production code isn't a vibe.

[Wesley Tokoi @tokoiwesley]

Day 10 of #100DaysOfPython: I completed Section 10 - Beginner - Functions with Output. #100DaysOfCode.

[Wesley Tokoi @tokoiwesley]

Day 9 of #100DaysOfPython: I completed Section 9 - Beginner - Dictionaries, Nesting and the Secret Auction. #100DaysOfCode.

[Wesley Tokoi @tokoiwesley]

Day 8 of #100DaysOfPython: I completed Section 8 - Beginner - Function Parameters & Caesar Cipher. #100DaysOfCode.

[Wesley Tokoi @tokoiwesley]

@srishticodes Hi

[Vishal Rajpurohit @vishal_viitor]

𝗟𝗮𝗿𝗮𝘃𝗲𝗹 𝗿𝘂𝗹𝗲𝘀 𝗖𝗧𝗢𝘀 𝗺𝘂𝘀𝘁 𝗲𝗻𝗳𝗼𝗿𝗰𝗲 𝗯𝘆 𝗱𝗲𝗳𝗮𝘂𝗹𝘁

Laravel moves fast.
That’s exactly why it needs rules.

If you don’t set these early, you’ll enforce them later — under pressure.

Here are the Laravel rules every CTO should make non-negotiable 👇
𝟭. 𝗡𝗼 𝘂𝗻𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗱 𝗱𝗮𝘁𝗮 𝗳𝗲𝘁𝗰𝗵𝗶𝗻𝗴
If a query returns “everything,” it’s a bug. Large datasets must always be constrained, paginated, or streamed.

𝟮. 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 𝗺𝘂𝘀𝘁 𝗯𝗲 𝗶𝗻𝘁𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹
Lazy loading is never accidental at scale. If relationships are accessed, they must be planned and reviewed.

𝟯. 𝗜𝗻𝗱𝗲𝘅𝗶𝗻𝗴 𝗶𝘀 𝗽𝗮𝗿𝘁 𝗼𝗳 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘆
Any new filter, lookup, or foreign reference ships with an index — not as a follow-up task.

𝟰. 𝗥𝗲𝗾𝘂𝗲𝘀𝘁 𝗰𝘆𝗰𝗹𝗲𝘀 𝘀𝘁𝗮𝘆 𝗹𝗶𝗴𝗵𝘁𝘄𝗲𝗶𝗴𝗵𝘁
Anything slow, repeatable, or failure-prone runs outside the user request. Queues aren’t optional once traffic exists.

𝟱. 𝗖𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗮 𝗱𝗮𝘁𝗮 𝗲𝗻𝗴𝗶𝗻𝗲
If logic can be pushed to the database layer, it should be. Memory-heavy collection work is a red flag.

𝟲. 𝗣𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗺𝗮𝗻𝗱𝗮𝘁𝗼𝗿𝘆 𝗳𝗼𝗿 𝗹𝗶𝘀𝘁𝘀
No exceptions. If a screen can grow, it must paginate from day one.

𝟳. 𝗧𝗵𝗲 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗶𝘀 𝗻𝗲𝘃𝗲𝗿 𝗮 𝗰𝗮𝗰𝗵𝗲
Repeat reads require a caching strategy. Database load should represent truth, not convenience.

𝟴. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗶𝘀 𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝗱, 𝗻𝗼𝘁 𝗮𝘀𝘀𝘂𝗺𝗲𝗱
Query counts, execution time, and memory usage are reviewed regularly — not only during incidents.

𝟵. 𝗘𝗹𝗼𝗾𝘂𝗲𝗻𝘁 𝗰𝗼𝗻𝘃𝗲𝗻𝗶𝗲𝗻𝗰𝗲 𝗶𝘀 𝗮𝘂𝗱𝗶𝘁𝗲𝗱
Accessors, casts, appended attributes, and global scopes are treated as performance-sensitive code.

𝟭𝟬. 𝗦𝗰𝗮𝗹𝗶𝗻𝗴 𝗿𝘂𝗹𝗲𝘀 𝗮𝗿𝗲 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗲𝗱 𝗲𝗮𝗿𝗹𝘆
Every Laravel codebase needs written performance boundaries — before the team doubles.

Laravel doesn’t collapse because it’s slow.
It collapses because leaders let convenience replace discipline.

CTOs don’t need to block speed.
They need to protect the system from its own success.

That’s how Laravel products survive real growth.

[Wesley Tokoi @tokoiwesley]

@BuikeBuilds Done 👍🏾

[Wesley Tokoi @tokoiwesley]

Day 7 of #100DaysOfPython: I completed Section 7 - Beginner - Hangman. #100DaysOfCode.

[Wesley Tokoi @tokoiwesley]

@BuikeBuilds Thank you

[Wesley Tokoi @tokoiwesley]

@chris__sev Hi, I am interested.

[Wesley Tokoi @tokoiwesley]

@Beno10_MFC What about my firstname?! 🤔

[Wesley Tokoi @tokoiwesley]

Concurrency is NOT Parallelism, and every software developer should know (and understand) that.

[Wesley Tokoi @tokoiwesley]

@fidexcode It's just pure preference for what works for you as a developer, and the rest is nonsense. I use both light mode and dark mode depending on whether I am coding during daytime or at night.

[Anton Martyniuk @AntonMartyniuk]

Mark Zuckerberg scaled Facebook in 2005 - without Kubernetes, Serverless Functions, Redis, Managed Auth, Rust, or Kafka.

No fancy orchestration.
No distributed event streams.
No cloud-native anything.

Modern devs love to over-engineer.
We build as if our projects will scale to 1 million users tomorrow.

But here's the truth:
Most apps die with 100 users, not 1 million.

We predict every possible future case:
→ So we add layers, queues, caches, and microservices...
for problems that don't even exist yet.

That's not architecture.
That's trend-driven engineering.

Always architect your apps based on current needs (not possible future guesses), leaving room for extension and evolution.

Complexity kills projects - simplicity scales.

Don't design your MVP like it's Facebook in 2025.

Design it like Facebook in 2005 - simple, fast, and focused on what matters most: value.

👉 Join 16,000 software engineers who learn how to build software based on current needs and not the trends:
↳ https://t.co/dajCViEeyi

𝗕𝗼𝗻𝘂𝘀: every subscriber gets a PDF with 650+ exclusive resources for mastering C#, .NET, ASP .NET Core, EF Core, and Microservices.

——

♻️ Repost to help others learn how to build software based on current needs

➕ Follow me ( @AntonMartyniuk ) to improve your .NET Skills

[Wesley Tokoi @tokoiwesley]

@rqobela Turbo Pascal. My first programming language (2006) that I used for an examination project at the secondary school level in 2007. I never used it again since it was (almost) obsolete. I tried Visual Basic in 2008 then started learning C++ in 2009 in preparation for university.

[Wesley Tokoi @tokoiwesley]

Day 6 of #100DaysOfPython: I completed Section 6 - Beginner - Python Functions & Karel. #100DaysOfCode.

[Wesley Tokoi @tokoiwesley]

It's quite unbelievable that 14 years have already lapsed since I joined X (formerly Twitter) - from the good old days when Twitter #Bootstrap (the frontend framework) was first released to the public! #MyXAnniversary