david (@afrogodd) header
david (@afrogodd) profile picture

designer. artist. futurist. intergalactic surfer. ex @terrace_fi @deel @andela @fincrahq

cosmos
Joined April 2012
Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)Photo by david (@afrogodd)
Nov. 18, 2026, 5:16am EST The Voyager 1 spacecraft has reached a distance of one light-day from Earth.
1,322
53,381
3,710
309,194
9,590,761
david retweeted
You must write. You must visit the water. You must talk to the trees, and to God. You must love. You must remember. You must learn to eat better. You must call down your dead with drum and gin. You must—live. Again and again and again.
18
1,755
32
7,036
96,830
you’re not a perfectionist sha, neither are you too shy to put your work out there your ego is just too big and you don’t want to be seen trying and failing because of what you think of people who try and fail publicly you’re just scared of yourself
100
1,345
224
5,571
131,073
worldly things being a reward in the afterlife according to any religion that preaches against the love of worldly things, is a special type of fooling.
67
3,702
157
14,837
280,417
A culture that steals from the young by monopolising their peak productive years through price gouging and egregious rent seeking, charging twice, thrice or even four times what they paid for essential services, is operating an inverted structure where the old siphon from the young by leeching off their vitality like a desiccating parasite, when they should be nurturing the next generation rather than sacrificing it. There is no greater sign of narcissism in a culture, be it western materialist short-term greed or eastern self-sacrificing parent worship where the child is viewed as a unit of consumption to better and improve the lot of elders, rather than something that those elders should be cultivating and sacrificing for. The young of today have every right to be mad. They would be mad not to be.
72
667
27
3,981
85,797
this is fucking insane. wow
Real life, baby
1
264
people are starting businesses in lagos life.. me i want to start a church
6
1
15
980
was reading ted’s site & just remembered devcenter. devcenter was consequential to a lot of techies circa 2017 & devcenter square was one of the best places to be on the internet. learnt a lot, met acekyd, fari & got many awesome gigs. s/o to akinfals & other champs on the team
1
3
541
i'm convinced burnout has nothing to do with 'working too hard' and everything to do with betraying yourself for an extended period of time
Burnout happens when you work too hard with not enough meaning. "He who has a why to live for can bear almost any how" — Nietzsche
91
1,671
97
15,372
364,080
david retweeted
get your spark back nigga
1,233
34,637
2,036
266,389
4,837,203
a prototype is not a prd
22
10
6
170
10,764
it’s insaneee that this is elizabeth holmes and not some hollywood actress
Thirty-four days before she reported to prison, Theranos founder Elizabeth Holmes gave Nathan Fielder and Lance Oppenheim access to document her every move. That turned into a three-year project, and A24 will release the resulting documentary this October.
4
597
diff architectures for diff jobs
Loops vs. Graphs, clearly explained! loops are great, and they have a ceiling you can watch happen: a loop goes around. it produces, checks, corrects, and goes around again. after six passes you have one job, done very well. after six hundred passes you still have one job, done very well. Graph engineering fixes this by moving the decision up a layer: not how well one job gets done, but which jobs exist to be done at all. you need both, and here is the sentence that resolves the whole confusion: the loop lives inside a node. the graph lives between them. ↳ inside one unit: produce, check, correct, repeat until green ↳ between units: split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs the loop does not go away when you build a graph. it moves inside, and now there are three of them running at once on three things you would never have thought to run. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. one thing to know before you scale it. a loop that cannot fail is not a loop, it is a repeat with a bill attached. and the check people write is almost always the wrong kind. ↳ the test suite exits 0 is a check. the diff touches only the files in the plan is a check ↳ the output looks good, the model says it is confident, no errors were raised, none of those are checks that last one catches careful people. absence of an error is not evidence of correctness, and a loop built on it will confidently repeat a mistake until the budget runs out, with a clean log the whole way. and the one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓
5
262
“CLAUDE I’VE EXPLAINED THIS BUG TO YOU 10 TIMES AND YOU STILL KEEP BREAKING IT, THINK LIKE A SOFTWARE ENGINEER WITH 15 YEARS OF EXPERIENCE AND FIX IT PROPERLY MAKE NO MISTAKES”
128
631
81
7,045
663,544
david retweeted
when software had a soul there was a moment around 2005 when using a Mac felt like touching something alive. the dock bounced. the genie effect swooped. exposé scattered your windows like cards on a table. none of it was strictly necessary. all of it felt like someone cared – not about metrics, but about the feeling of using a machine. software back then had texture. it had a philosophy. you could feel the person behind it. someone made a decision to make that icon beautiful, to animate that transition just so, to write that error message with a little warmth. apps had personalities. some were weird. some were over-designed in ways that would make a modern PM flinch. but they were alive. the web was the same. personal sites were genuinely personal. blogs felt like letters. forums had regulars. you knew who made what. the internet had neighborhoods, and each one felt different. nothing was optimized for scale. things were made by people who loved what they were making. somewhere along the way, we traded all of that for growth. A/B tests flattened the edges. design systems standardized the personality out. everything got faster, smoother, more consistent – and somehow less interesting. the quirks were removed because they didn't test well. the warmth got cut because it wasn't measurable. we optimized our way into a world of things that work perfectly and feel like nothing. now every app looks the same. every interface follows the same patterns. every product speaks in the same calm, frictionless voice, siloed in their own little islands. the humanity got rounded off. and then came AI agents. and the speed got inhuman. now you can generate an entire product in an afternoon. ship a feature before lunch. spin up ten variations before anyone's had their coffee. the gap from idea to code is basically zero. which sounds incredible. and it is. but there's a catch. when making things are too easy, the slop comes for free too. mediocre things don't look obviously bad – they look fine. they work. they ship. they pass review. and now there are infinite of them. the internet is filling up with software that functions but means nothing. interfaces that are correct but feel dead. products made by agents, reviewed by no one, shipped into the void. this is the thing that keeps me up at night. not that AI will replace people who care. but that it will drown them out. here's what I still believe: the best things are made by people who couldn't help themselves. someone who lost sleep over an icon. who rewrote the same line of copy twelve times. who added an animation nobody asked for because it made the thing feel right. that obsession – that's not inefficiency. that's the whole point. AI doesn't make that irrelevant. it actually makes it rarer and more valuable. taste is not a markdown skill. caring is not a parameter. the weird, specific, "soul" thing you put into something – that can't be programmed into existence. the path forward isn't to make more slop faster. it's to finally give people with real vision the tools to make the thing they always imagined but couldn't build alone. the designer who had the idea but couldn't code. the kid who saw something nobody else saw. the person who cared too much about something most people wouldn't notice. if we get this right, we don't get a faster factory. we get a renaissance. more strange, personal, opinionated software made by teams of people who care and mean it. that's still possible. but only if the people who care get the space and tools to actually express themselves – and don't just hand the wheel to the agent and walk away.
142
342
114
2,476
428,527
The @ilyasut episode 0:00:00 – Explaining model jaggedness 0:09:39 - Emotions and value functions 0:18:49 – What are we scaling? 0:25:13 – Why humans generalize better than models 0:35:45 – Straight-shotting superintelligence 0:46:47 – SSI’s model will learn from deployment 0:55:07 – Alignment 1:18:13 – “We are squarely an age of research company” 1:29:23 – Self-play and multi-agent 1:32:42 – Research taste Look up Dwarkesh Podcast on YouTube, Apple Podcasts, or Spotify. Enjoy!
397
1,256
644
8,431
4,158,978
the kind of longtail tiredness that has taken on a repeated flair and feels like it’s never gonna leave has now become my obligatory staple. but even tweeting is breathing rn, & a smol attempt to break free. a win
2
1
402