A productive meeting requires:
1. an agenda that covers every aspect that the meeting should be about

2. Everyone at the meeting gets a chance to provide feedback and or speak about their role in the project and what's the hold up.

3. All participants or at least a dedicated one takes notes about what is covered so that people aren't asking the same questions the very next day.

There's a special place hell for people who put their entire documentation on using an NPM package in the fucking READ.ME file.

I shouldn't have to play whack a mole through one giant ass file to figure out how a specific function works. Or figure out how specific optional parameters need to be defined.

Clients that ask you to build X and then when you ask about said details to know everything up front, you get a deer in the headlights look.

I get it, not knowing right away is fine, but 5-6 months later and still "not knowing", being absolutely lazy with no responses to questions or just dumping the work to me to figure out from whatever source material you got it from and force me to crunch to save your ass isn't fun for me and I really don't give a shit about how much praise you give me publicly for the job I did.

Couple hours before:
Management: "Emergency/last minute Meeting in 2 hours! Please attend"

Meeting time:
Management: "We just wanted to let you know that our mask usage is being changed to fit the recent CDC guidance"

Total time wasted: 6 minutes. 12 if you count the time for any questions.

I don't want to ever hear that you're proficient in JavaScript if you put a callback function call inside of an async function right after using the await command.

All you manage to do in the end was make a simple function that gets data to populate a dropdown menu into something that is absolutely more awful to look at than the worst callback hell possible.

Refactoring this code base has really questioned my sanity and how much I'm willing to spend on alcohol.

Why on earth would you create an entire new HTMLImageElement in the javascript file just to get the width and height of an image and never render it to the DOM. FFS use MS Paint, 3D Paint or ANY OTHER IMAGE EDITING SOFTWARE to get the size.

Seriously you over engineered the shit out of the easiest const you'll ever write in JavaScript.

And for the record, the width and height of the image used are only used in formulas which produce the actual width and height of the mock buttons that get drawn onto the canvas element. And don't worry, the click event handler for these mock buttons is actually the click event handler for the canvas...which checks the coordinates of where the click was made on the canvas. And if the click is over where the button is drawn in, congrats you clicked the button.

I really do wonder at what point the previous developer on this project thought 800 line functions are totally reasonable and standard practice...

I always thought I suffered from imposter syndrome until I saw what the previous developer on this NodeJS/SailsJS project did.

They put return statements inside of a switch block. He also put in the break statements as well. The return statements were the exact same thing every time it was written.

Fuck shitty JS developers....

Took over a NodeJS/SailsJS project from a previous developer that is no longer working at the company. There's no documentation or requirement docs and the models need to be rewritten as some have up to 67 attributes in them.

Looked through the source code file by file to see how bad it was and it will more than likely be easier to start over then to try and refactor and cleanup the existing project into a usable state.

As bonus, I was given the option to switch the entire stack if needed as well.