Some great comments here. Tangentially, I occasionally day dream of running or working for a company that flips typical corporate “intention” on its head – Specifically by placing employees at the highest place of priority and let profits, progress, customers, share price etc. be what they’ll be. I think that would be a very interesting experiment.

As far as how that relates to pay, part of the experiment would be to pay each employee more than they are “worth” to market. Just to see how it changes things for them and the company.

At the same time, “freeloaders” and folks that just can’t cut it would need to be identified and separated from, to protect those that recognize and appreciate that the company is truly looking out for them and are reciprocating with true hard work and value creation.

Ya this article was great. I wish I could convince my coworkers to take a deep dive into Git. I do it probably once a year and it’s helped me be the “hero” with confidence several times.

Git is exciting/interesting to me…it is not normal.

I just took a stab at git worktree at work this week after rereading this article. It’s amazing. We were in the process of upgrading our UI component library and I was able to checkout pre/post upgrade branches without having to continuously npm install to swap between dependencies.

Plus I’m pretty sure I could have both “versions” of our repo locally running at the same time so I could do UI comparisons…but I didn’t actually get that far.

I’m going to be honest. I like this thread. Not only is the article long and “thorough” (whether you agree with this form of thoroughness or not) but the responses are too.

I can appreciate what the author is trying to express. I also related to how he’s trying to express it because it’s very similar to how I try to explain my opinions, shower thoughts, meanderings…which typically earns me eyes glazing over from my conversation partners haha.

I have many many thoughts on everything being discussed here, but rather than contribute, I’m going to sip on my coffee and keep reading.

P.s. I’m liking PD better than Reddit. Actual conversation happening.

What did it for me is I stubbornly refused to use Git via VSCode and stuck with the terminal. I also stubbornly refused to change my default text editor for GIT to something other than VIM. One light bulb moment I had, funnily enough, was when I finally read the VIM docs and learned how to save and close rather than panicking when it popped up (this was early on… but not THAT early on … so still funny). That sparked my curiosity to truly learn VIM.

After that, I realized command line tools could be learned and advantageous and so it just went up from there.

Honestly, I’ve noticed a difference in the confidence level of peers using command line tools based on whether or not they learned GIT using command line or jumped straight to just clicking the buttons in VSCode.