The mistake many people make is that they think that enduring a toxic work environment and going to a new job makes them forget their horrible experience.
I know people who still relive experiences from toxic work environments years after leaving.
See, if a job is extremely toxic, leaving is an investment regardless of whether you have something lined up. You'll deal with the after effects many years later and will always wish you had left earlier.
@akinkunmi My main issue with Prisma was the Prisma Query Language, although they later introduced typed SQL, but I was long gone with Drizzle, and never looked back.
@darasoba Terrorism and Kidnappings all have a chain of command, those you see in this video barely get a share of that money, that money belongs to their "Oga at the top", They often break out, which is why there are so many factions.
Money can attract talent, but it doesn’t always keep it.
People stay where they feel valued, supported, challenged, and respected. A great salary may open the door, but a great work environment is often what keeps people from walking out of it.
Any company can poach talent.
The real challenge isn’t attracting great people; it’s creating a workplace so healthy, fulfilling, and well-run that they choose not to leave.
Yes. That is exactly why we exist.
If you believe Nigeria needs fearless journalism that isn't controlled by politicians or oligarchs, help more people find gst. Share our work. Tell your friends about us.
The elections are coming. We'll be here.
@Mochievous It all started with Buhari, when he outrightly prevented the media from covering the Boko Haram activities so people would assume Boko Haram had stopped and that the country was "safe".
@jayhemz@saen_dev Indeed, most companies are now struggling with unstructured and bloated codebases.
Debugging is now twice as hard because no one has a mental map of what it looks like.
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.
As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!
I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.
It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?
88ms => 1.5ms
150K allocs => ~500 allocs
Incredible right? Nope.
My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.
This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.
The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.
Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
This is something I see all across Africa all the time. A combination of scarcity mentality and short sighted competition makes people shoot themselves in the foot long term.
Many times it's not as obvious as in this case but it happens all the time.
God help us.