The fun part of my job is showing off my age to make the point that they need to build new things in new technologies. Typical interaction goes something like this.

Person: When we started X project, we were using the state of the art technologies. We can just use that again.
Me: And when was that?
P: About 2012
Me: I was a freshman in high school.

So, I got a ticket to make a page using a given wireframe that had submit buttons and other buttons to add more items in the wireframe.

So, I pull the html, hook up the abilty to submit the form and add items, and send it out for review.

One comment on the review.

"Remove the functionality, you'll handle it in the next ticket"

So I commented out the javascript. Guess what I'm doing on the next 10 minutes.

Remember that git commits are just like commitments in a relationship.

Make them small and avoid the big ones.

Perk of being a web developer.

When a website tries to hide its content behind a pop-up become I have an ad-blocker. I can "display:none" that stuff away.

So many years ago while I was in college learning to code and interning as a developer working on a javascript based image designer. We were learning event handlers in class and I was learning how to work with jQuery.

So I decided to build an event handlers to move objects by key press. I had an afternoon free and dont remember merging it to the codebase.

A few months later, something was pushed that took key press the event handler and the testers complained about losing the event handler I made.

End of the story, I added a feature that is still being used because I wanted to learn how to do something.

So I'm about to finish The Design of Everyday things by Don Norman and I have Clean Code coming up next.

But what are some good programming books that are tech agnostic?

(Monday)
Me: I'm gonna be gone the next few days and you take care of this? I have these notes if you have questions.
Dev: Sure.

(Friday)
Me: Did you take care of it?
Dev: I had a question.
Me: Okay, did you check the notes.
Dev: They didn't address my question. (Proceeds to ask question)
Me: Let me show you my notes where I answered it.
Dev: Oh sorry.....

Me: Alright today I'm going to work on X, Y, and Z because that's what we planned yesterday.

(10 Minutes into the day)

Boss: We need you to work on A, B, and C. These need to be done today.

Me: What about X, Y, and Z?

B: You have new priorities.

(30 Minutes later)

B: What's your status on X, Y and Z? You think it'll be done today?

M: (Forwards email about new priorities)

B: I'm coming down to talk with you.

WHY.

Not me but a coworker.

BA: How should we respond to business person's email?

Dev: Delete it.

Morning Deployment.

Me: Let's add this application to this server.

Deployer: Alright.

...

D: Done. Please verify.

Me: I'm seeing errors. Send me the logs.

D: Sure. I also updated the framework to a version that wasn't tested.

M: Yeah, that won't work. Roll it back.

D: Fine.

...

D: Done. Please verify.

M: All the applications on the box are broken. Please revert to the snapshot before the Deployment.

D: Oops, I didn't make one.

🙁😟😢😭😤

Business: We can't approve this code update in QA because we weren't aware of it.

Me: I was told you wanted it.

Business: We'll discuss it next week. Don't do anything on this till then.

Me: Alright. But you said so.

(Week passes)

Business: Why isn't that updated in QA for us to test? You said you were done.

Me: I am done but you said no. (Sends email exchange)

We shall see what happens next.

Making classes and functions without commenting what I expect each class and function to do. Which means that my classes and functions have really long names.

Example Code:
Class ReallySpecificClassToWorkWithThisFramework { ...

public void DoThisActionInTheFramework (obj TheKeyToTheWholeFunction) { ... }

}

So to test my server code that do calculations on large numbers that get above 10 digits 90% of the time.

The end users found a custom web page with basic javascript doing the calculations.

Now I get to explain why that doesn't work.

Leave my work at home. Play music and games to get away. Sleep and wake up with the solution.