For a large team project, I was working on the website. I implemented a log-in page that took me a bit of time since it was my first time.
He grade that process poorly saying he has seen log-in pages all the time and it was nothing new or exciting...
YOU ARE A PROFESSOR FOR AN INTRO CLASS! YOUR JOB IS TO LOOK AT THE EXACT SAME THING EVERY SEMESTER, SHITHEAD.

I started teaching myself AngularJS and was reminded how difficult it is to distinguish between a person's convention and proper implantation.
For example (pseudo-code):
angular.module(). controller(){}
or
var app = ang.mod()
app.controller(){}
I get it now, but figuring out the difference at first was an extra step that I found tedious.

Really... "Investigate the reason" and try again. Bruh.

I wish senior people would just admit if they don't know something or are unsure. I hate spending time implementing a feature and spending more time troubleshooting it only to ask for help and be questioned why I'm "doing it like that" in the first place...
YOU TOLD ME THIS IS HOW IT IS DONE!!!

Some Devs need to be better about sharing info. Like, I don't want to play 20Qs just to learn how to configure a system I never used. You have job security, don't worry! Other people are allowed to know what ya know; you don't need to impress anyone!

I think this is appropriate for this week's topic.

When a manager asks if you can implement a feature (their are legitimately not sure if it is even possible) and you say yes and they say, "Good, 'cause I already assured the client that we would provide it on the next release"
Like, what the actual fuck...

Work with PLCs and similar controllers. If there is an issue that cannot be found in a relative amount of time, just turn it off and back on. "Power cycle" is oh to common with my coworkers and actually works too often for my liking.

UGH! Wasting time explaining to the client why you are not adding information/functionality to a page since a separate software will do it all (and better than what you would do).