3 ms·
As an old-ish guy who doesn't like people on my lawn, I agree with the sentiment. A big struggle when balancing how to use the knowledge gained over decades of
by weeksie 9y ago
As an old-ish guy who doesn't like people on my lawn, I agree with the sentiment.
A big struggle when balancing how to use the knowledge gained over decades of experience in today's context is trying to figure out which tools are needlessly complex and which bring real value to the table. What are the tradeoffs?
Makefiles aren't the glimmering beacon of simplicity I would lean on for an example but sure, they're less byzantine than webpack but you have to learn the syntax and other foibles along the way. Hell I used CMake back in the day when I was working on a big Lua/C/C++ app so that gives you an idea of my feels toward Make.
Far more common is the knee-jerk reflex to import a library for every damned thing. For stuff like a graphics library or mapping? Sure. Library for a data structure? Maybe? How much customization are you expecting to do to it? Will it work out of the box? Library for plumbing, like auto generating Redux action creators? Please don't do that. You're importing something that can probably be generalized for your case with a 10 line function.
- codazoda 9y agoI agree and I'll single out npm. It's a great tool but it must be used with event greater care. You can `npm install` a package and get dozens of packages requiring packages. Before you know it your little app has 100's of dependencies. On the flip side, I use `npm run` instead of writing simple bash scripts. Why? Because everyone I work with runs lots of things this way. Doing so ensure's they'll know where to look for all the stuff they might be able to run.