4 ms·
I'm going to re-interpret the question more broadly than just "tools" (unless you consider a technique to be a kind of tool): * Taking good notes * Writing go
by piinbinary 6y ago
I'm going to re-interpret the question more broadly than just "tools" (unless you consider a technique to be a kind of tool):
* Taking good notes
* Writing good plans, good documentation
* Sharing updates and coordinating with the right people at the right time
* Understanding an unfamiliar codebase
* Test frameworks
* Different design techniques (pure functions, dataflow programming, etc)
* The terminal and related features (like emacs bindings, or middle-click to paste last selection)
* Firefox/Chrome devtools
* Emacs keyboard macros
- bob1029 6y agoI can no longer count on my fingers how many massive coding efforts from our backlog evaporated into nothing because we sat around and thoroughly talked through the actual business cases.
- smitty1e 6y agoSpacemacs! But also, writing the documentation as one works through the problem, either in org-mode, or in a wiki. The older I get, the less I remember, so the documentation is key.
- auslegung 6y agoI'd love to get better at quickly understanding an unfamiliar codebase. Do you have any resources I could dig into?