Software Engineer | creator @sendbyte_, @afripadhq
Federal Capital Territory, Nig
Joined April 2018
- Tweets25.3K
- Following4.5K
- Followers5.3K
- Likes32.5K
Victor retweeted
Absolutely agree with 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😪
Victor retweeted
This same thing I was discussing earlier this week, we have turned Software engineering into what it wasn’t before all “cos there is 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😪
Victor retweeted
There used to be brainstorming sessions where engineers could talk about engineering and learn a thing or two from one another.
All of a sudden, no one seems to care about that anymore. Even those who still care seem to care a little less compared to way back
And I think AI has something to do with that too Cause everyone is now thinking it’s a waste of time. Omo mhenn
Anyhow e be sha, Adapt !!! 😅
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
Terrible culture this. Companies’ excos are so AI pilled, they don’t even want to hear you refute their unimaginable requests.
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
It’s the price we pay for the exponential level of productivity AI has enabled. The augmented level becomes the new standard the management expects but guess what? The salary stays the same lol
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 why I say that the AI overlords who swear it'll bring freedom are lying to ppl and you're absolutely dumb to believe it. We only have decades upon decades of technological progress as evidence. You will be expected to be more productive for the same pay.
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
The more things change, the more they stay the same.
These people need to be spoken to in their language.
Yes, turn around is better. Response time is better.
However, every business decision is an exercise in risk management. When some risks decrease, that should not overshadow risks that remain.
We can do things faster. That means we can do stupid things faster as well.
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
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😪
