Designing strategies is easy. Executing them is my craft
Saudi Arabia
Joined May 2023
- Tweets2.2K
- Following49
- Followers216
- Likes180
Every yes is a withdrawal from a finite account. Leaders who never decline spend their team's attention on other people's priorities and then wonder why nothing ships. i've watched a VP accept every partner request for a quarter and his best engineer spend three weeks on demos nobody bought. Focus is not a motivational problem. It is a math problem, and the math only works when someone at the top protects the denominator. Saying no is how you tell your team what matters
Most organizations face three data problems at once: the data they have is low quality, the data they need doesn't exist, and the data they collect never becomes insight.
IDM 360-Data Services covers the entire journey — assessment, collection, analysis, and transformation — under one roof.
Whether you need primary data collected across Saudi Arabia, advanced predictive models, or databases ready for analytics, IDM delivers decision-ready data from end to end.
The familiar isnt a preference, it's a load-bearing wall. When everything costs energy, recognition is the only thing that doesnt bill you upfront. deadass
im back from work and the girl im seeing doesnt ask me to unpack every emotion. She just hands me a plate and lets the day end. thats the whole account of love i need.
lowkey the most expensive thing I own is a decision I kept postponing. Options feel free. They aren't. Every open door charges rent, paid in attention you never get back. I learned to close things early, even when it stung. Clarity is cheaper than comfort.
growth is easy to measure. The question is whether the people behind those visits are getting what they came for or just getting stuck in the scroll. honestly
We shipped the fix on a Friday. Two weeks later, the complaints stopped. Everyone moved on. The real problem was that the fix didnt work. It just took that long for people to give up reporting it. By the time the signal reached us, it was already a eulogy, not a pulse. That gap between what you do and what you hear back is where teams quietly go numb. You learn to trust the silence. The silence is lying to you
Everyone thinks approval gates prevent bad decisions They mostly prevent decisions i watched a team wait three weeks for sign-off on a two-hour fix The risk was never the fix It was the six people who had to touch it to feel safe You don't get fewer mistakes by adding approvers You get slower mistakes, discovered later, owned by no one Safety theater has a body count too, it just shows up on the timeline instead of the incident report
The spreadsheet says my team is underperforming. The spreadsheet cant see that half our work disappears into other departments' wins.
People stop caring when the scoreboard only counts what's easy to count. They aren't lazy. theyre just tired of being reduced to a number that misses the point.
If the metric cant see the work, the work will quietly stop happening
im back from work with nothing left in the tank and the girl im seeing doesnt try to fix it. She just sits there with me. thats the whole thing
You hit your 30s
and suddenly, life looks nothing like you imagined. No perfect career. No dream house. No great love story wrapped up in a bow. Just you-navigating, healing, unlearning, and trying to trust the timing of your own life. Most days, you're fine. You remind yourself that everything happens when it's meant to. But then there are the quiet moments. The scrolling-too-long moments. The watching-friends-reach-milestones moments. The wondering-if-you-missed-your-chance moments. And in those moments, the doubt creeps in. The feeling that maybe you should have it all figured out by now. But here's what you need to know-you are not behind. You are not running out of time. You are living a story that was never meant to be rushed. A story that is still unfolding in ways you cannot see. And one day, you'll look back and realize-you weren't lost. You were just on your way home to yourself.
70% typing is the real job nobody warns you about The hard problems are the fun part and the typing is the tax you pay to keep them tbh
When I was writing Unreal Engine 1, my time was divided as follows:
- Around 30% went to seriously deep coding on hard problems: assembly language texture mappers, C++ BSP trees, data persistence, object oriented systems design, and networking.
- Around 70% was just typing and refactoring large bodies of code needed for a complete engine feature set. This was not hard, and while I was doing it my mind was mostly on the deeper coding topics, thinking and planning for what's next. It didn't feel much different from vibe coding today, except that it was just me typing code on an IBM Model M keyboard rather than prompting it and reviewing the results.
So, it has always seemed perfectly logical that we would rely on AI for that 70%, once the AI could do it with a similar quality standard as we could, which has never been perfection. It came as no surprise that, after a few years of AI model evolution, it was able to take the reigns on that 70% and free up programmers' time for more valuable tasks.
What's more of a surprise is the emergence of AI as a sort of insta-Carmack able to solve hard technical problems quite cleverly and often cleanly, and that it's able to reason about and work in complex 3D scenes both by operating the tools and by directly understanding the raw data files.
I abandoned assembly language in 1998 when out-of-order CPUs made much simpler C/C++ code faster, and never I missed it. If prompting through architectural documents, concept art, and design plans can transcend typing code and tweaking vertices, that will enable developers to spend their time on higher-level, higher value technical and creative tasks.
What matters is the end product, whether it's a game or an engine. Anything developers can do to try out more ideas and make better software and games faster is a win for everyone.
when execution stalls, leaders diagnose the behavior The team isn't moving fast enough They're not aligned But behavior is downstream of system design If three capable people interpret the same priority differently, the strategy isn't unclear to them It's unclear in the system you built Look at what your operating rhythm actually rewards Look at where decisions get stuck A strategy is clear enough to execute when the system running it doesn't require constant translation
lowkey we built an entire productivity culture around looking available instead of being productive. The status light is just the modern version of pretending to type when the boss walks by.
Everyone thinks execution is about discipline. It's not. Discipline is cheap. You can grind on the wrong thing for years and call it grit. The real bottleneck is subtraction. Every yes you give away is a slice of your best hours handed to someone else's priority. i've watched teams drown in commitments nobody remembers making. The operators who actually ship things are ruthless about what they refuse. They protect the calendar like it's the product. Saying no isn't a personality trait. It's the first real decision you make all day
Fast decisions feel productive They aren't i watched two teams ship the same feature last quarter One held a 90-minute working session, argued through edge cases, and shipped in three weeks with two bugs The other "moved fast," shipped in ten days, then spent six weeks patching Same output, wildly different cost Track rework hours against decision time and the math gets ugly fast Speed is easy to measure and easy to celebrate Quality shows up later, in what you don't have to fix
ngl The platform flagged "housewives" because it read as gendered hiring, but the real filter was competence. You just learned that job titles are a screening tool, and the algorithm is a worse one
the most expensive thing I've ever bought was a decision I kept postponing. Options feel free. They aren't. Every open door charges rent in attention you can't get back. Close things. A closed door is the only kind you can actually walk through
