DAY 2

🔖 오늘 읽은 범위 : 시작 ~ Foreword, Preface, cp1 Stone Soup and Boiled Frogs

<aside> 😃 책에서 기억하고 싶은 내용을 써보세요.

</aside>

• What makes a pragmatic programmer?
  • Early Adopter/fast adapter. You have an instinct for technologies and techniques, and you love trying things out.
  • Inquisitive. You tend to ask questions.
  • Critical thinker. You rarely take things as given without first getting the facts.
  • Realistic. You try to understand the underlying nature of each problem you face.
  • Jack of all trades. You try hard to be familiar with a broad range of technologies and environments, and you work to keep abreast of new developments.
• Care About Your Craft We feel that there is no point in developing software unless you care about doing it well.
• Think! About Your Work In order to be a Pragmatic Programmer, we’re challenging you to 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.
• Within the overall structure of a project there is always room for individuality and craftsmanship.
• Every day, work to refine the skills you have and to add new tools to your repertoire. Unlike the Elton lawns, you’ll start seeing results in a matter of days.
• The Cat Ate My Source Code A Pragmatic Programmer takes charge of his or her own career, and isn’t afraid to admit ignorance or error. This means being honest and direct. We an be proud of our abilities, but we must be honest about our shortcomings—our ignorance as well as our mistakes. Provide Options, Don’t make Lame Excuses. Instead of excuses, provide options. Don’t say it an’t be done; explain what can be done to salvage the situation.
• Be a Catalyst for Change
• Don’t be like the frog. Keep an eye on the big picture. Constantly review what’s happening around you, not just what you personally are doing.
• A good idea is an orphan without effective communication.
• WISDOM acrostic
  • What do you want them to learn? What is their interest in what you’ve got to say?
  • How sophisticated are they? How much detail do they want?
  • Whom do you want to own the information? How can you motivate them to listen to you?

<aside> 🤔 오늘 읽은 소감은? 떠오르는 생각을 가볍게 적어보세요

</aside>

My mentor has told me to be a π(pi) type programmer who has knowledge/experience for a broad range of technologies and is specialized in 2 things. This advice is something I keep in mind.

<aside> 🔎 궁금한 내용이 있거나, 잘 이해되지 않는 내용이 있다면 적어보세요.

</aside>