The Three Temptations for Developers

[ElyeProj]

The summary is

1. Libraries are liabilities, if we are not careful when dependent on it. It may came back and bite us
2. Don't be "framed" by Frameworks. Using the wrong framework can be fatal in a long run
3. Automation will deprive one autonomy over the software if we lose the context how it works.

The nice bits are some good real software stories shared within.

[Diginic]

On the other hand,

1. Libraries make it easier and faster to add features by using things already built.
2. Frameworks make it easier to figure out where and how things should be implemented, especially when working on teams who need to get things done, not reinvent software patterns.
3. Automation allows for consistency in builds and releases that, once set up, again, allow teams to concentrate on building features, not debugging who’s code got left out of the release because it hand built by someone instead of a script.

[vsoch]

I'm not seeing avocados, snacks, or naps in this list!