Vain Effort

Today's 3 Line Summary Try to decoupling between codes If you need to use external golbal data or static configuration wrap an API Try to write code around events TIL (Today I Learned) date 2022.03.26 The scope I read today Chapter 5 Bend, or Break What you want to remember in the book Topic 28. Decoupling Tell, Don’t Ask https://martinfowler.com/bliki/TellDontAsk.html Try not to have more than one “.” when you access something. There’s a big exception to the one-dot rule: the rule doesn’t apply if the things you’re chaining are really, really unlikely to change. Any mutable external resource is global data.the solution is to make sure you always wrap these resources behind code that you control. If It’s Important Enough to Be Global, Wrap It in an API Topic 29. Juggling the Real World But whatever their source, code that’s crafted around events can be more responsive and better decoupled than its more linear counterpart Top

Today's 3 Line Summary Don't trust evev yourself. When you think "that could never happen", check it if use resources, check to freed status when finish Always take small, deliberate steps, checking for feedback and adjusting before proceeding. TIL (Today I Learned) date 2022.03.24 The scope I read today Chapter 4 Pragmatic Paranoia What you want to remember in the book But Pragmatic Programmers take this a step further. They don’t trust themselves, either. Topic 23. Design by Contract Remember, if your contract indicates that you’ll acceptanything and promise the world in return, then you’ve got a lotof code to write! Topic 24. Dead Programs Tell No Lies Pragmatic Programmers tell themselves that if there is an error,something very, very bad has happened. A dead program normally does a lot less damage than a crippledone. Topic 25. Assertive Programming Whenever you find yourself thinking “but of course that could never happen,

Today's 3 Line Summary When you are write code, you should consider ETC and DRY, orthogonality There are no final decisions. you should prepare about reversibility The only way to determine the timetable for a project is by gaining experience on that same project TIL (Today I Learned) date 2022.03.21 The scope I read today 2.A Pragmatic Approach What you want to remember in the book Topic 8 The Essence of Good Design ETC:Easier to Change You may need to spend a week or so deliberately asking yourself “did the thing I just did make the overall system easier or harder to change?” Topic 9 DRY The Evils of Duplication Programmers are constantly in maintenance mode.maintenance is not a discrete activity, but a routine part of the entire development process. Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. DRY is about the duplication of knowledge, of intent. It’s about expressing the same

Today's 3 Line Summary It is your life. Software development skills are in demand in the world. You can change it if you have frustrated the job. You should be responsible for what you did. Don't blame others, don't excuse problems. Don't leave broken windows(bad designs, wrong decisions, or poorcode) Your knowledge becomes out of date. As the value of your knowledge declines, so does your value.You should keep learning. TIL (Today I Learned) date 2022.03.19 The scope I read today Foreword ~ 1.A Pragmatic Philosophy What you want to remember in the book you can change your organization or change your organization. Don’t blame someone or something else, or make up an excuse. but it is up to you to provide solutions, not excuses That’s the way it must be with software: don’t cause collateral damage just because there’s a crisis of some sort. Great software today is often preferable to the fantasy of perfect software tomorrow. Don’t spoil