73 von 84 Kunden fanden die folgende Rezension hilfreich
Disappointing: Shallow and Old School,
Verifizierter Kauf(Was ist das?)
Rezension bezieht sich auf: The Pragmatic Programmer. From Journeyman to Master (Taschenbuch)
As most other reviewers, I was drawn in by the glowing commentaries here on Amazon.
As background, I've been programming professionally for nine years now, on a variety of projects, but generally high-performance embedded stuff. I'm interested in improving my software development & management skills, and have read a number of other, better books (listed later) about these topics.
My first criticism is that the collection of 50-odd tips are simply too shallowly presented to be very interesting. Generally, if you agree, you say, "yeah, duh," and if you don't, there's no discussion of the point, and no attempt to address known difficulties with "good" practices. There also seemed to be no attempt to balance some of the points. For example, the authors repeatedly talk about writing your code so it's flexible. In general, a good idea. On the other hand, they really seem to think you should be writing everything, regardless of what sort of application it is, to run on different machines, under different operating systems, with and without concurrency, etc. This, to me, just seems foolish, extra work, extra code, extra bugs. The estimates I've seen (in other, better, books) say that just writing re-usable code takes three times more work than "normal" code, ignoring multi-platform complexities.
The old school comment (and I consider myself fairly old school) is there because they very obviously come from a Unix/command line environment. I will admit, they motivated me to improve my scripting skills, something I've been planning on doing for a while. But then they have inane advice, like "use only one editor *for everything*". This is perhaps nice, if you can, but on larger projects or organizations, this probably isn't possible. I use the IDE required by the project, a different editor for documentation (also required) and a third one for doing hex & advanced search and replace. Perhaps with emacs and 47 scripts this wouldn't be necessary, but I'm not convinced it would be efficient either.
All in all, the advice is generally good, but I think there are better books out there (e.g. Code Complete, Writing Solid Code, Rapid Development, The Mythical Man-Month, C++ Coding Standards). As a light book to get you thinking about your craft, it's not bad, but that's the best I can say about it.
Sortieren: Ältester zuerst | Neuester zuerst
1-3 von 3 Diskussionsbeiträgen
Ersteintrag: 21.08.2009 20:54:27 GMT+02:00
hans-peter mueller meint:
Veröffentlicht am 21.02.2010 20:36:16 GMT+01:00
Amazon Customer meint:
Very good recension. I agree with every point.
Veröffentlicht am 25.02.2015 15:35:53 GMT+01:00
Zuletzt vom Autor geändert am 25.02.2015 15:36:14 GMT+01:00
The idea behind the "one editor for everything" is that you shouldn't have to juggle several editor's shortcuts and configurations around in your mind and on your disk. I don't know about "Emacs and 47 scripts", but I can conveniently do everything, from source (Bash Perl C C++ Java C# Python...) over documentation (LaTeX doxygen docbook...) to hex / binary, in either Vim / GVim, or UltraEdit if Vim is too oldschool for you. I think the underlying message here is, if your editor isn't up to the task, ditch it and find a better one...
‹ Zurück 1 Weiter ›