Software Engineer | creator @sendbyte_, @afripadhq

Federal Capital Territory, Nig
Joined April 2018
I'm building 20 products with AI before 2027. Every line of code written with Claude. Every mistake will be documented publicly. Starting now!
26
14
9
228
36,088
Victor retweeted
Reading this is funny because I just shipped a personal app I've been working on... Even my prompts averages around 20mins and 1 prompt doesn't mean one feature... Let's not even talk about debugging or architecture
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
2
1
1
62
I can forgive this guy, but you see Evaristus, i no fit ever forget that guy name for my life, Evaristus traumatize all the Lions wey dey there😂😂
You just have to be there 😂
6
1
1
14
575
Grok omo werey😂😂😂 xitter.cf/grok/status/2114096080…
Replying to @echo_vick
Abeg I find am. Na this Evaristus pitch for Ultima Lions Den where e dey ask for 100 million naira for 10% equity. The guy really traumatize the Lions with that energy 😂 xitter.cf/UltimaLionsDen/status/…
16
@grok i posted evaristus video on lions den, abeg help me find am
1
33
I'm considering bringing this back😂
Friday deployment shenanigans at the office…😂 Feedback is welcomed Skit Inspo - Beluga
1
1
15
551
Victor retweeted
Replying to @echo_vick
Sadly, this happens almost everywhere now… And it’s getting scarier day by day, buh I know one thing for sure, everyone will learn the hard way sooner or later
1
1
2
58
Victor retweeted
Even if I get it done within 48 hours, I won't ship it; I don't ship what I'm not satisfied or confident with.
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
1
1
2
40
Victor retweeted
the pressure I get sometimes can be so overwhelming and draining , I forget to eat or take care of myself because everybody expects you to be fast because of AI and I think the fear of losing a job plays its role in all this.
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
2
6
376
Victor retweeted
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
I want to talk about something that’s really been stressing me out and draining me mentally.
64
172
52
709
33,170
This topic triggers me so much Every non-technical person thinks just cuz Claude can write the code means it can automatically build everything in a goal Reducing deadlines and all Had a client come to me one to build a really sophisticated social app in less than 3 weeks cuz he wanted the app to be “out there” as soon as possible Told him it wasn’t possible cuz there are a lot of thinks to be considered The logic and algorithms behind how the feed will come to users is a nightmare alone for a mere 2 weeks He just said “can’t we get AI to do that” and that was where I ended the conversation It’s not me you’ll come and kill Deadlines now have been reduced drastically cuz of this shit and it’s annoying Expecting the impossible cuz “we have Claude”
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
1
1
3
109
Victor retweeted
With time there will be more regulations. At work we were asked to be cautious with AI use so we avoid revealing sensitive data, but It’s still a very fine line to walk though. Management needs you to ship fast, and it feels like there’s no time to cross over the learning curve because competitors are moving faster.
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
1
1
2
123
Victor retweeted
In here lies the true usefulness of a developer . once I'm getting this feedback I know it's a matter of ignorance . Keep singing out about how important architecture and structure is -sooner or later they'll find out .
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
1
1
1
17
Want to learn about what’s going on in African tech? I recommend following this page.
Richard Oyome helped Raenest process $3 billion in transactions. Now, the fintech co-founder wants to do more than move money. He’s building Raenest into a platform where Africans can receive, save, spend, and grow their money across borders. Read the full story: startupin60.com/p/f353df57-f…
7
43
963
87,875
For the long tail of businesses that will emerge in this new era of the internet We’re building for them The Fortune 500,000,000
3
6
65
1,313
Victor retweeted
Medical doctor trained in Ukraine wants to start Computer science in Unilag in the midst of AI making vibecoding the world's biggest software product's possible, practically making junior programming & product design pointless... Make it make sense
I decided to get excited again and I Started computer science in Unilag. In 4hours is my first exam in my 100Lvl …. Wish me luck 😩
1
3
2
1
6,194
Victor retweeted
This bachs webhook documentation 💐❤️
3
1
1
36
2,827
A very good read!
I spent 48 hours in SF hanging out with billionaires, data labs and AI founders and execs running $1B to $100B companies. My observations: 1. Sooo MANY stories of data brokers making like $2M a WEEK selling company data to labs. I can't tell if it's the beginning or a bubble, and I kept wondering which niches are left. Digging into it actively. 2. At dinner, someone asked the table, "If a new model drops next month, does your company get better or worse?" HALF the table went quiet! I think that's the best question to ask about any AI startup right now. 3. The bar people talk about now is hitting $1B in revenue in 12 months (I guess that's the new unicorn?). What I didn't hear much about is retention. AI revenue can come in fast and leave fast, and I think we're going to see a lot of stories of AI companies with huge revenue and terrible retention. 4. It's pretty clear we're living through the reinvention of the computer. The model is the CPU, the harness is the operating system, and skills and plugins are the apps. Thinking about it that way makes it easier to see where the whitespace is. 5. We're maybe 12 months from an agent that can watch you work for a week and then do your job without any instructions. The screen recording plus agent memory plus local model combination makes this possible right now. 6. Agent harnesses feel like the new GPT wrappers, in a good way, especially vertical ones. The best teams I talked to treat the model as swappable. One founder walked me through routing different models to different jobs: one for taste and visuals, a cheaper one for the everyday stuff, another for text. They use prompts they can move across models over fine-tuning, and A/B test the output on what users actually do with it: do they edit it, export it, share it? A vertical harness is basically four things: the connectors for that industry's data, evals written by people who know the work, rules for what the agent can and can't touch, and a clean screen for a human to review. The model is maybe 20% of it. 7. There's a lot of reverse engineering going on/cloning going on more than I've ever seen. People are decompiling software and rebuilding it with agents, and someone showed a suite of like 10 apps that are worth $5B+ each all that he cloned open source. Me and everyone are still thinking through what it means when software gets this easy to copy. 8. My guess is the value moves to data. If the software can be rebuilt quickly, what's worth paying for in a legacy SaaS company is the years of customer data and workflows inside it. Some SaaS companies are secretly data companies. Gets me thinking about how do you truly value data for this saas companies? Like if we were buying these dying saas companies at 2x ARR before (as example), maybe there is a better metric. Idk, just thinking out loud here. 9. It feels like a good chunk of legacy software won't make it to the agentic era, especially anything built around people clicking through a lot of screens. 10. Every company I talked to wants to pipe its internal data into one place and expose it to agents through MCP. Then they look at the data and realize it's a mess: five versions of the same customer, old Slack channels, PDFs nobody can search. Cleaning that up feels like a big consulting opportunity! 11. A lot of founders are building the basic building blocks for agents: APIs, data layers and tools. Some of the companies I saw barely have a UI because the main user is an agent. I really believe the startups that build primitives to this agentic era will do extremely well. Building blocks is the best way to think about it. 12. Labs can get plenty of training data, but it's harder to get real examples of agents failing inside companies. Whoever has those logs has something valuable. 13. Someone running a big consumer company told me the next fight is over memory. The model that remembers the most about you wins, and the smartest model matters less than people think. 14. Physical AI came up a lot. Astra I think was the first model that got people into AI can actually do CAD, and I think a lot of people are thinking what does vibe manufacturing really look like. The line I keep thinking about came from a robotics founder: the hardest problems in AI are deployment problems now, not research problems. Their robots work on their own, call a human when they get stuck, and every one of those calls becomes training data. 15. Cybersecurity companies are having a moment and are actually cool companies to build now, especially the ones that clean up after a breach. Every agent with access to your systems is a new door into your company, and a lot of those doors were left open. 16. Some startups are worth more dead than alive now. A shutdown company with 5 years of Slack, email and code can get paid for licensing all of it. I wouldn't be surprised if founders start factoring that into when they shut down. 17. People are starting to talk about monetizing the agent web. It feels really early, but when the most popular user of the internet is an agent, what startups should you be building? 18. I think agent insurance is coming. Once an agent makes an expensive mistake, insurers will want audits before they cover anyone. 19. Several people said the hire they want most is someone with taste who can write evals. The models are getting good at generating ideas, so the hard part is judging which ones are good. 20. New trend I observed: startup raises VC, uses venture dollars to become a creator, startup fails, founder falls back on being a full-time creator and incubates other products bootstrapped. 21. Getting SIGNIFICANT distribution is HARD right now. Founders are sponsoring buses, buying billboards like crazy and throwing parties with famous DJs to get noticed. Kinda feels dotcom era in that sense. Attention is what's scarce! The growth guy going viral sharing his UGC strategy from Wispr Flow is a good example. It's the sauce everyone wants, and I truly believe there are probably only 50 people on the planet who know how to scale these types of businesses efficiently in this era. Always good to get that dose of SF. I felt sooo lucky to have such an incredible trip during such an incredible time in building businesses. Surreal in so many ways. Happy to be home and locked in. Until next time!
2
14
597
We're going to see the contagious spread of workers forcing other workers to be meat proxies and then having them fired so they can keep their own jobs Basically Salem witch trials and McCarthyism but serving AI
Just a few years ago, management could comfortably wait out a two-week sprint to get a feature shipped. Today, there’s growing impatience when a feature takes more than 24 hours to deliver. 🥲 The pressure on software engineers right now is crazy, and I don’t think we’re talking about it enough. I can barely get two sentences into explaining my implementation plan before someone interrupts with: “Just give it to Claude to do!” “Sir, we need to think about…” “That’s what Claude is there for. Let it do the heavy lifting!” A task gets assigned, and barely 10 minutes later: “Why is it taking so long? Aren’t you using Claude properly? This should take a minute or two!” Somehow, the existence of AI has created this assumption that software engineering is now just a matter of writing a prompt and watching features magically appear. Nobody wants to hear about architecture, edge cases, testing, security, or the implications of a poorly thought-out implementation. Just ship it. And ship it NOW. AI has become both a blessing and a curse. Something I genuinely expected to reduce my workload has instead increased it. The productivity gains are real, but so are the expectations that come with them. We’ve made development faster, but somehow, we’ve also made every delivery feel slower. And that’s the irony nobody seems to be talking about. Omo mehn, I’m just exhausted, might as well just resign, but it seems it’s the same everywhere😪
1
1
5
216
Replying to @echo_vick
I think companies and users should ne educated on how AI works. AI speeds up work rate, which is absolutely true. But they forget that it's that point that the human work comes to play because you've got to look for possible flaws and correct them. We'll be fine at the end.
1
1
1
71