|
|
|
|
|
by alpanka
1680 days ago
|
|
That's the part I find most impressing. "Today we are going to add X" 2 hours later: X is added and working fine. Meanwhile, at work I could easily spend 2 hours looking for a GCC flag or figure out why the build script fails on arch after latest update |
|
Updating tools in your environment/workflow is exactly a thing that can lose a lot of time, often for not much gain[1]. One way to become very productive is to know your tools very well, and that would extend to not changing them often.
[1] not much gain in productivity, but perhaps in security, compatibility, etc