Software Engineer | creator @sendbyte_, @afripadhq
Federal Capital Territory, Nig
Joined April 2018
- Tweets25.3K
- Following4.5K
- Followers5.3K
- Likes32.4K
Victor retweeted
In meetings, I keep saying “just because we can doesn’t mean we should”
Like sir I can get you that full feature in two days but you will KNOW I worked on it for two days when you use it
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😪
Victor retweeted
real talk
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😪
Victor retweeted
I can't exactly relate to this yet but I had a somewhat similar experience regarding my final year project.
everyone expects you to deliver as soon as possible with little consideration to how much time and effort is required to actually understand what is being produced.
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😪
Victor retweeted
There is nothing to worry about.
Nothing important is run on PHP or old software—except the water & electrical grid, a few government services like our missile defense systems and a handful of electrified fences at the zoo (for the lions, tigers and cobras).
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😪
Victor retweeted
Dealing with nepo babies as someone who came from poverty is weird
My cousin who’s dad is very rich has traveled outside the country three times this year for vacation not African country o Asin London , Netherlands , Italy .. I’m always begging her to post it , she doesn’t post 😭
last week she relocated fully to Canada I told her to use that trending TikTok sound Nigerians normally use when they’re relocating to do her own vlog and post , she said there’s no need for that 😭 I’m pained because I want to post her but she’s spoiling my plans 😭 she only post bible verse every morning 😭😭😭
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😪
Victor retweeted
This is how I earn $20k/month as a software engineer living in Nigeria.
Victor retweeted
They “Engineering Team” is me😭
I have multiple enterprise systems running on both legacy PHP and laravel.
I have infrastructure running on railways,
I have applications running on Node.
Bruh I don almost mad this morning😭
