Mustafa Berkay Mutlu > Mustafa's Quotes

“Bir silgi gibi tükendim ben
Başkalarının yaptıklarını silmeye çalıştım
Mürekkeple yazmışlar oysa..
Ben kurşunkalem silgisiydim
Azaldığımla kaldım..”
― Oğuz Atay, Tutunamayanlar

“Kötü bir resim asarım korkusuyla hiç resim asmadım, kötü yaşarım korkusuyla hiç yaşamadım.”
― Oğuz Atay, Tutunamayanlar

“The decisions of our past are the architects of our present.”
― Dan Brown, Inferno

“We can destroy what we have written, but we cannot unwrite it.”
― Anthony Burgess, A Clockwork Orange

“Niçin rüzgarlı sonbahar akşamlarında, sessizce yan yana yürüyerek ruhlarımızın konuştuğunu dinleyemiyoruz?”
― Sabahattin Ali, Kürk Mantolu Madonna

“As Gregor Samsa awoke one morning from uneasy dreams he found himself transformed in his bed into a gigantic insect.”
― Franz Kafka, The Metamorphosis

“I cannot make you understand. I cannot make anyone understand what is happening inside me. I cannot even explain it to myself.”
― Franz Kafka, The Metamorphosis

“When I was a kid I was constantly being told to look at things from someone else’s point of view. What this always meant in practice was to do what someone else wanted, instead of what I wanted. This of course gave empathy a bad name, and I made a point of not cultivating it. Boy, was I wrong. It turns out that looking at things from other people’s point of view is practically the secret of success. Empathy doesn’t necessarily mean being self-sacrificing. Far from it. Understanding how someone else sees things doesn’t imply that you’ll act in his interest; in some situations — in war, for example — you want to do exactly the opposite.”
― Paul Graham, Hackers & Painters: Big Ideas from the Computer Age

“Architecting for the enterprise, when all you really need is a cute little desktop tool, is a recipe for failure.”
― Robert C. Martin, Clean Architecture: A Craftsman's Guide to Software Structure and Design

“The intelligent investor realizes that stocks become more risky, not less, as their prices rise—and less risky, not more, as their prices fall. The intelligent investor dreads a bull market, since it makes stocks more costly to buy. And conversely (so long as you keep enough cash on hand to meet your spending needs), you should welcome a bear market, since it puts stocks back on sale. 8”
― Benjamin Graham, The Intelligent Investor

“The intelligent investor is a realist who sells to optimists and buys from pessimists.”
― Benjamin Graham, The Intelligent Investor

“But investing isn’t about beating others at their game. It’s about controlling yourself at your own game.”
― Benjamin Graham, The Intelligent Investor

“invest only if you would be comfortable owning a stock even if you had no way of knowing its daily share price.3”
― Benjamin Graham, The Intelligent Investor

“But note this important fact: The true investor scarcely ever is forced to sell his shares, and at all other times he is free to disregard the current price quotation. He need pay attention to it and act upon it only to the extent that it suits his book, and no more.* Thus the investor who permits himself to be stampeded or unduly worried by unjustified market declines in his holdings is perversely transforming his basic advantage into a basic disadvantage. That man would be better off if his stocks had no market quotation at all, for he would then be spared the mental anguish caused him by other persons’ mistakes of judgment.”
― Benjamin Graham, The Intelligent Investor

“There is no such thing as quick and dirty. Anything dirty is slow. The only way to go fast, is to go well.”
― Robert C. Martin, Clean Agile: Back to Basics

“Some folks think that Agile is about going fast. It’s not. It’s never been about going fast. Agile is about knowing, as early as possible, just how screwed we are. The reason we want to know this as early as possible is so that we can manage the situation. You see, this is what managers do. Managers manage software projects by gathering data and then making the best decisions they can based on that data. Agile produces data. Agile produces lots of data. Managers use that data to drive the project to the best possible outcome.”
― Robert C. Martin, Clean Agile: Back to Basics

“Agile is a process wherein a project is subdivided into iterations. The output of each iteration is measured and used to continuously evaluate the schedule. Features are implemented in the order of business value so that the most valuable things are implemented first. Quality is kept as high as possible. The schedule is primarily managed by manipulating scope.”
― Robert C. Martin, Clean Agile: Back to Basics

“Ideas are easy. Implementation is hard.”
― Guy Kawasaki

“it’s not the external voice that will break you down. It’s what you tell yourself that matters. The most important conversations you’ll ever have are the ones you’ll have with yourself. You wake up with them, you walk around with them, you go to bed with them, and eventually you act on them. Whether they be good or bad.”
― David Goggins, Can't Hurt Me: Master Your Mind and Defy the Odds

“Whatever failures and accomplishments pile up in the years to come, and there will be plenty of both I’m sure, I know I’ll continue to give it my all and set goals that seem impossible to most. And when those motherfuckers say so, I’ll look them dead in the eye and respond with one simple question. What if?”
― David Goggins, Can't Hurt Me: Master Your Mind and Defy the Odds

“Early in my career as a manager at Google, the time came for me to hand out bonus letters to my team, and I grinned as I told my manager, “I love being a manager!” Without missing a beat, my manager, a long-time industry veteran, replied, “Sometimes you get to be the tooth fairy, other times you have to be the dentist.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time

“Google’s Site Reliability Engineering (SRE) team has a motto: “Hope is not a strategy.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time

“At Google, we often attach “freshness dates” to documentation. Such documents note the last time a document was reviewed, and metadata in the documentation set will send email reminders when the document hasn’t been touched in, for example, three months.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time

“the ideal test is unchanging: after it’s written, it never needs to change unless the requirements of the system under test change.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time

“When an engineer refactors the internals of a system without modifying its interface, whether for performance, clarity, or any other reason, the system’s tests shouldn’t need to change. The role of tests in this case is to ensure that the refactoring didn’t change the system’s behavior. Tests that need to be changed during a refactoring indicate that either the change is affecting the system’s behavior and isn’t a pure refactoring, or that the tests were not written at an appropriate level of abstraction.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time

“Fixing a bug is much like adding a new feature: the presence of the bug suggests that a case was missing from the initial test suite, and the bug fix should include that missing test case.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time

“Fakes Should Be Tested A fake must have its own tests to ensure that it conforms to the API of its corresponding real implementation. A fake without tests might initially provide realistic behavior, but without tests, this behavior can diverge over time as the real implementation evolves.”
― Titus Winters, Software Engineering at Google: Lessons Learned from Programming Over Time