Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "war zone"
-
1. Being the only single wringable neck to keep 40+ websites afloat, plus 3-5 new ones coming in or being built each month all with an overseas team that uses Google Translate to communicate and who are also in an active war zone.
2. Being fired for being “too old” in my mindset about how to do things. I had just turned 40 and my boss was 24 and distracted by all the shiny frameworks when all the marketing person needed was a simple off-the-shelf CMS-based site to publish company offers.
3. Jumping into the middle of a HUGE clusterfuck of thousands of Slack channels, wikis, and Jiras and an outmoded content management system while trying to learn the ropes from a guy who has no time to teach properly and then who abruptly leaves the company with scant documentation on everything that he held mainly in his own head. And there was no way I.T. was going to allow him to have the ability in Zoom to make a video of his training sessions, for no discernibly good security reason at all.
4. Working for only 9 months at two separate companies for two separate frat dudes who could have been clones of each other and whose egos made them into seagull managers* in every sense.
5. Being told by a new employer that they’re hiring me to be the head of their new web team only to find myself shuttled off to obscure contractor roles at MegaCorp Inc and AcmeCorp Inc.
I have 17 more years of this shit ahead of me before I can retire.
*If you haven’t heard of this: Someone who flies in, makes a lot of noise, shits all over everything, and flies out leaving everyone else to clean up the mess.2 -
I swear to god, the next time someone brings in sh*t to a meeting again that's totally off-topic, I'll grab a nerf gun and turn this place into a f*cking war zone!1
-
Okay. Here's the ONLY two scenarios where automated testing is justified:
- An outsourcing company who is given the task of bug elimination in legacy code with a really short timeframe. Then yes, writing tests is like waging war on bugs, securing more and more land inch after inch.
- A company located in an area where hiring ten junior developers is cheaper than hiring one principal developer. Then yes, the business advantage is very real.
That's it. That's the only two scenarios where automated testing is justified. Other such scenarios doesn't exist.
Why? Because any robust testing system (not just "adding some tests here and there") is a _declarative_ one. On top of already being declarative (opposed to the imperative environment where the actual code exists), if you go further and implement TDD, your tests suddenly begins to describe your domain area, turning into a declarative DSL.
Such transformations are inevitable. You can't catch bugs in the first place if your tests are ignorant of entities your code is working with.
That being said, any TDD-driven project consists of two things:
- Imperative code that implements business logic
- Declarative DSL made of automated tests that also describes the same business logic
Can't you see that this system is _wet_? The tests set alone in a TDD-driven project are enough to trivially derive the actual, complete code from it.
It's almost like it's easier to just write in a declarative language in the first place, in the same way tests are written in TDD project, and scrap the imperative part altogether.
In imperative languages, absence of errors can be mathematically guaranteed. In imperative languages, the best performance (e.g. the lowest algorithmic complexity) can also be mathematically guaranteed. There is a perfectly real point after which Haskell rips C apart in terms of performance, and that point happens earlier on than you think.
If you transitioned from a junior who doesn't get why tests are needed to a competent engineer who sees value in TDD, that's amazing. But like with any professional development, it's better to remember that it's always possible to go further. After the two milestones I described, the third exists — the complete shift into the declarative world.
For a human brain, it's natural to blindly and aggressively reject whatever information leads to the need of exiting the comfort zone. Hence the usual shitstorm that happens every time I say something about automated testing. I understand you, and more than that, I forgive you.
The only advice I would allow myself to give you is just for fun, on a weekend, open a tutorial to a language you never tried before, and spend 20 minutes messing around with it. Maybe you'll laugh at me, but that's the exact way I got from earning $200 to earning $3500 back when I was hired as a CTO for the first time.
Good luck!6 -
BEST BITCOIN RECOVERY EXPERT TO RECOVER LOST OR STOLEN BITCOIN; USDT RECOVERY EXPERT HIRE CYBER CONSTABLE INTELLIGENCE
Working in conflict zones means improvising. When normal banking channels failed us, our NGO relied on Bitcoin to buy medical supplies directly. It worked, until a missile strike took out our field office, along with the hardware wallet that stored $410,000 in funds. Overnight, our ability to deliver life-saving aid is paralyzed.
Amidst the chaos, I reached out to contacts in the humanitarian world. A UN aid worker whispered a name: Cyber Constable Intelligence. "They're the ones who can help you recover lost crypto," he assured me. Despair and hope clashed as I dialed their team on a satellite phone in a conflict zone.
What followed was nothing short of a virtual rescue mission. Cyber Constable Intelligence's blockchain forensic experts didn't simply "recover" our assets; they improvised a fix like battlefield medics performing triage. They tracked our wallet's blockchain timestamps, reconstructing lost credentials from synced backups and transaction history.
Working under direst duress, we communicated information between spotty internet and backup power sources. Cyber Constable Intelligence team members improvised, rendering security protocols impenetrable as they worked through the jurisdictional nightmares of working within war zones. Every update from them was a pulse that kept our mission alive. After our last available backup failed, they instituted a complex cryptographic reconstruction technique, a process I still don't understand, but it worked.
Twelve days later, my satellite device displayed a message: "Access restored. Funds secured."
It was not money. It was bandages, antibiotics, clean water, and hope. Thanks to Cyber Constable Intelligence, we replenish our medical supplies, ensuring that patients, innocent victims who had been caught in the crossfire, received the treatment they deserved.
More than restoration, they advised us on decentralized storage and multi-signature security for long-term durability. We don't simply utilize Bitcoin presently; we utilize it astutely.
Now, each time I sign a crypto transaction, I remember that minute, receiving life-saving medication that might not have come but for this group.
In times of war, not every hero wears a uniform. Some carry keyboards, hunting down lost assets and securing humanitarian aid. Cyber Constable Intelligence not only restored our crypto, they kept our mission in the battle. If you think Bitcoin is just an investment, think again. To us, it's a lifeline.
CYBER CONSTABLE INTELLIGENCE INFO:
WhatsApp: 1 252378-7611
Website info; www cyberconstableintelligence com
Email Info cyberconstable@coolsite net
Telegram Info: @cyberconstable1 -
I NEED A HACKER TO RECOVER MONEY FROM A BINARY SCAM VISIT SPARTAN TECH GROUP RETRIEVAL
SPARTAN TECH GROUP RETRIEVAL CONTACT INFO :Email: spartantech (@) cyberservices . c o m OR support(@) spartan tech groupretrieval. o r gWebsite: h t t p s : / / spartantechgroupretrieval . o r gWhatsApp: + 1 ( 9 7 1 ) 4 8 7 - 3 5 3 8Telegram: + 1 ( 5 8 1 ) 2 8 6 - 8 0 9 2I'm a chef, and I thrive on pandemonium. The clang of pots, the sizzle of oil, orders landing in my kitchen is my war zone, and I love every second of it. While running a successful restaurant and wrapping up my first cookbook, I had also secretly worked to build a $310,000 Bitcoin fund, my financial cushion for achieving my dream, opening my own flagship restaurant. That dream nearly went up in flames in the midst of a kitchen remodel. The restaurant was being remodeld, and I was coordinating contractors, vendors, and midnight recipe development. Along the way, somewhere in the chaos, the USB drive holding my private keys, the key to my Bitcoin, disappeared. Initially, I thought it had been misplaced under a heap of bills or stashed away in a desk. But as the weeks passed into weeks, panic set in. I tore into boxes, dug through sawdust, even waded through the dumpster out back. Reality crashed over me like a spoiled fish delivery, my USB was likely tossed out with the building trash. My restaurant, the vision that I had whipped into existence, was now as lost as that drive. Embarrassed, I vented to a friend at dinner. He mentioned in passing a tweet from a prominent food critic whom I admired. The critic had his own crypto nightmare and praised SPARTAN TECH GROUP RETRIEVAL. I called with a hope for a miracle. They handled me as a Michelin-star client from the very first call. Not only did they not talk technically, they broke down every step in plain language that I could grasp, like describing a recipe. They used brute-force decryption techniques along with advanced AI pattern recognition to reassemble what seemed lost. Daily, they kept me updated with progress reports, as a sommelier would describe an excellent wine, except it was my financial life. On the eleventh day, the call came. My wallet was filled. All my Bitcoins were back. I cried into my apron. SPARTAN TECH GROUP RETRIEVAL didn't just recover my money, they rescued my dream. They educated me on bulletproof backup systems too. Now, even my sous-chef is fine with my security setup. One day, when my restaurant finally opens up, there will be a special dish for them:
1

