오늘 TIL 3줄 요약

• Version Control, Regression Testing, Full Automation

• Our goal as developers is to delight users.

• Pragmatic Programmers don’t shirk responsibility.

TIL (Today I Learned) 날짜

2022.04.05

오늘 읽은 범위

Chapter 9 Pragmatic Projects

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

Topic 49. Pragmatic Teams

• Teams as a whole should not tolerate broken windows—those small imperfections that no one fixes.

• Don’t adopt new tech, frameworks, or libraries just because “everyone is doing it,” or based on something you saw at a conference or read online.

• Good communication is key to avoiding these problems.

• Automation is an essential component of every project team.

Topic 50. Coconuts Don't Cut It

• The purpose of a software development methodology is to help people work together.

• But as with any goal, the key is to keep aiming in the right direction.

Topic 51. Pragmatic Starter Kit

• And that’s the important part: at the project level, version control drives the build and release process

• We use fine, mall nets (unit tests) to catch the minnows, and big, coarse nets (integration tests) to catch the killer sharks.

• In fact, a good project may well have more test code than production code. The time it takes to produce this test code is worth the effort.

• Because we can’t write perfect software, it follows that we can’t write perfect test software either. We need to test the tests.

• Once a human tester finds a bug, it should be the last time a human tester finds that bug.

• People just aren’t as repeatable as computers are. Nor should we expect them to be.

Topic 52. Delight Your Users

• Our goal as developers is to delight users. That’s why we’re here.

• Even though your title might be some variation of “Software Developer” or “Software Engineer,” in truth it should be “Problem Solver.” That’s what we do, and that’s the essence of a Pragmatic Programmer.

Topic 53. Pride and Prejudice

• Pragmatic Programmers don’t shirk from responsibility. Instead, we rejoice in accepting challenges and in making our expertise well known. If we are responsible for a design, or a piece of code, we do a job we can be proud of.

• “I wrote this, and I stand behind my work.” Your signature should come to be recognized as an indicator of quality.

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

• The last chapter was about the practical programmer's mindset and a summary of previous chapters

• The phrase "Pragmatic Programmers don't shirk responsibility" is particularly memorable. I look back on whether I have taken responsibility for my work.

• I'm finished!