Vain Effort

Today's 3 Line Summary Version Control, Regression Testing, Full Automation Our goal as developers is to delight users. Pragmatic Programmers don’t shirk from responsibility. TIL (Today I Learned) date 2022.04.05 The scope I read today Chapter 9 Pragmatic Projects What you want to remember in the book 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 helppeople 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 proje

Today's 3 Line Summary Requirements rarely lie on the surface, so you should try to produce mockups and prototypes for customers or become a client. When faced with an intractable problem, enumerate all the possible avenues you have before you. sometimes it is useful to do something different. The agile team should experiment continuously, and need a good design for easy change. TIL (Today I Learned) date 2022.04.03 The scope I read today Chapter 8 Before the Project What you want to remember in the book Topic 45. The Requirements Pit Requirements rarely lie on the surface. Normally, they’re buried deep beneath layers of assumptions, misconceptions, and politics. Even worse, often they don’t really exist at all. In those cases, Pragmatic Programmers rely on the “is this what you meant?” school of feedback.We produce mockups and prototypes, and let the client play with them. There’s a simple technique for getting inside your clients’ heads that isn’t used

Today's 3 Line Summary Don't write code by Coincidence. Don’t assume it, prove and try it. Write test code, when you write code. Try to Unit test,Property-Based Test Whenever you create a name, you need to think of the reason. TIL (Today I Learned) date 2022.04.01~02 The scope I read today Chapter 7 While You Are Coding What you want to remember in the book Coding is not mechanical. There are decisions to be made every minute—decisions that require careful thought and judgment if the resulting program is to enjoy a long, accurate, and productive life. Topic 37. Listen to Your Lizard Brain First, stop what you’re doing. Make doodles about the code you’re writing, or explain it to a coworker (preferably one who isn’t a programmer), or to your rubber duck Write “I’m prototyping” on a sticky note, and stick it on the side ofyour screen. Topic 38. Programming by Coincidence As developers, we also work in minefields. There are hundreds of traps

Today's 3 Line Summary Concurrency is a requirement in our system Try to use transaction,semaphores for concurrency issue Consider to use Actor for concurrency without shared state TIL (Today I Learned) date 2022.03.30 The scope I read today Chapter 6 Concurrency What you want to remember in the book Topic 33. Breaking Temporal Coupling Activity diagrams show the potential areas of concurrency, but have nothing to say about whether these areas are worth exploiting. Remember the distinction: concurrency is a software mechanism, and parallelism is a hardware concern. Topic 34. Shared State Is Incorrect State A semaphore is simply a thing that only one person can own at a time. You can create a semaphore and then use it to control access to some other resource. The current design is poor because it delegates responsibility for protecting access to the pie case to the people who use it. Let’s change it to centralize that control. This caused the buil