• Title: The Pragmatic Programmer: From Journeyman to Master
  • Author: Andy Hunt Dave Thomas
  • ISBN: 9780201616224
  • Page: 300
  • Format: Paperback
  • The Pragmatic Programmer From Journeyman to Master Ward Cunningham Straight from the programming trenches The Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core proces
    Ward Cunningham Straight from the programming trenches, The Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core process taking a requirement and producing working, maintainable code that delights its users It covers topics ranging from personal responsibility and career development to ar Ward Cunningham Straight from the programming trenches, The Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core process taking a requirement and producing working, maintainable code that delights its users It covers topics ranging from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse Read this book, and youll learn how to Fight software rot Avoid the trap of duplicating knowledge Write flexible, dynamic, and adaptable code Avoid programming by coincidence Bullet proof your code with contracts, assertions, and exceptions Capture real requirements Test ruthlessly and effectively Delight your users Build teams of pragmatic programmers and Make your developments precise with automation Written as a series of self contained sections and filled with entertaining anecdotes, thoughtful examples, and interesting analogies, The Pragmatic Programmer illustrates the best practices and major pitfalls of many different aspects of software development Whether youre a new coder, an experienced programm

    One Reply to “The Pragmatic Programmer: From Journeyman to Master”

    1. This is essentially a self-help guide for programmers, the kind of book that enumerates the habits of Good and Happy People and makes you feel slightly guilty about not practicing most of them, but probably won't result in you forsaking your evil ways and stepping on the path toward Nirvana. Hunt and Thomas are friendly but occasionally annoying gurus. Their cloying metaphors (boiled frogs, etc) and kitsch jokes are offputting, and some of their advice borders on insult. One assumes that when th [...]

    2. I no longer have any need for mentors or friends now that I have AVClub (the AVQ&A and "Gateways to Geekery" columns in particular), Quora, and Stack Overflow.Case in point: That I found this book. Over the past couple of years I have been gradually writing and less-gradually maintaining a code base for separate projects. It's getting the point where I might as well figure out what the hell I'm doing. So I go to Stack Overflow and find my way to a question like "What programming book do you [...]

    3. While many complain about already knowing everything in the book, or that it's outdated, I believe they are quite missing the point. Perhaps this book didn't speak to you at the point you are at in developing your skills and crafts, but it might speak to someone else just beginning. Rating the book low for the reason it wasn't what you needed is rather disingenuous, as a rating should be a guide to the quality of the book overall. The information contained in this book is essential for software [...]

    4. (4.0) Good for new programmersThis seems to be a favorite in the office, so before I participating in the recommending of this book to new hires, I figured I should check it out first. There is definitely some good stuff in here, but most won't be new for anyone who's been programming professionally for 2 or 3 years or more. I think most engineers' problems is that they don't do what they know is the right thing.I think many people have said this before, but at the risk of duplication I'll say t [...]

    5. For a total beginner, the concepts will be difficult to internalize. For a seasoned programmer (on a good team), it will be little more than a general reinforcement. While it's hard to imagine the right time in one's career to read the The Pragmatic Programmer (probably, often), it's a classic. It's written at a high enough level that very little material is outdated- in fact some of the arguments ring much truer now than they would have in 1999.

    6. This is my favorite non-technical tech book. It explores good software development practices. In my opinion it is more than just a checklist of what you should do - it literally changed my approach to development with positive results.Others have mentionned that they already knew most of the things in this book, and practice these good habits in their development environments. I've worked in dozens of environments ranging from very successful experienced companies, to fly-by-night operations tha [...]

    7. Эту книгу нужно ОБЯЗАТЕЛЬНО прочитать КАЖДОМУ студенту, который учится на специальностях, связанных с ИТ. Причём лучше прочитать уже на втором-третьем курсе, чтобы студенты не только знали языки программирования и алгоритмы, но и принципы разработки, чтобы они понимали, ч [...]

    8. In fact, it's a good book if you're just beginning to program. I've just read it late, so it contains nothing new to me. I can't imagine that there are software developers who don't know about practices described in this book. Besides, it's already outdated (RCS? Really?).As to Russian edition of this book, it's translated very badly, it's almost unreadable.

    9. I didn't like the structure of the book. Some of the concepts were vaguely presented. I was also bored a little bit while reading it.Some notesChapter 1. A Pragmatic PhilosophyTip 3: Provide Options, Don't Make Lame ExcusesBefore you approach anyone to tell them why something can't be done, is late, or is broken, stop and re-evaluateTip 4: Don't Live with Broken WindowsDon't leave "broken windows" (bad designs, wrong decisions, or poor code) un-repairedTip 5: Be a Catalyst for ChangeStart with s [...]

    10. Who is this book for?Certainly not for experienced, skilled software developers. Considering myself at least experienced, I found most of the material in this book a rehash of methodologies and techniques I've used for more than a decade. Granted, there were a few gems here and there, but mostly I was bored because I didn't learn anything new.One has to respect that this book is from 1999, so in that perspective, it must have been quite ground-breaking. Had I read it in 1999, I wouldn't have kno [...]

    11. I enjoyed the pragmatic programmer. Still I found myself skipping sections, especially where I felt the subjects discussed I already had a good grip on. Other parts just felt dated, like the sections on source control and "modular code" in the age of distributed git, npm and microservices. I would definitely recommend this to programmers looking to up their game. The advice this book gives for you to become a better programmer is solid, and you'll find yourself agreeing with it. You should espec [...]

    12. The beautiful thing about a book like The Pragmatic Programmer is that it sparks ideas when you read it. Can you do something more efficiently? Can you do it more elegantly? Can you make the computer do the work instead?I like to think that I already ask myself those questions all the time. Nevertheless, I found myself reading a page or two and then having to stop because I was having a great idea and needed to write it down. I filled six sheets of letter-size paper with dense, cryptic notes. Th [...]

    13. I don't think I can gush enough about this book. It's the kind of thing I unconsciously resist reading because I know of all the guilty feelings it could provoke. Well, one thing I can tell you is that it's not like that at all. Oh actually, yes it is. The first chapter starts off gently reminding you that you should be constantly learning new things, for example, a new programming language every year (not necessarily because you want to have mastery of that language, but because it's good to ke [...]

    14. The Pragmatic Programmer is centered on good programming practices. It is very well written and is able to persuade you to want to change your habits and behavior. I intend on re-reading this book on a regular basis (anually, perhaps) because there is certainly a learning and adaptation curve to all the techniques that are introduced. Although I do use some of them on my day-to-day work, it's very difficult to start using every single tip at once, so I'll introduce them gradually on my working f [...]

    15. This is probably my favorite book about technology. Full of great and timeless advice for anyone working on the field; written by one of my biggest inspirations in programming, master Dave Thomas.It's more philosophical than technical which makes it a nice and easy read.The book is not written in linear way so whenever you need inspiration, you can just open it in a random page and get charged up. Reason why I have a hard copy with me.I've read it twice already and I will probably read it again. [...]

    16. A great non technical book that goes into codifying the good practices about software development. It is a must read for neophytes in software industry with a couple of years of experience. If you have worked or are working in a good team and good project, you can easily relate back and forth about the goof things that are talked about.It is simple to read, still relevant in 2016 and is worth investing couple of weeks to read this if you are aspiring to be a pragmatic programmer.

    17. Terrific book. Great thing explained in the most pragmatic way possible. Due to its usage of metaphors, easy-to-read language, it read like a breeze. I might have forgotten some of the great stuff in it, might actually reread it soon.

    18. This was a great book for programmers to read. It had a lot of very general, yet very useful advice for programmers. I loved the broken window theory of programming. Malcolm Gladwell argues the same theory cured New York's crime wave in the 90's inBlink

    19. A very insightful read. I look at my projects differently after reading this. It doesn't focus on a particular language, but rather teaches principles.

    20. Not great. This book aged really weirdly and it explains itself when you realize theres a bullet pointed list in the back that they probably just created fluff around.There are a whole bunch of stand out weird suggestions the book has, but I think my major problem with it is that it rambles back and forth into light level technical things and sort of wastes time there. That and the section about how source control is good. And that weird section on how oh my god u just gotta know all the keyboar [...]

    21. If you are a programmer, get this book. This is the best book I've read on how to be a good, professional programmer.From 's review:Programmers are craftspeople trained to use a certain set of tools (editors, object managers, version trackers) to generate a certain kind of product (programs) that will operate in some environment (operating systems on hardware assemblies). Like any other craft, computer programming has spawned a body of wisdom, most of which isn't taught at universities or in cer [...]

    22. This book is a real kick-in-the-pants for computer programmers. No matter where you are on the technology curve, this book will give you great insight into developing your craft.The premise of the book is that software development is a craft. The subtitle of the book is, "From journeyman to master", which evokes the traditional pathway a person learned to ply a craft. An apprentice would sit at the feet of a master and learn the secrets of the trade.Computer programming, though, is often a solit [...]

    23. When I was about 100 pages into this book, I felt two things:1) I know this stuff2) This is good stuffI recommended it to a few junior engineers on my team as a result.Having finished the book, I see it as a product of its time. Dotcom had not happened yet. Ward's wiki was "an interesting experiment in collective editing of ideas". Refactoring was barely going to press. The version control section recommends you install CVS at home. Into this cold winter came a snowball, which in this book is ph [...]

    24. I used to teach a course from this book. Well, not entirely from this book, but mostly from it. Despite it not being designed as a textbook, it's eminently suitable as one. I often think, looking back at this experience, that textbooks should *really* be written in lecture-size chunks, not in huge chapters like most are. The book provides somewhat of a "tour de force" through sane programming practices. It slightly predates the eXtreme Programming craze, but elements of agile development are cle [...]

    25. If you're going to be a solid, productive programmer, what are the ground rules? What are the basic "do"s and "don't"s?They're all here.Basic stuff like:Don't Repeat Yourself, which states that, if you find the some piece of code in more than one place, refactor it so the duplicated code is in a function, procedure or template. If you have to modify the code, either for adding functionality or for fixing a bug, you will have only one place where you need to edit it. Otherwise, if there are multi [...]

    26. First of all I want to say that Russian translation is terrible, I strongly advise every russian speaker who thought about reading the translation - to read the original.The book itself is obviously somewhat outdated but in general really great set of techniques and approaches that will allow you to become a better software engineer.The techniques described here partially became a foundation for agile software development methodologies, as I see it. One other great thing about this book is that [...]

    27. This book makes me both excited to become a software engineer and to learn all of the things in order to become a good one (which, it turns out, is a lot). It's the perfect combination of high-level tips and low-level recommendations (which I assume are now out of print, but should point me toward newer alternatives), and its style is fantastic. The authors present their advice in a rational way which made it attractive for me to try and assimilate the advice into my work without becoming overwh [...]

    28. The authors propose their philosophy of software development, some of which can be applied to life in general. So the DRY principle- Don't Repeat Yourself says that if any information exists in more than one place, then inevitably, when it is updated, it won't be updated everywhere it is found. So the key is to make sure that all information exists in just one location, and that anything that needs the information obtains it from that location, so that updates are propagated automatically. This [...]

    Leave a Reply

    Your email address will not be published. Required fields are marked *