Amerika’da 15 sene boyunca askeriyede şoförlük yapan ve emekli olduktan sonra olul otobüsü süren Marcus için sıradan bir gün başlamıştı.
Çocukları topladıktan sonra okul yoluna koyuldu. Ancak ön camı kırıp içeri gelen devasa bir taşla neye uğradığını şaşırdı.
Bilincini kaybetme ve başka cisimlerin camdan içeri girmesi ihtimaline karşı frene bastı.
Otobüste tek ciddi yara alan Marcus’un ta kendisiydi.
Ancak çocukların aileleri, hayatı pahasına çocukaları koruyan Marcus’a $500.000 dolar değerinde dava açtı.
Neyse ki Frank Caprio’yu aratmayan bir hakim, Marcus’un yaşanan kazada ölmek üzereyken bile çocukları sağ salim indirebilmek için çabaladığını, bu durumun ceza değil ödül alması gerektiğini söyledi.
Kaldı mı gerçekten böyle hakimler???
@creepydotorg My question is, what is he looking for? Didn't God create him a human? You're not a snake, what is he looking for in snake habitation?. God have mercy...
John Jones was stuck like this for 27 hours in Nutty Putty Cave, Utah, before he died.
In the final hours, rescuers considered pulling him out, knowing it could break his spine and legs. The risks were too high, and the team ultimately decided it would be more humane to let him die.
The rescue team stayed in contact with him until the very end; trapped upside down, he eventually went into cardiac arrest and died.
@javarevisited Is like a classic race condition or idempotency not check.
1. Frontend Double-Clicking.
2. Missing Idempotency Keys.
3. Aggressive Retries.
@IbBeatrice It's high time everyone sits in their house, you won't come to my house and disrespect my wife. Either mother, siblings or relatives, there should be a boundary and no one should cross it, regardless....
Because HashMap works on hashing 👀
On average, the key’s hash points directly to a bucket, so lookup is O(1).
But if many keys land in the same bucket (hash collision), it has to scan entries inside that bucket.
In the worst case, if everything collides into one bucket, it behaves like a list → O(n)
Future headache 👀
This works today, but it violates OCP (Open/Closed Principle).
Every new employee type means adding another if-else.
Tomorrow it becomes:
FULL_TIME → CONTRACTOR → INTERN → PART_TIME ...
Better design: use polymorphism / strategy pattern, where each employee type calculates its own salary.
Honestly, yes.
Legacy code at that scale teaches you more than greenfield projects ever can.
You learn how real systems survive traffic, bad decisions, migrations, and years of business changes.
Anyone can build from scratch.
Maintaining 2008 code in production is where engineering maturity shows 🚀
@starbuxman Haven't seen the video yet but your post here already scared me from seeing it lol 🤣, during my college we had to write it by hand in exam all, sweating under AC 🥲
lol bro setup a YouTube channel and put out exactly one, epic 2h+ long video title “the worst programming language of all time,” and it’s a screed about every terrible inconsistency in C++
youtu.be/7fGB-hjc2Gc?is…
Imagine a teammate submits this code. It takes a list of high-priced transactions and tries to create a formatted "Report Summary" string of their IDs. What is the problem here?.
A good developer writes code that a computer can understand, but a great developer writes code that manages resources efficiently so the system stays healthy under pressure.