Pinned
A brief intro to Clean Code Second Edition
a.co/d/h81TOYL
00:00
Uncle Bob Martin
44.5K posts
Uncle Bob Martin
@unclebobmartin
Software Craftsman
- Never ask permission to refactor. Never ask permission to write tests. You do these things because you KNOW they are the best way to go fast. When you ask permission, you are asking someone else to take responsibility for your actions.
- Replying to @theoSQL was never intended to be used by computer programs. It was a console language for printing reports. Embedding it into programs was one of the gravest errors of our industry.
- Agile is not a way to go fast. It is a way to know where you are going. Agile is does not increase productivity. Agile increases manageability. Agile does not guarantee you’ll get there on time. Agile destroys the hope that you might, when you won’t.
- The word “refactoring” should never appear in a schedule. Refactoring is not a story or a backlog item. Refactoring is not a scheduled task. Refactoring is immediate and continuous. It’s like washing your hands in the bathroom. You always do it.
- Most programmers want to write good code; but believe that their employers don’t want good code. They are wrong. Most employers want the benefits of good code; but don’t know that good code provides those benefits. We do. So, we should write good code.
- We need a new law. No AI should ever use a first person pronoun. This is because no AI is a person. Pretending to be a person is a very, very bad idea for a computer program. Especially an AI.
- It is more important for code to be changeable than that it work. Code that does not work, but that is easy to change, can be made to work with minimum effort. Code that works but that is hard to change will soon not work and be hard to get working again.
