News for hackers. Stuff that matters.
Re:Evidence-based Software Engineering: based on the publicl... by derefr on Tuesday May 25, 2021 @02:11PM (#27280226)
I'd love to read a book that teaches concepts "in anger" — where you're given a big problem statement with lots of subproblems; and then, in each chapter, the author:

• introduces a subproblem, that would be solvable but for one tool you're currently missing;

• introduces the tool you'll need to solve the subproblem;

• explains the tool in the process of using the tool to solve the subproblem. Only explaining as much of the tool as is necessary to solve the subproblem — more can be explained in later subproblems.

Sadly, I find that most books like this first introduce all the tools you'll need; teach them all thoroughly (including teaching stuff you won't need at all, because it's part of the explanation as traditionally taught); and then go about solving all of the subproblems using all of the tools, in a pretty random order. So the first half ends up boring, and the second half ends up messy and hard-to-follow.

There are no comments on this comment yet.