An hour meeting about the purpose of this meeting.
Meta.

Sorry boss, I can't work today, fucking Intellij is indexing again.

my neighbors should upgrade their wifi.

it too slow.

It's nice wanting to follow the best practice but many Java programmer have the bad habit to overdo it making lasagna code which causes painful headaches to who needs to maintain it afterwards. This is just a little sample of the "paranoia driven development" many does in my company.

In the future, Linux will be written in Rust and called Windows.

What if I told you..

..the //TODO comment you just added to your code will never get done?

Apologies if this has been asked here before, but I wanted an open feedback on a query: Is there such a thing as overdocumenting?

I take pride in being a very articulate developer, being as descriptive as possible in my emails, internal communications, PR review comments, JIRA etc.

A product guy from the company today mentioned: "Though I understand your good intent behind being as descriptive as possible, it is possible that some of the junior engineers might get overwhelmed/ intimidated looking at those comments/ emails and it might stop them reaching out to you with your doubts."

I was not able to wrap my head around this, because I don't understand how a descriptive explanation might overwhelm anyone. It's a skill I picked up going through my career and I personally have always respected peers who documented things properly.

Open to feedback. Thank you in advance.

the one who knocks

… I need a drink.