Bartosz Bilicki > Bartosz's Quotes

Showing 1-30 of 77
« previous 1 3
sort by

  • #1
    Michael Ende
    “People never seemed to notice that, by saving time, they were losing something else. No one cared to admit that life was becoming ever poorer, bleaker and more monotonous. The ones who felt this most keenly were the children, because no one had time for them any more. But time is life itself, and life resides in the human heart. And the more people saved, the less they had.”
    Michael Ende, Momo
    tags: time

  • #2
    Michael Ende
    “...it's like this. Sometimes, when you've a very long street ahead of you, you think how terribly long it is and feel sure you'll never get it swept. And then you start to hurry. You work faster and faster and every time you look up there seems to be just as much left to sweep as before, and you try even harder, and you panic, and in the end you're out of breath and have to stop--and still the street stretches away in front of you. That's not the way to do it.

    You must never think of the whole street at once, understand? You must only concentrate on the next step, the next breath, the next stroke of the broom, and the next, and the next. Nothing else.

    That way you enjoy your work, which is important, because then you make a good job of it. And that's how it ought to be.

    And all at once, before you know it, you find you've swept the whole street clean, bit by bit. what's more, you aren't out of breath. That's important, too...”
    Michael Ende, Momo
    tags: zen

  • #3
    Robert C. Martin
    “It is not enough for code to work.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #4
    Michael C. Feathers
    “Code without tests is bad code. It doesn't matter how well written it is; it doesn't matter how pretty or object-oriented or well-encapsulated it is. With tests, we can change the behavior of our code quickly and verifiably. Without them, we really don't know if our code is getting better or worse.”
    Michael Feathers, Working Effectively with Legacy Code

  • #5
    Michael C. Feathers
    “Programming is the art of doing one thing at a time”
    Michael Feathers, Working Effectively with Legacy Code

  • #6
    Michael C. Feathers
    “Encapsulation is important, but the reason why it is important is more important. Encapsulation helps us reason about our code.”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #7
    Michael C. Feathers
    “To me, legacy code is simply code without tests.”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #8
    Michael C. Feathers
    “Tests that take too long to run end up not being run.”
    Michael Feathers, Working Effectively with Legacy Code

  • #9
    Michael C. Feathers
    “Encapsulation is a good thing, right? Well, don’t ask testers about that; they are liable to bite your head off. Classes that are too big often hide too much. Encapsulation is great when it helps us reason about our code and when we know that certain things can be changed only under certain circumstances. However, when we encapsulate too much, the stuff inside rots and festers. There isn’t any easy way to sense the effects of change, so people fall back on Edit and Pray (9) programming. At that point, either changes take far too long or the bug count increases. You have to pay for the lack of clarity somehow.”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #10
    Michael C. Feathers
    “How do I test private methods?” Many people spend a lot of time trying to figure out how to get around this problem, but, as I mentioned in an earlier chapter, the real answer is that if you have the urge to test a private method, the method shouldn’t be private; if making the method public bothers you, chances are, it is because it is part of a separate responsibility. It should be on another class.”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #11
    Michael C. Feathers
    “Big classes can hide too much. This question comes up over and over again from people new to unit testing: “How do I test private methods?” Many people spend a lot of time trying to figure out how to get around this problem, but, as I mentioned in an earlier chapter, the real answer is that if you have the urge to test a private method, the method shouldn’t be private; if making the method public bothers you, chances are, it is because it is part of a separate responsibility. It should be on another class.”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #12
    Michael C. Feathers
    “Over time, the system will get better as long as people aren’t introducing duplication behind your back. If they are, you can take steps with them short of physical violence, but that is another issue.”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #13
    Michael C. Feathers
    “Effective software change, like effective surgery, really involves deeper skills. Working with care doesn’t do much for you if you don’t use the right tools and techniques. Cover”
    Michael C. Feathers, Working Effectively with Legacy Code

  • #14
    Robert C. Martin
    “Truth can only be found in one place: the code.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #15
    Robert C. Martin
    “Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. ...[Therefore,] making it easy to read makes it easier to write.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #16
    Robert C. Martin
    “So if you want to go fast, if you want to get done quickly, if you want your code to be easy to write, make it easy to read.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #17
    Robert C. Martin
    “A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a long descriptive comment.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #18
    Robert C. Martin
    “Clean code is not written by following a set of rules. You don’t become a software craftsman by learning a list of heuristics. Professionalism and craftsmanship come from values that drive disciplines.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #19
    Robert C. Martin
    “You should name a variable using the same care with which you name a first-born child.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #20
    Robert C. Martin
    “It is not the language that makes programs appear simple. It is the programmer that make the language appear simple!”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #21
    Robert C. Martin
    “Of course bad code can be cleaned up. But it’s very expensive.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #22
    Robert C. Martin
    “Programmers must avoid leaving false clues that obscure the meaning of code.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #23
    Robert C. Martin
    “You are reading this book for two reasons. First, you are a programmer. Second, you want to be a better programmer. Good. We need better programmers.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #24
    Robert C. Martin
    “One difference between a smart programmer and a professional programmer is that
    the professional understands that clarity is king. Professionals use their powers for good and write code that others can understand.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #25
    Robert C. Martin
    “Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.
    - Grady Booch author of Object
    Oriented Analysis and Design with
    Applications”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #26
    Robert C. Martin
    “There are two parts to learning craftsmanship: knowledge and work. You must gain the knowledge of principles, patterns, practices, and heuristics that a craftsman knows, and you must also grind that knowledge into your fingers, eyes, and gut by working hard and
    practicing.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #27
    Robert C. Martin
    “If the discipline of requirements specification has taught us anything, it is that well-specified requirements are as formal as code and can act as executable tests of that code!”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #28
    Robert C. Martin
    “Redundant comments are just places to collect lies and misinformation.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #29
    Robert C. Martin
    “Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best.”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

  • #30
    Robert C. Martin
    “Code, without tests, is not clean. No matter how elegant it is, no matter how readable and accessible, if it hath not tests, it be unclean. Dave”
    Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship



Rss
« previous 1 3