Hello {Project}, my old friend. I've come to debug you again
Because the scope is softly creeping
Left its seeds while I was developing
And the misery that was planted in my brain
Still remains
Within the sound of silence...

In restless dreams I debugged alone
Narrow file of cobbled code
‘Neath the halo of a desk lamp
I turned my collar to the cold and damp
When my eyes were stabbed by the flash of git checkin
That split the night
And touched the sound of silence

And in the naked light I saw
Ten thousand bugs and maybe more
People coding without asking
People coding without listening
People writing code that they never share
And no one dared
Disturb the sound of silence

Fools, said I, you do not know
{Project} like a cancer grows
Hear my words that I might teach you
Take my arms that I might reach you
But my words, like silent raindrops fell
And echoed in the wells of silence.

And the people bowed and prayed
To the kludgy app they made
And the sign flashed out its warning
In the words that it was forming
And the sign said, the words of the prophets are written on the subway walls
And tenement halls
And whispered in the sounds of silence

Manager: Good news everyone, I made a big giant announcement this morning that the app upgrades will be released today!

Dev: They definitely won’t be, we need another 2 weeks minimum. I told you yesterday

Manager: Ok well I already made the announcement that today was the day so too bad for you.

Dev: Doesn’t change the state of things

Manager: 😡 This announcement is supposed to motivate you to work faster! You guys are making me look bad when you don’t support me like this!

Dev: Working as fast as we can, it’s a 2 person dev team for 4 separate applications so it’s quite a bit to get pushed through

Manager: Ok well then stay extra then, we have to get this out asap. Tell your spouses they are not going to be seeing much of you until this work is done. People are starting to ask questions!!!!!

Dev: Not my problem, it’s done when its done. I’m not staying extra.

Manager: !!

// *************

Might be blowing my cover a little but what are they going to do? Fire me? Good luck getting this out without me. They’ve tried to replace me in the past but the cheapest person they could find was 60k more expensive than me and still couldn’t keep up. Probably they’ll ship the work overseas and the code will die in a dumpster fire and cost them even more. Ah well, just another company that doesn’t deserve code.

Sometimes I wish I was allowed to just strangle my colleagues...

Example from the 'code base':

try:
do_something()
except Exception as e:
log(e)
do_something()

When I asked why they would redo the same call right after it failed I was told that 'It works the second time because it takes time to raise the Exception '.

Bitch, you've got a race condition in your sensitive banking software. You know it's there. Do you really want to trust the time needed to raise your exception will always be enough to synch that dumpster fire you call code?
Show some fucking respect for your craft and fix that shit. But of course they won't, because it will work flawlessly until it suddenly stops working. Taking down who knows what in this damn, undocumenred monolith with it....

Sometimes I'm honestly afraid to trust banks with my money.

tl;dr I need ideas on how to warn the next dev(s) that the company is a dumpster fire.

------

For the past week (actual time: three days) I've been writing documentation for work, since there isn't any. It's been okay, I guess. Certainly more interesting than anything else I've done at work in months.

I'm up to 10k words / 67kb of markdown, and I think I'm done. I could easily write another 30k words on everything, but I just can't care enough.

However, what I do care about is warning the next dev(s) about how terrible the place is to work, so I want to add little references or hints or other such things to my writing. To complicate that, there's a contractor dev who said he will edit the document to strip out my commentary and make it "friendly" for the next person. (I can kind of see why: I've been quite honest about the situation of everything, and it's pretty dire. If they read it as-is, they might just walk out the door. I certainly would have.) I'm also going to commit it to the repo, and afaik he doesn't have push rights, so he can't force-push and remove it. (and a force-push by someone else, adding my documentation immediately after I leave... that would be pretty fishy, too.)

Anyway, at someone's suggestion, I added a "three envelopes" reference in the access phrase generator section. I also wrote "Promises made outside of ES6 will not resolve" -- in the warning section of a document almost entirely about Rails. (because the boss has broken every single promise he has ever made me.)

What other hints and subtle warnings could I add?

(And hurry: tomorrow is my last day! ;3)

The tech stack at my current gig is the worst shit I’ve ever dealt with...

I can’t fucking stand programs, especially browser based programs, to open new windows. New tab, okay sure, ideally I just want the current tab I’m on to update when I click on a link.

Ticketing system: Autotask
Fucking opens up with a crappy piss poor sorting method and no proper filtering for ticket views. Nope you have to go create a fucking dashboard to parse/filter the shit you want to see. So I either have to go create a metric-arse tonne of custom ticket views and switch between them or just use the default turdburger view. Add to that that when I click on a ticket, it opens another fucking window with the ticket information. If I want to do time entry, it just feels some primal need to open another fucking window!!! Then even if I mark the ticket complete it just minimizes the goddamn second ticket window. So my jankbox-supreme PC that my company provided gets to strugglepuff along trying to keep 10 million chrome windows open. Yeah, sure 6GB of ram is great for IT work, especially when using hot steaming piles of trashjuice software!

I have to manually close these windows regularly throughout the day or the system just shits the bed and halts.

RMM tool: Continuum
This fucker takes the goddamn soggy waffle award for being utterly fucking useless. Same problem with the windows as autotask except this special snowflake likes to open a login prompt as a full-fuck-mothering-new window when we need to open a LMI rescue session!!! I need to enter a username and a password. That’s it! I don’t need a full screen window to enter credentials! FUCK!!! Btw the LMI tools only work like 70% of the time and drag ass compared to literally every other remote support tool I’ve ever used. I’ve found that it’s sometimes just faster to walk someone through enabling RDP on their system then remoting in from another system where LMI didn’t decide to be fully suicidal and just kill itself.

Our fucking chief asshat and sergeant fucknuts mcdoogal can’t fucking setup anything so the antivirus software is pushed to all client systems but everything is just set to the default site settings. Absolutely zero care or thought or effort was put forth and these gorilla spunk drinking, rimjob jockey motherfuckers sell this as a managed AntiVirus.

We use a shitty password manager than no one besides I use because there is a fully unencrypted oneNote notebook that everyone uses because fuck security right? “Sometimes it’s just faster to have the passwords at the ready without having to log into the password manager.” Chief Asshat in my first week on the job.

Not to mention that windows server is unlicensed in almost every client environment, the domain admin password is same across multiple client sites, is the same password to log into firewalls, and office 365 environments!!!

I’ve brought up tons of ways to fix these problems, but they have their heads so far up their own asses getting high on undeserved smugness since “they have been in business for almost ten years”. Like, Whoop Dee MotherFucking Doo! You have only been lucky to skate by with this dumpster fire you call a software stack, you could probably fill 10 olympic sized swimming pools to the brim with the logarrhea that flows from your gullets not only to us but also to your customers, and you won’t implement anything that is good for you, your company, or your poor clients because you take ten minutes to try and understand something new.

I’m fucking livid because I’m stuck in a position where I can’t just quit and work on my business full time. I’m married and have a 6m old baby. Between both my wife and I working we barely make ends meet and there’s absolutely zero reason that I couldn’t be providing better service to customers without having to lie through my teeth to them and I could easily support my family and be about 264826290461% happier!

But because we make so little, I can’t scrap together enough money to get Terranimbus (my startup) bootstrapped. We have zero expendable/savable income each month and it’s killing my soul. It’s so fucking frustrating knowing that a little time and some capital is all that stands between a better life for my family and I and being able to provide a better overall service out there over these kinds of shady as fuck knob gobblers.

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

I used to love my job.

Then I disliked my job.

The people I worked with kept me at my job.

When those people left all I had was my dislike.

Now I hate my job.

And I'm really starting to hate the people I work with.

I'm not even sure I even want to keep developing anymore, but at this point I couldn't support my family any other way.

So I'll stay smouldering for the next 40 years, in a career dumpster fire that's long lost its magic just so I can give my family a better life.

(Best read while listening to AEnima by Tool, loudly)

Dear Current Workplace,

Fuck you, for the reasons enumerated below.

Fuck your enterprise grey blue offices, the stifling warm air of a hundreds of bodies and sub par "development laptops".

Fuck your shitty carbonated water machines which were a cost saving measure over decent drinkable water.

Fuck your fake "flexi time", "you can do home office whenever you want" bullshit. You're still inviting me to mandatory meetings at 09:00 regularly.

Fuck your shitty, in house, third part IT provider sister company. They're the worst of all worlds. If it was in company, we'd get to give out to them, if it was an external company we'd fire them. And yes, when I quit I will quote the dumpster fire that is our corporate VPN as a major factor.

Fuck your cheery, bland, enterprise communication. Words coming under the corporate letterhead seem to lose all association with meaning. Agile, communication, open are things you write and profess to respect, but it seems your totally lack understanding of their meaning.

Fuck your client driven development. Sometime you actually have to fix the foundations before you can actually add new features. And fuck you management who keep on asking "why are there so many bugs and why is it always taking longer to deliver new releases". Because of you, you fucknuts, Because you can't say "NO" to the customer. Because you never listen to your own experienced developers.

Fuck your bullshit "code quality is important to us" line. If it's so important, then let us fix the heap of shit you're selling so that it works like a quasi functional program.

Fuck you development environment which has 250 projects in a single VS solution. Which takes 5mins plus to compile on a quad core i7 with 32 gb of ram.

Fuck this bullshit ball of mud "architecture". I spend most of my time trying to figure out where the logic should go and the rest of the time writing converters between different components. All because 7 years ago some idiot "architect" made a decision that they didn't have to live with.

Actually, fuck that guy in particular. Yeah, that guy who was the responsible architect for the project for 4 years and not once opened the solution to look a the code.

Fuck the manual testing of every business process. Manual setup of the entities takes 10mins plus and then when you run, boom either no message or some bullshit error code.

Fuck the antiquated technology choices which cause loads of bugs and slow down development. Fuck you for forcing me to do manual tests of another developers code at 20:00 on a Friday night because we can't get our act together to do this automatically.

Fuck you for making sure it's very clear I'm never going to be anything but a code monkey in this structure. Managers are brought in from outside.

Fuck you for being surprised that it's hard to hire competent developers in this second rate, overpriced town. It's hard to hire anywhere but this bland shithole would have anyone with half a clue running away at top speed.

Fuck you for valuing long hours and loyalty over actual performance. That one guy who everyone hated and was totally incompetent couldn't even get himself fired. He had to quit.

Fuck you for your mediocrity.

Fuck you for being the only employer for my skill-set in the region; paying just well enough that changing jobs locally doesn't make sense, but badly enough that it's difficult to move.

Fuck you for being the stable "safe" option so that any move is "risky".

Fuck your mediocrity.

Fuck you for being something I think about when I'm not at work. Not only is it shit from 9 to 5 you manage to suck the joy out of everything else in my life as well?

Fuck you for making me feel like a worse developer every day I work here. Fuck you for making every day feel like a personal and professional failure. Fuck you for making me seriously leave a career I love for something, anything else.

Fuck you for making the most I can hope for when I get up in the morning is to just make it until the night.

Windows 10 'App Store' Stole My Money.

So I work a 40 hour work week, sometimes more, same as anyone, on my feet, all day.

I get home, buy a little $3.99 app. Won't install. Check it again won't install. I check some guides. Follow all the standard commands, my purchase won't install. Use the tools. won't install.

Naturally I sent off what I'm good at, some hate filled invective

For fucks sake. I'm exhausted, have insomnia and want to wind down. And here microsoft is killing 32bit libraries to dispose of competing services like steam (also fuck gabe in his fat asshole) but I digress.

And they expect us to use their services? Spend our hard earned *fucking money*..and spend half an hour on their dumpster fire fucking 'walled garden' with nothing to fucking show for it?

No refund button. No chat option. Just a fucking feedback hub. Look at it some time. JUST LOOK AT IT. The motherfucking *feedback* hub *frozeup* in the process of my feedback. Microsoft is a sewer of negligent business practices and incompetence.

So I've chosen now to aim two heavy ion cannons at them and warned them too. Two twitter accounts, one with almost 10k followers and another with 15k.

Should have just offered a manual download button microsoft.

My money would have been better spent on alcohol. Cheap alcohol. It's not like it's a lot of money and I don't buy a lot online, but it's the principle. You're fucking *payment* process worked *just fucking fine*.

Anyway can anyone calculate the monetary damage a cumulative quarter million views over the course of a month will do to the reputation of the windows store in dollar amounts?

I'm betting it's going to be a lot fucking more than three fucking ninety nine.

Don't worry microsoft, I'm gonna take it out of your sweet fucking hide.

Highlights from my week:

Prod access: Needed it for my last four tickets; just got it approved this week. No longer need it (urgently, anyway). During setup, sysops didn’t sync accounts, and didn’t know how. Left me to figure out the urls on my own. MFA not working.

Work phone: Discovered its MFA is tied to another coworker’s prod credentials. Security just made it work for both instead of fixing it.

My merchant communication ticket: I discovered sysops typo’d my cronjob so my feature hasn’t run since its release, and therefore never alerted merchants. They didn’t want to fix it outside of a standard release. Some yelling convinced them to do it anyway.

AWS ticket: wow I seriously don’t give a crap. Most boring ticket I have ever worked on. Also, the AWS guy said the project might not even be possible, so. Weee, great use of my time.

“Tiny, easy-peasy ticket”: Sounds easy (change a link based on record type). Impossible to test locally, or even view; requires environments I can’t access or deploy to. Specs don’t cover the record type, nor support creating them. Found and patched it anyway.

Completed work: Four of my tickets (two high-priority) have been sitting in code review for over a month now.

Prod release: Release team #2 didn’t release and didn’t bother telling anyone; Release team #1 tried releasing tickets that relied upon it. Good times were had.

QA: Begs for service status page; VP of engineering scoffs at it and says its practically impossible to build. I volunteered. QA cheered; VP ignored me.

Retro: Oops! Scrum master didn’t show up.

Coworker demo: dogshit code that works 1 out of 15 times; didn’t consider UX or user preferences. Today is code-freeze too, so it’s getting released like this. (Feature is using an AI service to rearrange menu options by usage and time of day…)

Micromanager response: “The UX doesn’t matter; our consumers want AI-driven models, and we can say we have delivered on that. It works, and that’s what matters. Good job on delivering!”

Yep.
So, how’s your week going?

We hired a new senior dev. The lead architect is going over basic bit branching and commits with him. This new job already feels like a dumpster covered in petrol.

I think, after a few weeks, I'm actually quite enjoying that the Android SDK is genuinely awful.

We all know the feeling: "This is shit, whoever designed this is a fuc...oh, I get it. This is pretty cool actually."

So, it's nice to encounter a genuine dumpster fire of a platform.

I think the beautiful thing about its absolute obsession with providing a context to every single operation, is that you end up passing it around so much that the very concept of context becomes redundant.

Honestly, half of the stuff in here I've just attached to a global statics class, because it saves having to request a context, or a manager or some fucking kind of adapter, and it works just fine.

I've started to laugh when I look up a solution and see the browser scrollbar shrink into infinity, because the recommended answer is about two whole pages' worth of boilerplate to make the back button disappear or something.

I don't think there's been a single moment where I've just been in the flow of writing code. Pretty much all of the process is grafting boilerplate into it.

Not long til deadline, thank fuck.

Today I had what might have been my worst job interview to date. It had many different technical, cultural, and business red flags. One that really stuck out to me was when I asked my interviewer why he loves his job, he went on about how great the benefits and events are. Not a single word about the work he does or his teammates. A younger me would have seen this as an opportunity to put in some hard work and contribute to something great. Older me knows to avoid this dumpster fire like the goddamn plague.

Joined a place where I am the only FE engineer and the product is mature (around 15yrs).

Every single framework you can think of is there. The codebase is such a mess that it makes spaghetti looks neat, organized and logical.

I need to port the code to the latest standard but everything is so bad that tasks that would take a week or 2 max are taking almost a month.

I’m gonna cry. I feel so incompetent even though it’s not my fault.

Angular is still a pile of steaming donkey shit in 2023 and whoever thinks the opposite is either a damn js hipster (you know, those types that put js in everything they do and that run like a fly on a lot of turds form one js framework to the next saying "hey you tried this cool framework, this will solve everything" everytime), or you don't understand anything about software developement.

I am a 14 year developer so don't even try to tell me you don't understand this so you complain.
I build every fucking thing imaginable. from firmware interfaces for high level languaces from C++, to RFID low level reading code, to full blown business level web apps (yes, unluckily even with js, and yes, even with Angular up to Angular15, Vue, React etc etc), barcode scanning and windows ce embedded systems, every flavour of sql and documental db, vectorial db code, tech assistance and help desk on every OS, every kind of .NET/C# flavour (Xamarin, CE, WPF, Net framework, net core, .NET 5-8 etc etc) and many more

Everytime, since I've put my hands on angularJs, up from angular 2, angular 8, and now angular 15 (the only 3 version I've touched) I'm always baffled on how bad and stupid that dumpster fire shit excuse of a framework is.

They added observables everywhere to look cool and it's not necessary.
They care about making it look "hey we use observables, we are coo, up to date and reactive!!11!!1!" and they can't even fix their shit with the change detection mechanism, a notorious shitty patchwork of bugs since earlier angular version.

They literally built a whole ecosystem of shitty hacks around it to make it work and it's 100x times complex than anything else comparable around. except maybe for vanilla js (fucking js).

I don't event want todig in in the shit pool that is their whole ecosystem of tooling (webpack, npm, ng-something, angular.json, package.json), they are just too ridiculous to even be mentioned.

Countless time I dwelled the humongous mazes of those unstable, unrealiable shitty files/tools that give more troubles than those that solve.

I am here again, building the nth business critical web portal in angular 16 (latest sack of purtrid shit they put out) and like Pink Floyd says "What we found, same old fears".
Nothing changed, it's the same unintelligible product of the mind of a total dumbass.

Fuck off js, I will not find peace until Brendan Eich dies of some agonizing illness or by my hands

I don't write many rants but this, I've been keeping it inside my chest for too long.

I fucking hate js and I want to open the head of js creator like the doom marine on berserk

Been asked if we can make a few "minor tweaks" to a Visual Basic 6.0 application last worked on in 2013.

I haven't coded in Visual Basic in approximately 20 years, the project can't be opened in Visual Studio 2012 or above and the code I've seen is a dumpster fire.

Please send help.

How do you deal with massively poorly-performing and unknowledgeable teams?

For background, I've been in my current position for ~7 months now.

A new manager joined recently and he's just floored at the reality of the team.

I mean, a large portion of my interview (and his) was the existing manager explicitly warning about how much of a dumpster fire everything is.

But still, nothing prepares you for it.

We're talking things like:
- Sequential integer user ids that are passable as query string args to anonymous endpoints, thus enabling you to view the data read by that view *for any* user.
- God-like lookup tables that all manner of pieces of data are shoved into as a catch-all
- A continued focus on unnecessary stored procedures despite us being a Linq shop
- Complete lack of awareness of SOLID principles
- Actual FUD around the simplest of things like interfaces, inversion of control, dependency injection (and the list goes on).

I've been elevated into this sort of quasi-senior position (in all but title - and salary), and I find myself having to navigate a daily struggle of trying to not have an absolute shit fit every time I have to dive into the depths of some of the code.

Compounded onto that is the knowledge that most of the team are on comparable salaries (within a couple thousand) of mine, purely owing to length of service.

We're talking salaries for mid-senior level devs, for people that at market rates would command no more (if even close) than a junior rate.

The problem is that I'm aware of how bad things are, but then somehow I'm constantly surprised and confronted with ever more insane levels of shitfuckery, and... I'm getting tired.

It's been 7 months, I love the job, I'm working in the charity sector and I love the fact that the things I'm working on are directly improving people's lives, rather than lining some fintech fatcat's pockets.

I guess this was more a rant than a question, and also long time no see...

So my question is this:

- How do you deal with this?
- How do you go on without just dying inside every single day?

Front-end web development in 2018 is a fucking dumpster fire. 4 month old blog post guides are out of date, hipster toolchain APIs change monthly, npm can't find a module that is literally right there in its entirety in the fucking node_modules directory. JavaScript is love. JavaScript is life.

Dev trend I think will pass?

Creating new frameworks on this dumpster fire of a language we call JavaScript.

Is it just me or are image uploads broken? Whenever I attach a png file pressing the "Post" button does nothing. Text alone submits fine, so it's not because of my dumpster fire of a text.

It seems now I gotta rant about my failed attempt to post another rant because I'm in a ranting rant mood.

Just started onboarding the new hire and it made me realise how much of a dumpster fire some of our code is

Who else is loving the twitter dumpster fire? He threatens to fire the devs if they don't roll out the verified account to anyone willing to pay.

The shipped that bomb just like you demanded assface.

Toughest part of dev interviews? There are multiple I can think of.

Getting an interview altogether in this dumpster fire of an economy.

Negotiating salary (i.e. prevent getting a low-ball offer)

When the interviewer is a dev themselves and they get on a power trip and ask you the toughest/trickiest questions.

Convincing the interviewer that something you don't know now can be learned later just by googling and tinkering around.

Trying not to burst out in anger when you get asked stupid questions like "Why aren't you married?"

Ds (dipshits) keep calling my phone 6-8 times a day. Almost all automated calls.

One day AI will handle these robocallers automatically. And then it will just be GAN style robocallers vs robosecretaries training against each other to become better and better at fooling each other.

And then suddenly, one day: skynet.

With a neutral female voice.

Or maybe an Indian accent.

"Hel. Lol. m I k r O s o t tech surprott. We detect virus on ur peesee. You will be assimilated. Where joon connor?"

Like a possessed speak-n-spell melting to death in a dumpster fire.

And we'll have done it to ourselves.

I am scratching my head since 2 days cause a rather large Dockerfile doesn't work as expected.

CMD Execution just leads to "File not found".

Thanks, that's as useless as one ply toilet paper...

Whoever wrote the Dockerfile (not me…) should get an oscar...

Even in diarrhea after eating the good one day old extra hot china takeout from dubious sources I couldn't produce such a dumpster fire of bullshit.

The worst: The author thought layering helps - except it doesn't really, as it's a giant file with roughly 14 layers If I count correctly.

I just found out the problem...

The author thought it would be great to add the source files of the node project that should be built as a volume to docker... Which would work I guess....

Except that the author is a clueless chimp who thought at the same time seemingly that folder organization means to just pour everything into one folder....

Yeah. That fucker just shoved everything into one folder.

Yeeeeeesssssssss.

It looks like this:
source
docker-compose.mounts.yml
docker-compose.services.yml
docker-compose.yml
Dockerfile-development
Dockerfile-production
Dockerfile
several bash scripts
several TS / JS / config files
...

If you read the above.... Yes.
He went so far to copy the large Dockerfile 3 times to add development and production specific overrides.

I can only repeat what I said many times before: If you don't like doing stuff, ask for fucking help you moron.

-.-

*gooozfraba*

Anyways...

He directly mounts this source directory as a volume.

And then executes a shell script from this directory...

And before that shit was copied in the large gooozfraba Dockerfile into the volume.

Yeeeaaah.

We copy stuff inside the container, then we just mount on start the whole folder and overwrite the copied stuff.

*rolls eyes* which is completely obvious in this pit latrine of YML fuckery called Dockerfile.

As soon as I moved the start script outside the folder and don't have it running inside the folder that is mounted via volume, everything works.

Yeah.... Maybe one should seperate deployment from source files, runtime related stuff from build stuff.

*rolls eyes*

I really hate Docker sometimes. This is stuff that breaks easily for reasons, but you cannot see it unless you really grind your teeth and start manually tracing and debugging what the frigging fuck the maniac called author produced.

Microsoft installed an update that I didn't want and now my computer is unable to boot into Windows. It either constantly reboots before the windows logo or sits at attempting repairs forever.

Why is modern computing such a dumpster fire?

Apple is wall to wall garbage in every capacity.

Windows is the most expensive ad delivery platform you can buy, while also trying to be Apple.

Linux doesn't work unless your computer is years old.

Got one right now, no idea if it’s the “most” unrealistic, because I’ve been doing this for a while now.

Until recently, I was rewriting a very old, very brittle legacy codebase - we’re talking garbage code from two generations of complete dumbfucks, and hands down the most awful codebase I’ve ever seen. The code itself is quite difficult to describe without seeing it for yourself, but it was written over a period of about a decade by a certifiably insane person, and then maintained and arguably made much worse by a try-hard moron whose only success was making things exponentially harder for his successor to comprehend and maintain. No documentation whatsoever either. One small example of just how fucking stupid these guys were - every function is wrapped in a try catch with an empty catch, variables are declared and redeclared ten times, but never used. Hard coded credentials, hard coded widths and sizes, weird shit like the entire application 500ing if you move a button to another part of the page, or change its width by a pixel, unsanitized inputs, you name it, if it’s a textbook fuck up, it’s in there, and then some.

Because the code is so damn old as well (MySQL 8.0, C#4, and ASP.NET 3), and utterly eschews the vaguest tenets of structured, organized programming - I decided after a month of a disproportionate effort:success ratio, to just extract the SQL queries, sanitize them, and create a new back end and front end that would jointly get things where they need to be, and most importantly, make the application secure, stable, and maintainable. I’m the only developer, but one of the senior employees wrote most of the SQL queries, so I asked for his help in extracting them, to save time. He basically refused, and then told me to make my peace with God if I missed that deadline. Very helpful.

I was making really good time on it too, nearly complete after 60 days of working on it, along with supporting and maintaining the dumpster fire that is the legacy application. Suddenly my phone rings, and I’m told that management wants me to implement a payment processing feature on the site, and because I’ve been so effective at fixing problems thus far, they want to see it inside of a week. I am surprised, because I’ve been regularly communicating my progress and immediate focus to management, so I explain that I might be able to ship the feature by end of Q1, because rather than shoehorn the processor onto the decrepit piece of shit legacy app, it would be far better to just include it in the replacement. I add that PCI compliance is another matter that we must account for, and so there’s not a great chance of shipping this in a week. They tell me that I have a month to do it…and then the Marketing person asks to see my progress and ends up bitching about everything, despite the front end being a pixel perfect reproduction. Despite my making everything mobile responsive, iframe free, secure and encrypted, fast, and void of unpredictable behaviors. I tell her that this is what I was asked to do, and that there should have been no surprises at all, especially since I’ve been sending out weekly updates via email. I guess it needed more suck? But either way, fuck me and my two months of hard work. I mean really, no ego, I made a true enterprise grade app for them.

Short version, I stopped working on the rebuild, and I’m nearly done writing the payment processor as a microservice that I’ll just embed as an iframe, since the legacy build is full of those anyway, and I’m being asked to make bricks without straw. I’m probably glossing over a lot of finer points here too, just because it’s been such an epic of disappointment. The deadline is coming up, and I’m definitely going to make it, now that I have accordingly reduced the scope of work, but this whole thing has just totally pissed me off, and left a bad taste about the organization.

Me: Ok I've updated the docs, I'll open a PR with the changes

Maintainer: Looks great! Can you remove the changes to the package-lock.json? (I assume it got updated when you ran npm install to start the webserver)

Me: Ok sure, I'll update it soon

And this is where the troubles begin. The file was commited 2 commits ago, so I have to roll back to then. However, the remote repository has been updated since then, so I git fetch to keep up to date.

This makes the rollback a hell of a lot harder, so I run git log to see the history. I try a reset, but I went back to the wrong commit, and now a shit ton of files are out of sync.

I frantically google 'reset a git reset', and come across the reflog command. Running that fucks things up even worse, and now so much shit is out of sync that even git seems confused.

I try to fix the mess I've created, and so I git pull from my forked repo to get myself back to where I was. Git starts screaming at me about out of sync files, so I try to find a way to overwrite local changes from the origin.

And by this point, the only way to describe what the local repo looks like is a dumpster fire clusterfuck that was involved in a train wreck

I resolved the mess by just deleting the local copy and git cloning again from my fork.

I gotta learn how to use Git better

I tried to get this trainwreck of a middleware running again. Generations of imbecile devs turned this once ambitious project into a dumpster fire. I had some feeble hopes. Wrote a little framework to get this braindead architecture back on its track. BUT EVERY PULL REQUEST I GET TO REVIEW SHOWS THEY DON'T CARE. FML! Why am I even trying. I should have known these morons just want to pour gasoline onto an already blazingly burning software. GODDAMMIT SHOW SOME ENGINEERING SPIRIT. Why are you even in this industry in the first place?

I am witnessing Einsteins theory of relativity first hand, I’m amazed. The closer I get to Microsoft products, the slower my velocity becomes. At 9 PM, I have tried to connect a MS SQL Server to an ERP System for 30 minutes. After this piece of shit robbed me of all my energy, I look at the clock and it’s midnight. Go die in a dumpster fire Microsoft

Starting of the week inside the belly of an absolute dumpster fire from hell.
Ending the week with everything completed and running well??

It's been a good week afterall.

Happy weekend everyone!
Here's to a random return to hell next Monday.

Imagine a "development" environment with no vcs, no APIs, no general hierarchy for db admin or software development, no test environment. Well this was my first job.

Quite literally a dumpster fire.

I know I'm not a world class developer but I still think this was beyond unacceptable for a software startup.

Don't you love it when banks decide to change their "security" policies without any warning?

Logging in via private wifi? Forbidden with a nebulous message. You better download their banking app or connect to your router via cable. As if the app they keep pushing wasn't a complete dumpster fire.

Need to transfer money? Okay, just register the account and the limitations will be removed after 24 hours... Does it say 24? I'm sorry we updated our policy to 72 hours and haven't bothered updating the message.

I swear one of my new year resolutions will be to switch banks asap

Safari devtools is an absolute dumpster fire

IOS keyboard is utter garbage. IOS as a whole is utter garbage, but the keyboard is the cream of the crop of garbage.

Wasting a user's time and destroying/changing the user's input against their wishes is malicious design of the highest order and this dumpster fire excels in it.

Type something completely valid and autocomplete changes it to something that doesn't makes sense. It not only gives you a terrible suggestion half the time, it will also change previous parts of the sentence that it somehow allowed you to keep. If you reject its suggestion, it deletes your current word and previous word(s), instead of restoring it to what it was before it made the terrible suggestion, like every other keyboard does.

Need to go back and adjust your sentence? If you tap it will hijack the cursor and highlight the nearest word it doesn't like instead of moving the cursor where you touch. If you accidentally hit a character on the cramped and unusable keyboard, congrats, you get to type the word again.

I know about hold space to drag the cursor.

I don't want Apple to decide for me that I actually wanted to go to the closest word it doesn't like, or the current word, or the next word based on a dice roll. I want the cursor to go where I tap. Like literally every other input device functions.

Want readily accessible numbers and punctuation? lol no

I know there's gboard, but compared to Android it's also almost unusable. This leads me to believe the keyboard is little more than a skin over the IOS keyboard engine, like Safari, another IOS dumpster fire. But, it is slightly better than the stock keyboard, which isn't saying much.

I yearn, minute by minute, for the time I can ditch this dumpster fire for a real phone.

Can I list this experience? Will it look bad?

I am an entry level programmer in a software shop, or whatever they are called. I was given no mentorship on the task I have done. Not even proper documentation and it seems management is passing me around. What I mean by that is that the task I work on no one has ideas about since it seems the last guy who was responsible left. He was a senior though and it seems that I might have been too eager to find a job. Now I am being tasked for things a senior would do but I have the entry pay and knowledge and skill set. 2 months experience...

I am going to design a whole system from scratch and they have not read anything on it. From networking to applications to fees to compliance requirements. Oh the great part is they want it soon, no pressure, but we have to start certification within a tight deadline. This is a great opportunity and maybe a dumpster fire waiting to start. I will gain so much real experience but they are taking a great risk. It seems that is throughout their code and infrastructure though.

I plan to leave after the project. I also will document and hopefully they start reviewing my stuff to catch my incompetence. Not on purpose but from pressure and inexperience, which I hate cause I was excited at first.

I plan to stick the year or until Covid strips work-from-home, cause they are bit “old school”. I will begin my job search as well. I just know I will burn out long term and the money and package is shit.

Do I list them if I leave earlier but finish the project?

.Net Dev here with a degree in graphic design. Almost 9 months into my first dev job, 85% of it has been dealing with god damn webforms. Unfortunately, sometimes it doesn't play too nice with a bootstrap / jQuery especially with code behind and when you have post backs. I never thought I would say this but fuck the front end lol at least when it come to this dumpster fire. At least I'm learning a lot but damn I can't wait to get back into an MVC project or service work.

Today, I'm making a revolutionary change to our code base. I'm finally deprecating a script that lived in this goddamn repo for way too long. There's about 10 copies of the same script in 10 different directories. The script copies all the code into a "dev" folder and then runs "sed s/prod/dev/g" on all the files, and then overwites a bunch of it with some files suffixed with ".dev". Finally, after fighting the so-called architects, the devs and everyone else that seems to have gotten used to the pain this cursed dumpster fire script has caused us, my merge request is now open and ready to go to get rid of this insanity. Now we won't have to deal with as many "surprises" that happen every goddamn time we deploy to production, overwriting all our hard work by accident, and relieve some of my OCD of having the same script in 10 different places in the repository.

I started working at a new company a couple of weeks ago as a Dev/Ops engineer, my first real ops position after years of being mostly a dev with two sys-admin positions sprinkled in.

I should have seen the red warning signs when, during the interview, a developer told me the old devops team was so bad they fired all of them last year. After I started, I learned that all four people on our team were totally new. Three were hired after the last guy from the old team left (without any notice) and one person use to be a developer who was transferred over to this new team (but not to lead it).

Named my current project "dumpster fire" so I can say "This dumpster fire doesn't even get through compiler anymore!" will work on that level too.

I thought I posted about this awhile back but I didn't. I'm glad since the story is so much better now.
6 weeks ago: Told I'm going to be on a super fun JAMStack build with lots of sexy animations. Sweet, this will be a fun build!

5 weeks ago: Find out what the timeline on this incredibly ambitious project is. I start raising flags cause everything needs to go PERFECT for this to not blow up and/or turn in to a dumpster fire.

4 weeks ago: Project "kicks off" with a meeting with the client. We find out that they've decided to do another round of revisions on their design comps, but we have what we need for sprint 1. We provide a list of all the assets/information we still need for sprint 1 success.

3 weeks ago: Still waiting on some assets for sprint one, but we're fumbling our way through. Still waiting on the PM to get around to doing their PM job and building out our backlog / gathering requirements for us.

2 weeks ago: Sprint 1's end date comes and goes. Still need assets from the client, I've personally asked them for the same asset 3 different times. Sprint 1 gets extended 1 week.

1 week ago: We deliver sprint 1 page templates, minus the resources we're still waiting for. Get chewed out by the client regarding the pages not looking like their comps (Yeah, no shit sherlock, you never sent us the assets)

This week: Working on Sprint 2 commitments. We have 2x as many page templates to deliver, per developer, as we had the first sprint. Still waiting on Sprint 1 assets. Don't have Sprint 2 assets. Wait, what about the global styles? They still haven't sent those to us yet either.

Requirements? Guess I'll spend valuable dev time tracking those down for myself.

Client? Well, they're pissed off we haven't hit our commitments yet.

Oh well, at least we have a pimple faced, fresh out of college, CS major, with no real development experience rolling on to this cesspool of a project.

Other devs? Well, we're out of fucks to give. Lets just watch this thing burn.

Oh, I forgot to add, we have 17 page templates to deliever between today (2/27) and 3/18. #NoFuckingWay

Am I in developer hell already? A shitty project is about to come to an end (hopefully), or should I rather say: It needs to come to an end. But I am still quite lost in how to deal with it, hence procrastinating on it - making the deadline come closer and with it the realization that I'll probably have to rewrite almost everything. I'm not sure how, but I do know that the current code is a dumpster fire.

Basically what I need to do is dealing with the APIs of different payment providers/gateways (like PayPal, AmazonPay). For most cases I'll get a payment ID from the shop and need to act on it later, e.g. capture the authorized money in the case of a credit card transaction or do refunds (without user interaction, unless there is an error). Now at first I put something together where I try to abstract the payment information into two tables:
orders{1}<->{0..n}payments
payments{1}<->{1..n}paymentDetails

Unfortunately trying to abstract the different payment methods and to squeeze them (and their different possible stati and functions) in these tables was not very successful, it's a total mess with magic numbers, half-broken behavior and without any consideration for partial payments/captures or unfinished requests (i.e. if there is an exception before the response is dealt with, there is no indication that anything has ever been sent). Also the current amount is calculated through the history of the paymentDetails table, which basically works differently for each payment type.

How to fix this mess in a way that I'll still have a job by next week?

I'm trying to improve the db schema first, as I think my biggest problems are lying there. Through some research I've come across a recommendation for making payment type specific subtables (with a magic number/string in the main table to prevent having to look up all subtables). That way I can record what I send and receive without having to abstract it too much, so I'll have an acceptable transaction log. The paymentDetails table can be removed (necessary fields go to the payments table). The payments table gets multiple fields for the amount (differentiating between open, authorized, captured, processing and refunded values) and always reflects the current status.

Tables:
payments
paymentRequestsPaypal
paymentRequestsAmazonpay
paymentRequestsXyz

I think I'm going in the right direction here. hm. Maybe there's some light at the end of this long, dark tunnel. Or a train. I'll have two days to find out.

Recently helped someone with a Spark project and encountered “reactive JS” for the first and hopefully last time. Never minded using JS but happy to admit that it’s a dumpster fire design-wise…one that Spark engineers apparently decided didn’t have quite enough petrol on it.

Last Saturday, I came across a fellow techie at a house party. As soon as he found out I am a developer, the question
"What is your favorite programming language?"
came bursting not even a nano-second after I told him.

Anyone else finds this super cringe?

I believe that people who dig deep trenches in such a topic will be the root cause for the next software crisis. I mean, look at Javascript. In one of my later posts, literally noone could give me a reason to not think Javascript is a dumpster fire. And yet it spread out like a malignant tumor.

To verify not all is lost, I quickly googled any databases written in JS, and luckily just found one archived repo and nothing else. Because Im calling it, once Javascript reaches the database layer, it's terminal.

Java's garbage collector must be broken - it failed to get rid of this dumpster fire another dev called "source code". But, hey, at least the profiler works.

Was curious abut how painfu to work with and deploying .net core, asp.net core, blazor and xamarin are. I am currently learning c# and I have heard stuff such as ".net is a dumpster fire" and xamarin has had pretty negative reviews. Is that stuff true

I think I'm reaching the point of being willing to take a pay cut to transfer away from this and any other place using MarkLogic. It's just the giant dumpster fire topping off the rest of this place.

Partially-inherited a WordPress website today that 1) has a ton of outdated plugins (therefore causing Visual Composer to complain), 2 was upgraded to WordPress 5 without keeping the old TinyMCE editor around, and 3) uses a page builder that's built into the "page options" portion of the Edit view.

We also have to add a couple of pages with the project in this state.

(For those not familiar with WordPress, "Page Options" can't be previewed before the page is published/updated, even though anything inside of the actual content area can.)

We got some work to do. 😐

Oh look! Another botched NPM release.

What a dumpster fire of a codebase.

FUUUUUUUUUUUUUUUCCCCCCCKKKKKKKKKKK LOOPBACK. Fuck it right in the dickhole. Fuck IBM for paying the salary on this piece of shit. Fuck all of the copy pasting I have to do, fuck the fact that it never knows what fields my type will or will not have, fuck the 4 different versions of the docs they have for each version of this dumpster fire of a framework. This is the dumbest codebase I have ever worked with, and I hate every minute of it. One last fuck, it is for the guys who came before me and chose this for our companies server. Fuck you!

Some people think building a clone of tinder takes a weekend. Good luck with that dumpster fire of an app

Bing Ads Reporting Service is a dumpster fire of complexity...

Has anyone else ever had to work with the dumpster fire that is SCORM in js? I fucking hate it. I'd have rather had everyone develop their own course content for each platform than have SCORM exist. Fuck this.