26 ms·

- git. Not just commit/push/pull on a single branch - but getting really good at using git is a game-changer. - vim. I started off in linux sysadmin land befor

- git. Not just commit/push/pull on a single branch - but getting really good at using git is a game-changer. - vim. I started off in linux sysadmin land before pivoting into more regular software engineering work, so I was very good as basic vi(m) stuff because it's ubiquitous in linux/unix servers. However I've learned its just as valuable as a full-blown IDE/dev environment if you're willing to invest in learning and configuring it. I think newer editors like Atom/VSCode/IntelliJ are still very valuable and great tools, but Vim really is incredible. - An understanding of unix history. Maybe it's just the type of work I do, but knowing why things are the way they are is incredidbly valuable.

rovr138 6y ago
Regarding understanding unix history. I actually think that knowing the history of whatever you're working with, is good and really valuable. If you don't know the history, you don't know how things came to be and why things are the way they are. This applies to language, code, product, organization, tools, etc. You can treat things like a blackbox and use them. They'll work for a while but every time you see something that doesn't work, you'll spend time and more time trying to figure things out. Do/Learn things once. Ask questions. Sit with people that know. Ask smart questions - http://catb.org/~esr/faqs/smart-questions.html http://catb.org/~esr/faqs/smart-questions.html I've been using git for years. But I decided to really dig into it to find out how things work. These are good links and there are actually many more good ones about git internals out there. - https://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2 - https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco... - https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Po...

rovr138 6y ago

Regarding understanding unix history. I actually think that knowing the history of whatever you're working with, is good and really valuable. If you don't know the history, you don't know how things came to be and why things are the way they are. This applies to language, code, product, organization, tools, etc. You can treat things like a blackbox and use them. They'll work for a while but every time you see something that doesn't work, you'll spend time and more time trying to figure things out. Do/Learn things once. Ask questions. Sit with people that know. Ask smart questions - http://catb.org/~esr/faqs/smart-questions.html http://catb.org/~esr/faqs/smart-questions.html I've been using git for years. But I decided to really dig into it to find out how things work. These are good links and there are actually many more good ones about git internals out there. - https://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2 - https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco... - https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Po...