jchnxu

People don't pay you for your (team's) code, people pay you to solve their problems

Learn to listen & talk to your manager

Learn to listen & talk to your user

Learn to be a bad cop, stay away or even fire those who negatively impact the team ASAP

I'm not writing to you, I'm writing to myself :p

No.

For library usage, yes.

When I want the code, yes.

For everything else, no, never impact my decision.

dark reader heavy user here haha

I feel that actually we are on the same page.

patterns as a concept for communication are helpful.

But I mean for people coding in in python & js creating singletons are overkill right?

Agree. And I feel like some patterns emerged from the limitations of programming laguauages Java & C++ which does not apply to languages like python/js. I mean when you can use lambdas/high order functions a lot of those patterns does not even make senses. Not to mention those pure functional programming languages.

My 2 cents,

If I need to push a project I'd really love to work face to face, it takes me 5 min to spot the problem or to slip in a conversation easily. Or even just observing what's happening is fun and educating.

But in large corps I understand the dilemma, even if you go to the office your job is to hop in remote meetings, that sucks. Then the office might just be cancelled.

do you just literally ask that or rephrase the question to "what are the expectations for me"? I mean sometimes what keep the VP up at night is not sth relevant to or disclosable to you.

I have read about the journey of Figma and actually watched their CEO's early video call and their CTO's github WebGL demos. It's an amazing 5yrs