DEV Community 👩‍💻👨‍💻

Cover image for The pragmatic programmer book tips (Part 1)
Wassim Ben Jdida
Wassim Ben Jdida

Posted on • Updated on

The pragmatic programmer book tips (Part 1)

3 weeks ago I bought The pragmatic programmer book, I saw it on a blog and the writer really recommended it, so I said why not.

the book is full of great tips, actually each section the book talks about, ends with a tip its like a summary of the section.

the book has about 70 tip, this is part 1. I will list them and explain some of the ones that are not clear, the explanation is from the book itself.

#1 - Care About Your Craft

There is no point in developing software unless you care about doing it well.
 

#2 - Think! About Your Work

think about what you're doing while you're doing it. Never run on auto-pilot. Constantly be thinking, critiquing your work in real time.
 

#3 - Provide Options, Don't Make Lame Excuses

don't have a backup, it's your fault. Telling your boss "the cat ate my source code" just won't cut it.
 

#4 - Don't Live with Broken Windows

Don't leave "broken windows" (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered. If there is insufficient time to fix it properly, then board it up. Perhaps you can comment out the offending code, or display a "Not Implemented" message, or substitute dummy data instead.
 

#5 - Be a Catalyst for Change

You may be in a situation where you know exactly what needs doing and how to do it. The entire system just appears before your eyes you know it's right. But ask permission to tackle the whole thing and you'll be met with delays and blank stares. People find it easier to join an ongoing success. Show them a glimpse of the future and you'll get them to rally around.
"It's easier to ask forgiveness than it is to get permission."
 

#6 - Remember the Big Picture

Keep an eye on the big picture. Constantly review what's happening around you, not just what you personally are doing.
 

#7 - Make Quality a Requirements Issue

 

#8 - Invest Regularly in Your Knowledge Portfolio

Learn at least one new language every year. Read a technical book each quarter. Read nontechnical books, too. Look for interesting courses. Participate in local user groups, Isolation can be deadly to your career. Experiment with different environments. Stay current. Surf the Web for papers, commercial sites, and any other sources of information you can find.

It's important to continue investing. Once you feel comfortable with some new language or bit of technology, move on. Learn another one
 

#9 - Critically Analyze What You Read and Hear

Just because a bookstore features a book prominently doesn't mean it's a good book, or even popular; they may have been paid to place it there
 
 
 

Part 2 will be ready soon

Top comments (0)

👋 Every week new members join DEV and share a bit about them in our Welcome Thread

 
Welcome them to DEV and share a bit about yourself