Too Many Tools and Frameworks (2015)

Re:Too Many Tools and Frameworks (2015) by JustSomeNobody on Tuesday October 04, 2016 @10:49AM (#12635953)

Interesting, but you're pretty spot on. Personally this has caused me great angst[0] as I tend to write the absolute minimum amount of code necessary to solve the exact problem I'm trying to solve.

I tend to wait until I've solved a problem in similar ways three[1] or so times before I generalize it.

[0] Because other developers want to solve for a more general problem. [1] Three is such a comfortable number, isn't it?

[ Parent | on HN ]

Re:Too Many Tools and Frameworks (2015) by crasm on Tuesday October 04, 2016 @04:53PM (#12639381)

I've noticed I tend to work in three passes, although not necessarily three tries.

First is an over-abstracted mess that may or not work before it eventually collapses. Brainstorming.

Second is a rewrite aiming for compactness, that could end up impossible for anyone else to understand.

Third pulls just the right amount of abstraction out of the terseness of the second pass.

I treat it like a feedback driven control-system. Too much abstraction? Dial it down. Not enough abstraction? Dial it up. Repeat until good enough.

If I stop at 1 or 2, the code is poor. If I don't oscillate, it takes more passes.

[ Parent | on HN ]