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 - "wk245"
-
So, you start with a PHP website.
Nah, no hating on PHP here, this is not about language design or performance or strict type systems...
This is about architecture.
No backend web framework, just "plain PHP".
Well, I can deal with that. As long as there is some consistency, I wouldn't even mind maintaining a PHP4 site with Y2K-era HTML4 and zero Javascript.
That sounds like fucking paradise to me right now. 😍
But no, of course it was updated to PHP7, using Laravel, and a main.js file was created. GREAT.... right? Yes. Sure. Totally cool. Gotta stay with the times. But there's still remnants of that ancient framework-less website underneath. So we enter an era of Laravel + Blade templates, with a little sprinkle of raw imported PHP files here and there.
Fine. Ancient PHP + Laravel + Blade + main.js + bootstrap.css. Whatever. I can still handle this. 🤨
But then the Frontend hipsters swoosh back their shawls, sip from their caramel lattes, and start whining: "We want React! We want SPA! No more BootstrapCSS, we're going to launch our own suite of SASS styles! IT'S BETTER".
OK, so we create REST endpoints, and the little monkeys who spend their time animating spinners to cover up all the XHR fuckups are satisfied. But they only care about the top most visited pages, so we ALSO need to keep our Blade templated HTML. We now have about 200 SPA/REST routes, and about 350 classic PHP/Blade pages.
So we enter the Era of Ancient PHP + Laravel + Blade + main.js + bootstrap.css + hipster.sass + REST + React + SPA 😑
Now the Backend grizzlies wake from their hibernation, growling: We have nearly 25 million lines of PHP! Monoliths are evil! Did you know Netflix uses microservices? If we break everything into tiny chunks of code, all our problems will be solved! Let's use DDD! Let's use messaging pipelines! Let's use caching! Let's use big data! Let's use search indexes!... Good right? Sure. Whatever.
OK, so we enter the Era of Ancient PHP + Laravel + Blade + main.js + bootstrap.css + hipster.sass + REST + React + SPA + Redis + RabbitMQ + Cassandra + Elastic 😫
Our monolith starts pooping out little microservices. Some polished pieces turn into pretty little gems... but the obese monolith keeps swelling as well, while simultaneously pooping out more and more little ugly turds at an ever faster rate.
Management rushes in: "Forget about frontend and microservices! We need a desktop app! We need mobile apps! I read in a magazine that the era of the web is over!"
OK, so we enter the Era of Ancient PHP + Laravel + Blade + main.js + bootstrap.css + hipster.sass + REST + GraphQL + React + SPA + Redis + RabbitMQ + Google pub/sub + Neo4J + Cassandra + Elastic + UWP + Android + iOS 😠
"Do you have a monolith or microservices" -- "Yes"
"Which database do you use" -- "Yes"
"Which API standard do you follow" -- "Yes"
"Do you use a CI/building service?" -- "Yes, 3"
"Which Laravel version do you use?" -- "Nine" -- "What, Laravel 9, that isn't even out yet?" -- "No, nine different versions, depends on the services"
"Besides PHP, do you use any Python, Ruby, NodeJS, C#, Golang, or Java?" -- "Not OR, AND. So that's a yes. And bash. Oh and Perl. Oh... and a bit of LUA I think?"
2% of pages are still served by raw, framework-less PHP.32 -
I die, go to hell and my punishment is to write software for hell network that is having power problems due to light source disruptions and is running on Windows 95 on FAT32 without any service pack.
Network speed is trough 300bps dial up modem. Protocol is over IPX/SPX.
My task is to write interactive websites that are replacement of modern websites but in VBScript, ActiveX, IE 4.0.
I have 10 managers that tell me what to do and scream when I miss deadline that is set everyday without my knowledge at random times.
They send me an email and 5 minutes later they arrive at my desk to ask me about it.
I must work 16 hours a day before I can leave the place and if I won’t show up police beats me and escorts me to the office.
If I’m late a second I don’t get payment.
I can’t afford to rent a place so I sleep in the sleeping bag.
It doesn’t matter much cause as soon as I fall asleep phone rings until I wake up and my manager screams about the problems he have for about an hour.6 -
Being responsible for a massive breach of personal & financial data.
Seriously, that crap scares me way more than any amount of downtime does.1 -
Outsourcing front-end for web is like playing russian roulette, but with 6 bullets in 6 chambers.
You shoot yourself in the balls (or ovaries)... HARD.
I don't know how you can develop in a complete nightmare of a SCSS file - 3500 lines of insanity.
This dev must have changed his mousewheel at least 50 times!
SERIOUSLY, why the fuck use SCSS when you piss everything into one single fucking file???
What drives me completely nuts is the fact that he even used an @import to include his custom.scss file... how many more IQ poins are needed to realize that you could SPLIT your spaghetti into smaller, sane files?
I need a whiskey...3 -
Developers too lazy to google search/read the README.md yet too proud to admit their mistakes.
They create disasters that I need to clean up later because they took a vacation.12 -
Accidentally copying my sex tape into an npm repository without realizing, publishing it, and having it be downloaded billions of times before I could unpublish it.8
-
Worst dev disaster
I was responsible for allowing users to purchase a six month premium plan in our app for free.
Only way we got to know about this was that a customer himself emailed us saying we are allowing users to get premium access for free.
Thankfully he emailed us within a day of the release and we didn't incur massive losses.5 -
It began when I was tasked with creating a better and more engaging experience for our new Facebook page. This was in Facebook's early days, so there were not really any "best practices". We were making it up as we went along. I decided one way would be to game-ify things, since gaming, at the time, was a Big Deal on Facebook and people were starting to use it to build customer funnels.
Grasping for low-hanging fruit, I decided a Tetris variant around our topic would be fun. I had to hire a dev because at the time I was a static HTML web developer just getting into social media management. I knew nothing about game development or how to use Facebook's API for such things.
Long story short, we got about $10,000 (FB app devs came at a premium then) into the project when I came across a very recent article about the history of Tetris games. It said that even though Tetris had once been considered for all intents to be public domain due to it being created by a Russian coder during the Cold War, it had just been acquired by an IP protection entity that was charging royalties for any variant of Tetris created from a specific date onward and paying the original developer. So, even though I thought I had been thorough in my initial permissions checking, it turned out we were gonna be in deep doo-doo with licensing fees and restrictions if we released this game to the public.
I had to call my boss and admit my error. She was FURIOUS and really gave me an ass-chewing over it. I then had to call the marketing person whose budget I'd been slaving away at wasting. She was a bit more forgiving (her budget was in the millions). Then I had to call the corporate legal department and explain what was going on. They told me to immediately pay any outstanding hours, then fire the dev but not before getting him to send me all code and assets, deleting his copy, and then, upon my receipt of those assets, deleting MY copy so that nothing of it ever existed. And I was supposed to say _nothing_ to the dev about why he was being let go, so that there would be no "trail" leading back to this fiasco. (The dev hounded me for weeks asking what he'd done wrong. It killed me that I was bound and gagged by corporate legal and couldn't tell him.)
I was in so much trouble. I was literally in tears over it. I'd never wasted that much money in my life. That incident pretty much sealed my fate as far as any trust my bosses ever put in me again (not much at all). I was a bit of a pariah in a lot of ways for the next 5 years whereas I had come onto the team as a young social media rockstar at first.
After that, and a couple of other bad scenarios that were less my fault and more due to a completely dysfunctional management and reporting structure, they eventually "transferred" me to another team. Which was really just a way of getting rid of me by sending me to a department that was already starting to outsource overseas and lay people off. It was less messy that way. I was in the first set of layoffs.
Since then, I've had a BIG fear of EVER joining a large corporation EVER again. I prefer to work for small businesses now, even if I get paid less. Much less stressful from an office politics and impact of mistakes standpoint.3 -
We all get replaced by AI and nobody can understand their source code...
And everyone else just goes: hey it works ¯\_(ツ)_/¯12 -
An enormous government project that leaves the tax office's database along with all backups exposed to SQL injection.
I know for a fact that the tax office database in at least one country only got a cold backup a few years ago, so it's more likely than you think.
Although around that time someone hacked the public transport company and bought a 12 month ticket for free as PoC and he got jail for it so the risk is quite high.5 -
1) API Server crash due to Uncaught Error and none of us realised it until 30 mins later (no email alerts, no mechanism in place to notify devs): expensive mistake
2) api server and database server on one frickin vps, with no caching mechanisms or memoisation on frontend: Worst nightmare of my life5 -
- my (non-dev) supervisor at my job
- no documentation
- no source control
- people working in the same team with completely different programming/domain knowledge levels, but also very different ways of being
- bad within-project communication
Luckily not all of them are about my job. We do use source control.8 -
Hmm I have created marketing application. and when it goes live the client comes with approxx.. 10M mails to be sent at once :( Everything worked smoother But client does not have patience to wait.. So he went to the boss.. boss told us heyy you process email one by one .. instead create batch of emails and then sent.. my whole application flow has been changed.,.....
Its like am on 0 to start again
crying in corner ... :(10 -
Learning Python as a first language. Or Pascal. It's a tie between mainstream informal and obsolete formal education.17
-
Worst dev disaster?
Welp, my now 6 year old Mac keeps sending signal to my monitors that in my experience regardless of OS generally says "my video card is gonna fuckin die soon".
I've re-installed the Windows partition like 3 times, but that responds to the video card problems so bad it pretty much just BSODs... but the Mac side soldiers on, just occasionally having weird visual glitches. Thats fine, I work on the Mac side.
And I don't really want to spend a shit ton on a new computer... but I do want a Mac, so I'm gonna spend a shit ton.
So now I have to decide if I can hold out for an M1 or if I should just shell like thousands for a Mac that will be out of date in like 4 months. After which for development purposes I'd still have to buy at least the M1 dev kit Mac Mini.
All of which hinges on this effing video card lasting another few months.
Because if it doesn't I'm going to have to use my kids 8GB fuckin HP laptop as my main dev machine while I get another Mac in the mail and that would fucking suck not to mention the like minimum two days sleep I'd lose just setting up the required local environments I'd need... not to mention I'd have to do all that in Windows... so I'd have to find Windows equivalents for all my dev tools. Or fuck it, maybe I could just install Putty and server cowboy everything... but it would still suck.
And, of course, I don't have time to do any of that because I have the normal like 2 tight deadlines on shit.
The next few months of my life, potentially my ability to earn a living, potentially my sanity...
Hangs on the health of a fucking six year old heavily abused video card.9 -
Work from home, jerking off, ranting co-workers/bosses during an online meeting forgetting to turn off my cam and mic3
-
The fact my university still teaches ada as a coding language in a required class. That's a real disaster. Also had to use racket in another course. Nothing uses racket.7