Don’t blame your cat, talk to your duck (includes chapter 1 The Pragmatic Programmer | from journeyman to master)

--Originally published at Alfonso reviews…

To be a pragmatic programmer you need to approach problems keeping an eye on the big picture, we don’t always have to create the best software, but sometimes we have to, also, sometimes we need to adapt to the changes, but that’s not always the case, the point that I’m trying to get here is that there is no static solution to all of your problems, use your criteria so you can get to a good solution.

When you make mistakes or you don’t know how to do something, speak, offer options and learn, and don’t blame others for your mistakes, be responsible. And if the need comes, talk to your rubber duck and explain it your situation, maybe the rubber duck will give you the same answer your boss would give you, and you just saved your boss from that.

When someone makes a mistake, and it’s ignored, the tendency states that more mistakes will come, even when it’s not code, a bad decision or design can also wreck a project into tiny pieces. Code follows the law of entropy, so beware and clean your mess, and keep an eye on other’s mess, see if you can help.

This two topics were part of the first chapter of the book, but I was surprised to find the stone soup story, as a reference to what I think is incremental delivery, many times people won’t give away what you need to develop a big project, unless of course you convince them you can do the thing by showing them well done mini deliveries, then you can ask for more, and deliver even more. But as stated at the start of the chapter, keep in mind the big picture, or the original idea of the project will fade away and you

Continue reading "Don’t blame your cat, talk to your duck (includes chapter 1 The Pragmatic Programmer | from journeyman to master)"

How pragmatic are you?, introduction

--Originally published at Alfonso reviews…

This post is an introduction for “The Pragmatic Programmer” from Andrew Hunt and David Thomas, and the authors said it’s intended for people who want to become more effective and productive programmers. For people who want to do, they stated that this isn’t a theoretical book, but a practical one, a way to gain experience and productivity, a way to write better software.

Authors also said that this book will help you become a pragmatic programmer, and that if you become one, you will probably gain the following characteristics, you’ll become:

  • An early adopter/fast adapter so you’ll enjoy trying new technologies to apply them in the future.
  • Very inquisitive, asking questions about how everything works.
  • Critical, you won’t take things for granted, you’ll wonder if things can be done differently than stated.
  • Realistic, if a problem is hard, you will notice, and won’t lose determination in spite of that.
  • Comfortable with many technologies, even when you don’t need them at the moment.

I thought I needed to be more confident with new technologies, so I challenged myself to read this book.

Will you accept the challenge as well?