!rant

This was over a year ago now, but my first PR at my current job was +6,249/-1,545,334 loc. Here is how that happened... When I joined the company and saw the code I was supposed to work on I kind of freaked out. The project was set up in the most ass-backward way with some sort of bootstrap boilerplate sample app thing with its own build process inside a subfolder of the main angular project. The angular app used all the CSS, fonts, icons, etc. from the boilerplate app and referenced the assets directly. If you needed to make changes to the CSS, fonts, icons, etc you would need to cd into the boilerplate app directory, make the changes, run a Gulp build that compiled things there, then cd back to the main directory and run Grunt build (thats right, both grunt and gulp) that then built the angular app and referenced the compiled assets inside the boilerplate directory. One simple CSS change would take 2 minutes to test at minimum.

I told them I needed at least a week to overhaul the app before I felt like I could do any real work. Here were the horrors I found along the way.

- All compiled (unminified) assets (both CSS and JS) were committed to git, including vendor code such as jQuery and Bootstrap.
- All bower components were committed to git (ALL their source code, documentation, etc, not just the one dist/minified JS file we referenced).
- The Grunt build was set up by someone who had no idea what they were doing. Every SINGLE file or dependency that needed to be copied to the build folder was listed one by one in a HUGE config.json file instead of using pattern matching like `assets/images/*`.
- All the example code from the boilerplate and multiple jQuery spaghetti sample apps from the boilerplate were committed to git, as well as ALL the documentation too. There was literally a `git clone` of the boilerplate repo inside a folder in the app.
- There were two separate copies of Bootstrap 3 being compiled from source. One inside the boilerplate folder and one at the angular app level. They were both included on the page, so literally every single CSS rule was overridden by the second copy of bootstrap. Oh, and because bootstrap source was included and commited and built from source, the actual bootstrap source files had been edited by developers to change styles (instead of overriding them) so there was no replacing it with an OOTB minified version.
- It is an angular app but there were multiple jQuery libraries included and relied upon and used for actual in-app functionality behavior. And, beyond that, even though angular includes many native ways to do XHR requests (using $resource or $http), there were numerous places in the app where there were `XMLHttpRequest`s intermixed with angular code.
- There was no live reloading for local development, meaning if I wanted to make one CSS change I had to stop my server, run a build, start again (about 2 minutes total). They seemed to think this was fine.
- All this monstrosity was handled by a single massive Gruntfile that was over 2000loc. When all my hacking and slashing was done, I reduced this to ~140loc.
- There were developer's (I use that term loosely) *PERSONAL AWS ACCESS KEYS* hardcoded into the source code (remember, this is a web end app, so this was in every user's browser) in order to do file uploads. Of course when I checked in AWS, those keys had full admin access to absolutely everything in AWS.
- The entire unminified AWS Javascript SDK was included on the page and not used or referenced (~1.5mb)
- There was no error handling or reporting. An API error would just result in nothing happening on the front end, so the user would usually just click and click again, re-triggering the same error. There was also no error reporting software installed (NewRelic, Rollbar, etc) so we had no idea when our users encountered errors on the front end. The previous developers would literally guide users who were experiencing issues through opening their console in dev tools and have them screenshot the error and send it to them.
- I could go on and on...

This is why you hire a real front-end engineer to build your web app instead of the cheapest contractors you can find from Ukraine.

One comment from @Fast-Nop made me remember something I had promised myself not to. Specifically the USB thing.
So there I was, Lieutenant Jr at a warship (not the one my previous rants refer to), my main duties as navigation officer, and secondary (and unofficial) tech support and all-around "computer guy".
Those of you who don't know what horrors this demonic brand pertains to, I envy you. But I digress. In the ship, we had Ethernet cabling and switches, but no DHCP, no server, not a thing. My proposition was shot down by the CO within 2 minutes. Yet, we had a curious "network". As my fellow... colleagues had invented, we had something akin to token ring, but instead of tokens, we had low-rank personnel running around with USB sticks, and as for "rings", well, anyone could snatch up a USB-carrier and load his data and instructions to the "token". What on earth could go wrong with that system?
What indeed.
We got 1 USB infected with a malware from a nearby ship - I still don't know how. Said malware did the following observable actions(yes, I did some malware analysis - As I said before, I am not paid enough):
- Move the contents on any writeable media to a folder with empty (or space) name on that medium. Windows didn't show that folder, so it became "invisible" - linux/mac showed it just fine
- It created a shortcut on the root folder of said medium, right to the malware. Executing the shortcut executed the malware and opened a new window with the "hidden" folder.
Childishly simple, right? If only you knew. If only you knew the horrors, the loss of faith in humanity (which is really bad when you have access to munitions, explosives and heavy weaponry).
People executed the malware ON PURPOSE. Some actually DISABLED their AV to "access their files". I ran amok for an entire WEEK to try to keep this contained. But... I underestimated the USB-token-ring-whatever protocol's speed and the strength of a user's stupidity. PCs that I cleaned got infected AGAIN within HOURS.
I had to address the CO to order total shutdown, USB and PC turnover to me. I spent the most fun weekend cleaning 20-30 PCs and 9 USBs. What fun!
What fun, morons. Now I'll have nightmares of those days again.

So, continuing the story, in reverse order, on the warship and its domain setup...
One day, the CO told me that we needed to set up a proper "network". Until now, the "network" was just an old Telcom switch, and an online HDD. No DHCP, no nothing. The computers dropped to the default 169.254.0.0/16 link local block of addresses, the HDD was open to all, cute stuff. I do some research and present to him a few options. To start things off, and to show them that a proper setup is better and more functional, I set up a linux server on one old PC.
The CO is reluctant to approve of the money needed (as I have written before, budget constraints in the military is the stuff of nightmares, people there expect proper setups with two toothpicks and a rubber band). So, I employ the very principles I learned from the holy book Bastard Operator From Hell: terrorizing with intimidating-looking things. I show him the linux server, green letters over black font, ngrep -x running (it spooks many people to be shown that). After some techno-babble I got approval for a proper rack server and new PCs. Then came the hard part: convincing him to ditch the old Telcom switch in favour of a new CISCO Catalyst one.
Three hours of non-stop barrage. Long papers of NATO specifications on security standards. Subliminal threats on security compromises. God, I never knew I would have to stoop so low. How little did I know that after that...
Came the horrors of user support.
Moral of the story: an old greek saying says "even a saint needs terrorizing". Keep that in mind.

$ sudo pacman -Syu
*enter*
"283 updates available"

The only thing I can think of is:

Please, don't break my system.
Please, don't break my system.
Please, don't break my system.
Please, don't break my system.

'$ y' *enter*

*gives me creeping horrors*

Speechless 😆

I think I want to quit my first applicantion developer job 6 months in because of just how bad the code and deployment and.. Just everything, is.

I'm a C#/.net developer. Currently I'm working on some asp.net and sql stuff for this company.

We have no code standards. Our project manager is somewhere between useless and determinental. Our clients are unreasonable (its the government, so im a bit stifled on what I can say.) and expect absurd things from us. We have 0 automated tests and before I arrived all our infrastructure wasn't correct to our documentation... And we barely had any documentation to begin with.

The code is another horror story. It's out sourced C# asp.net, js and SQL code.. And to very bad programmers in India, no offense to the good ones, I know you exist. Its all spagheti. And half of it isn't spelled correctly.

We have a single, massive constant class that probably has over 2000 constants, I don't care to count. Our SQL projects are a mess with tons of quick fix scripts to run pre and post publishing. Our folder structure makes no sense (We have root/js and root/js1 to make you cringe.) our javascript is majoritly on the asp.net pages themselves inline, so we don't even have minification most of the time.

It's... God awful. The result of a billion and one quick fixes that nobody documented. The configuration alone has to have the same value put multiple times. And now our senior developer is getting the outsourced department to work on moving every SINGLE NORMAL STRING INTO THE DATABASE. That's right. Rather then putting them into some local resource file or anything sane, our website will now be drawing every single standard string from the database. Our SENIOR DEVELOPER thinks this is a good idea. I don't need to go into detail about how slow this is. Want to do it on boot? Fine. But they do it every time the page loads. It's absurd.

Our sql database design is an absolute atrocity. You have to join several tables together just to get anything done. Half of our SP's are failing all the time because nobody really understands the design. Its gloriously awful its like.. The epitome of failed database designs.

But rather then taking a step back and dealing with all the issues, we keep adding new features and other ones get left in the dust. Hell, we don't even have complete browser support yet. There were things on the website that were still running SILVERLIGHT. In 2019. I don't even know how to feel about it.

I brought up our insane technical debt to our PM who told me that we don't have time to worry about things like technical debt. They also wouldn't spend the time to teach me anything, saying they would rather outsource everything then take the time to teach me. So i did. I learned a huge chunk of it myself.

But calling this a developer job was a sick, twisted joke. All our lives revolve around bugnet. Our work is our BN's. So every issue the client emails about becomes BN's. I haven't developed anything. All I've done is clean up others mess.

Except for the one time they did have me develop something. And I did it right and took my time. And then they told me it took too long, forced me to release before it was ready, even though I had never worked on what I was doing before. And it worked. I did it.

They then told me it likely wouldn't even be used anyway. I wasn't very happy at all.

I then discovered quickly the horrors of wanting to make changes on production. In order to make changes to it, we have to... Get this

Write a huge document explaining why. Not to our management. To the customer. The customer wants us to 'request' to fix our application.

I feel like I am literally against a wall. A huge massive wall. I can't get constent from my PM to fix the shitty code they have as a result of outsourcing. I can't make changes without the customer asking why I would work on something that doesn't add something new for them. And I can't ask for any sort of help, and half of the people I have to ask help from don't even speak english very well so it makes it double hard to understand anything.

But what can I do? If I leave my job it leaves a lasting stain on my record that I am unsure if I can shake off.

... Well, thats my tl;dr rant. Im a junior, so maybe idk what the hell im talking about.

I see too many back-end rants against front-ends.

Should we talk about table layouts, malformed html, programatically generated spaghetti wrong markup, css absurd class naming, infinite div wrapping (div-itis), awful usability, poor legibility, terrible typography, wrong color palettes and user-unfriedly design? To name a few horrors i've seen so far.

Some people won't admit that their contempt against HTML and CSS being 'not real code' actually hides their inability or unwillingness to learn it. Or they need the feeling of superiority.

I used to work for a company in 2017 that was affiliated with a ruling party's tax information agency. The website was janky and the database .. oh the horrors.

Every single record was a JSON object stored in a NEW COLUMN.

That's right. If you had 10K records then the table had 1 row with 10K columns with each column contained JSON data in it.

I understood then, why government websites are so crap.

Anyway, I untangled it and made the performance better to a degree that my then-boss didn't believe what I pulled off.

But yeah, I never got any pay increments or whatever, It was a good dopamine boost to my boss which lasted only 15 mins.

I don't believe in improving code ever since because of the fact that I ain't getting paid extra, so why bother.

Tru story:

We have a folder that we keep as shared documentation known as Javascript And PHP Fuckery made by yours truly in which I added a bunch of fixes to fuckery written in those 2 languages by previous developers.

The entire department has access to those files(as in all of IT) and I have been commended by the head of our department for my determination and uncanny ability to spot fuckery and fix it.

He says that he "thoroughly enjoys my colorful mastery of language, sarcasm and cognitive imagery when dealing with documentation regarding the code horrors done by previous developers"

By cognitive imagery he said that he meant my thought process and that he wouldn't trust a developer that does not use this language.

Fucking killing it b.

I'll let y'all(as in youse) when I am done with my Book(if anyone here steals the idea of the title as js php fuckery i am gonna sue you)

The horrors persist, but so do I.

In a universe where JavaScript was never invented, the world of programming might look vastly different. Perhaps another programming language would have taken its place, or multiple languages would have coexisted in a more harmonious ecosystem.

Without the challenges posed by JavaScript, web development may have been smoother and more streamlined. Websites could have been faster and more responsive, without the need for complex optimization techniques. There might have been fewer security vulnerabilities to worry about, and the web could have been a safer place for users.

In this utopian world, developers would have had more time to focus on building great user experiences and innovative features, rather than battling with cross-browser compatibility issues and JavaScript quirks. The internet would have been a more accessible and inclusive place, with fewer barriers to entry for those who want to build and create.

Overall, a world without the horrors of JavaScript would have been a world with less frustration and more possibilities.

(Fooling around with ChatGPT)

Well thus far is a bunch of rails small jobs. Funny enough this week I managed to get a bunch of php contracts "with the possibility to extend for larger contracts"

I am not really interested in long term contracts, but being that most developers that I see hired for small php jobs are not used to the patterns of development used for modern php and that i bring in a lot of my own stuff for it I know that I will be maintaining them for the long run.

So good stuff. Lets see how the week pans out. Getting really excited. Even tho I see more horrors in php than even on JS or ASP.NET or Java I still really love all languages that I have used. And normally I work like a mechanic. In which I bill by the hour(i am an expensice hooker...I mean developer) and finish everything as fast as possible to let me lazy around the house. So for example, if something takes 10 hours I will do it i 5 or less and charge all 10 hours, or I would charge per build(custom login and registration that kind of deal) and yeah. Pretty basic.

Good shit man!

yesterday I had to use a Windows VM.

Took me less than 5 minutes to remember why I'm no longer using it.

- I'm doing nothing; CPU is at 100%
- Laggy AF
- Windows Updates not only download, but also install themselves and restart my OS automatically
- right after restart it starts downloading and installing another set of updates (restarted my PC while I was away, I come back - all my work is gone. And this dumbass Windows has a popup "I want to install more updates. When should I restart?")

ooohhh the horrors

The horrors of working on 3 projects that look almost the same - finding out that the file you've been working on belongs to a wrong different site.

I finally attempted php, I wrote a bunch of scripts to fetch data... I feel like I have betrayed myself 😞😞😞
I should have just absorbed the cost of azure 😭😭😭 now am a php dev.... The things I'm about to do, the horrors I'm about to put out into the world.... Pulling your hair out will be the least of your worries, dear maintainer forgive us all, always and forever. 😳

Poll: do you think everyone, especially managers, should read The Phoenix Project?

My personal opinion: yes... They need to understand the horrors from unplanned work and how to prevent it... I'm getting really tired of checking up after people...

Starting work like "How the hell am i going to do this !!"
ending it like "was that even a task !!"
the excitements and horrors of code.

just a quick rant to express my HATRED towards java.

Today I played minecraft a bit to release some stree (plis dont tell anybody xD)

FUCKING HELL

1) Java boasts with its portability. Except it doesnt even have a proper runtime for linux
2) ITS SUPER SLOW
3) FAHCKING HELL it's so broken when you start with custom hardware (might be the fault of Gl tho)

^^ those points dont list the horrors of coding in it. I have already accomplished some coding challenges in it, and I know it to be an epitome of misery

scraping websites gave me some insights on different design patterns and OH MY GOSH THE HORRORS IV'E SEEN!
some are so inconsistent as if they had been designed and saved with ms word. another loads the whole sites content on every request as an bloated object. i think of me being just an amateur developer, but these seemed likely unprofessional or overengineerd. not what i would expect from major companies.

!dev

Vampire homegirl and I got into bit of a pickle last time we went out marauding around the City of the Dead. We collected payment for a hit on a merchant, but a large portion of the money was discounted, as unbeknown to us, there was a witness to our bloody crime.

Soon enough, we were being hunted down by a rival sect, encroaching on our territory. Their High Priest sent some dogs our way, and we felt right into their ambush, at a crossroads within the southern alleways. I took down three of those sons of bitches, with two crossbow bolts stuck on my back, before finally being knocked down by a shield slammed to my face.

Got both my fucking legs mauled with a flail and almost put out of commission. Luckily, my vampiric companion was there to save my skin. She fought a desperate duel against the last one of our foes left standing: an inquisitor, sent to either capture, or more likely, kill us both.

This fucker was tougher than any adversary either of us had ever fought against. Fully clad in silver armor, wearing an enchanted crimson cloak, her face hidden behind a terrifying iron mask. My companion stood her ground, but throughout the fight, she was constantly on the defensive, hesitant to close too much distance against the enemy.

Our foe launched one devilishly mighty blow, that my partner in crime fortunately managed to block. However, her blade was pulverized by the sheer weight of the inquisitor's strike, nearly shattering her ribcage. In a last ditch effort to survive the encounter, she lunged at her opponent with what remained of her sword, and stabbed the hunter right in her fucking eye, to then sink her fangs into the ecclesiastical bitch's neck.

Having temporarily incapacitated the inquisitor, we made our escape. My companion carried me back to our safehouse, where we would plan our next move... but our masters were one step ahead of us.

At our hideout, we were intercepted by them, at the behest of the Matriarch. We were to be smuggled out of the city inside a funeral carriage, to then be safely transported back to our sacred order's sanctuary.

Uppon arriving, we were confronted and reprimanded for our failures, past and present. I was forcefully separated from my esteemed nocturnal friend, as way our masters put it, our growing affections were cause for concern. Longing to be reunited, we schemed for weeks through our mutual acquaintances in the monastery, delivering small coded messages.

Through our cunning subterfuge, we finally managed to meet in an ancient grotto underneath a cedrus tree, on a hill overlooking the sanctuary. I was ready to plan a daring escape, but to my suprise, she had her mind made up to a wildly different course of action. We were to play by their rules -- go through with their dark cleansing rituals, meant to re-educate us before admitting us back into the order as fully-fledged acolytes.

And so, in the penumbra of that age-old grotto, a pact was made.

I am now riding south on a black stallion, falchion in hand, and a trail of witches' blood in my wake. I carry with me orders from the Matriarch herself: purify the nearby catacombs and prove my devotion to the utter blackness of our faith. Should I not return, my companion will be up next.

Failure is not an option. As I evade the twisted creatures that guard the entrance, and descend the staircase down into the tomb, I wonder what kind of horrors await me inside...

OH GOD FUCKING SHIT I JUST STEPPED ON A TRAP

** TO BE CONTINUED **

I was tasked with reviving this mobile app purchased off the shelf. Initially, I was impressed with what I was seeing while perusing the codebase. I'm used to editing laravel projects written by handpicked amateurs. So this felt like a breath of fresh air. Coupled with the fact that I'd recently enquired on this very platform whether anyone has chanced upon an impressive code. All is going well, until

I start finding the multi layers of abstraction and indirection cryptic and obfuscatory; and that is coming from an idealist like me who advocates for "clean" patterns such as event emission. I wonder whether it would have helped if the emission or events were typed for easy listener tracking, instead of a black hole like vm.notifyListeners() (DOESN'T EVEN HAVE AN EVENT NAME!)

With time, I become disgusted by the tons of custom elements with so many parents

My take on production level user of the view model pattern: amazing in theory

One of the architectural decisions made on this project that had me foaming in the mouth, pulling my hair and cursing out the author's generations, past, present and future: can you believe these guys are APPENDING IMAGE DOMAINS TO THE RESOURCE? Ie the domain names are tightly coupled to the images and dictated by the api, instead of the client

If this isn't bad enough, the field names of returned entities/models don't exist on the database, of course because the stupid laravel framework abets this sort of madness by combining eloquent "scopes, attributes, and appends". A trifecta of horrors.

I eventual scaled through the horrors, but not without losing my admiration for the team behind it. App has returned to the shelves, because my company lost patience with my resuscitating it. They have the regular api authentication in place, but that's not good enough. They just had to integrate firebase as well, just because. Meanwhile, this isn't documented anywhere. I stumbled into it during my scuffle with app setup, gradle ish. Eventually got banned by firebase for "sending unusual requests". My company's last straw

Going through online course that uses a language with 1-based indexing. All those errors. Oh the horrors. :-S

Oh god I just experienced the horrors of returning 301....

Thank god it's not on production yet...

Fastcsv is my knight in shining armour. After reliving the horrors of handling utf-8 csv files with the built in library of Python 2.7 it made my day to see everything work.

Today, I began learning about the wonders and horrors of HA in production environments.

My head feels like when I first joined the company as a total noob who never worked an IT job in his life. Soooooooo much new information and concepts and potential issues to learn to avoid.

But all super interesting!

Reading... About coding? And the horrors when monkeys code?