The Pain Of Frontend Dev | Prime Reacts

I'm mainly a backend C# and SQL developer but can do frontend as well. One mid size company I worked with sales to put a "Tax Exempt" checkbox on a page. This was later in the day. Next morning she asked if the checkbox was done!!!! I said no... she said it's just a checkbox! I asked if she just wanted the checkbox there or does she want it to work also. So had to change 50+ C# files in backend code,, some reports, and some stored procedures to get it to work. Guess she thought putting the checkbox on there that the application would know what to do with it? LOL

lol that button thing hit home. Client wants a "print" button put on a data table and added to the context menu. Ok so just print the page? No, a custom-tailored report with specific formatting and watermarks. The data they want exists across 18 tables and in 1-1, 1-many, and many-many related relationships. The data fields they want keep evolving, as well as the formatting each time they see the prototype report, as well as the report will display different data fields and be in different orders depending on certain conditions of said data. Is it a Template A? Does it contain X number of software items? Is it Tuesday!?!? 2 months later...."Why is it taking so long, IT'S JUST A PRINT BUTTON!!

"It's just a button, why is it taking so long?" is a sentence capable of instantly curing low blood-pressure conditions. Only downside is the instant depression.

The startup I worked at: "WE WANT QUALITY! MAKE QUALITY STUFF!" (They didn't tell us that he wanted a pretty rapid prototype, so I wrote software to be decently stable, and the CEO hated that). Surprisingly, the "Jira ticket for that" event almost happened when some guy in the building went to a local grocery store to buy a bunch of grapes for a snack. Middle manager was flipping the you-know-what out. "Bruh. He's gone for maybe 15-20 mins. If that's enough to derail the project, this company is screwed".

"You just want to add a button but Bill is on vacation" is the realest thing I've ever heard. That has been my entire experience in software, just constantly waiting for [person] to get back from PTO or vacation so that you can do the one thing that's preventing you from doing everything else you need to do.

4 minutes made into 20. Good job!

I cried this week. Something that has been working for years was breaking in very annoying ways that could not be replicated in debug mode and the failures were the exact failures I was trying to avoid in my design. Then, I took a moment to refactor a stupidly written class (I don’t know what the was I thinking. Then again, I’m support, IT, sys engineer, project management, devops, tech lead, and lead software engineer so maybe I forgot a hat when I wrote it). The class affected my task scheduler which indirectly affected the lifetime of triggered tasks which affected whether some state was committed to disk as expected. Since I had to keep prod flowing while figuring out wth was happening, I cried every day… Software dev is truly an exercise in not crying.

The “button diagram” was exactly how my instructor explained docker to me

One time I was assigned to change a button to a drop-down with a few options. It only took 2 weeks and 13 file changes to make it happen.

Man that explanation at the beginning. That went from nirvana to my current work really fast

This happens with any project. The bigger the product, the bigger the binary decision tree and the longer it takes to add even the simplest of features. Eventually, it's cheaper to make a new project than it would take to fix all the bugs in the old project.

That "net is built with old tech" part hits hard. I recently had to review a 10 years old app that somehow got a new version, but security team did not want to approve it. I checked the code: Webpack 1.0, libraries so old you can't upgrade them without upgrading / replacing dozens more, tons of libraries on top of tons of other libraries including an internal library for components that was acquired from one of the child companies and was no longer maintained. And the problem? Dep of a dep of a dep 5+ levels deep should be upgraded because string method X is bad or some minuscule shit like that. Which would require upgrading the main dep, which would require other deps changes, yadda yadda. After a day of trying to not colapse the Jenga tower I was told to write down why this can't be done, security team approved another of very many exceptions, and I went back to my oryginal project.

I felt the MTB rant. Currently am in the middle of the same thing happening in our project. It started as a simple enough web application, a .NET GUI and an Oracle DB, the DB had what passed as the application layer in PL/SQL. One webservice of some large data inputs we got once a week, that the customers then could work with on the GUI, and a DB Link for a project that ours spawned off from. Then came middle management and wanted scalability.. for an app that has maybe 50 users, country wide, max. So now we have an API between GUI and DB, and spend half a year ripping the app layer from the DB, so it can run on multiple servers, if needed (Not needed yet and probably never will be). We since added a ticket system that needs to communicate to the sister project, so got 2 APIs for that too, one for our end, and one for their end. We also needed a job service to fetch data from a third party data source, actually make that two for another one, because microservices, amiright fellas? I have 6 different .NET solutions in 3 different versions ranging from Framework 4.8 to .NET 8. Sometimes I wonder where it all went wrong.

I'm in shambles after watching this. You took all hope out of my life.

4:40 as a famous developer once said: "You silly product manager! You know nothing about GALACTUS's pain, my pain. Delivering this feature goes against everything I know to be right and true, and I will sooner lay you into this barren Earth than entertain your folly for a moment longer."

17:53 The End of the World by AlbinoBlackSheep mentioned! I thought I was the only one to still remember that video, absolutely was dying that you quoted it, such classic YouTube!

4:45 this whole oddly specific rant about Bill and the co-founder's daughter not being able to post cat pictures and three weeks waiting to add a button... I think @ThePrimeTime actually experienced this, and is still recovering. Why is Bill like this?

19:39 Trailing slash is usually meant to distinguish between directory location and file location. For HTML pages it should be with slash because it is actually loading /index.html. But since it looks ugly this semantic standard is rarely respected.

Bro, you're such a vibe, I appreciate you

As my company's Bill, I only hear tiny violins