Something don't look right. 🤔

Good:
Nothing.
Bad:
Fell into depression, didn't get out yet.

Best: Discovering devRant.
Worst: Spending too much time on devRant.

Best experience: working from home.
Worst experience: working from home.

Worst: work caused me to lose passion, be stressed/really close to burnt.

Best: I resigned

Worst: Uni called us back for offline exams in the middle of pandemic despite our attempts of thwarting it.

Best: Thankfully none of the people I know got infected and we got some time together before we graduate.

After three years of using docker, I can safely say "it just works" was a lie.

Is unlimited beer involved?

If not, probably the first thing would be a micro brewery.

Not gonna lie, I would keep procrastinating...

I would finish some of my many projects

A house.. or lego star destroyer..😝😆

Joke aside, I'd rewrite current project from scratch to get rid of all the automation and IE dependancies and make it cross browser and all the dead code...and all excess ORMs and especially EFCF..and also make support for db diff than oracle..and no need for ora client installation..

Yeah, I'm a work junky, I have no projects of my own.. one kid is demanding enough of my time.. 😉

"Pythonists don't comment, they write readable code."

Yea, tell that to the list comprehension with three lambdas

I wish my colleagues try to google first and then ask me.

Don’t work here.

I'm still a junior myself, but some fundamentals I've told my coworkers:
* Commit more, regret less
* Yes, you can remove a commit, if something goes wrong.
* No, I'll not explain again how to undo a commit you pushed typo to you feature branch. Feel the shame of pushing "Fix typo" commits
* ask, if you are stuck or unsure.
* don't do deployments at 5pm Friday. 6pm results in less crashes in production for some reason /s
* Don't be like me. Go to sleep at appropriate times

To anyone new to the corporate world I have this advice: there's a game no one tells you about in school or university. It's a game of politics. The good news is that you can choose not to play the game. The bad news is that others who do can change that decision for you, if you give them a reason to. So here's my tips to keep yourself from common bad situations:

* Some people will say they'd "prefer that people were honest". This is an outright lie.
* Be guarded - if a scenario could be taken out of context assume it will be.
* Mimic the office culture, don't try to rock the boat.
* Be polite, but always stay neutral between colleagues, picking a side means you're playing the game. Unless that side is your company vs another company in which case-- you are 100% on the company side and everyone else is stupid and incompetent.

Listen, before you talk...

There are no stupid or dumb questions. A lot of headache has been and could have been saved by one person asking what seemed like a stupid question.

I would now expand on this to say that if the question is procedural in the sense that it’s asking “what” or “how”, you should make every attempt to come to an answer yourself and then ask for clarification. If the question revolves around “why”, there are no stupid questions. A lot can be overlooked in a cascade of moving pieces.

Never take an advice from anyone if you did not specifically ask, this one included.

FUck you google with your falsy advertisement of unlimited photo storage shit

Colleagues sharing passwords.That was a big fat NO when I was a sysadmin - and for a good reason. But now, since I'm closer to development, it feels like no one really cares about the passwords. If I tell my colleague I'll take 10 minutes more because I can't log in, he OFFERS me his credentials. And sends them over saying "in case you need it". [the next day the same colleague was complaining his account is locked out. Oh, wonders! How on Earth...!]

But seriously, password sharing is a serious problem. I would fire the person on spot if I caught him sharing his credentials! This is the 8th deadly sin! IDC if they are for non-prod. Most people reuse their passwords in multiple systems, and even non-prod envs can bring the prod down! Or worse - install a trojan.

password.trim()

Going through git commit history to figure out when *the programmer fucked up this code.

* I am the only programmer.

Developers :
Work as efficient as possible!

Also developers :
Pressing the arrow up ⬆️ in the terminal 90 times to find a command that could have been manually typed out in 1 sec

There was a time in Windows 95, where during login, you could just press cancel and you were logged in without the need of a password.

Be skeptical of best practices. "Best" comes with assumptions, which may not apply to you.

Read the error message before closing it and/or asking for help.

Bring me some coffee.

Those people who don’t even understand the commit message

Who commits using commit message “commiting”?

Fuck you Android Studio. FUCK YOUU...