Coding Quotes

“Programming isn't about what you know; it's about what you can figure out.”
― Chris Pine

“Think twice, code once.”
― Waseem Latif

“Rebellion and accidents have caused a majority of the advancements we enjoy on a daily basis. Thank goodness for defiance and randomness!”
― Linda Armstrong, Mission: Subhero

“The coding was anachronistic, kind of like bokeh in a renaissance painting.”
― Sorin Suciu, The Scriptlings

“Happiness should be a function without any parameters.”
― Pranshu Midha

“I bet you’re wondering why they are on the ground. When they can be outside, even for a little bit, it calms them down for days afterward. It’s the connection between humans and mother earth. It’s nice to be in contact with Mom.”
― Linda Armstrong, Mission: Subhero

“Don’t just download the latest app, help redesign it. Don’t just play on your phone, program it.”
― Barrack Obama

“Coding like poetry should be short and concise.”
― Santosh Kalwar

“At X-Feer, we teach how to solve problems not how to write a code because that's the most important thing in coding.”
― Ahmed Abu Taha

“There's a high that you get when you're writing code. It's cool. It's easy to do. You forget your mom, your dad, everything. You've got the whole country onboard. This is America. You hit the frontier. You can go anywhere. It's about being connected, access, gateways, like a whispering game where if you get one thing wrong you've got to go all the way back to the beginning.”
― Colum McCann, Let the Great World Spin

“Tom Demarco, a principal of the Atlantic Systems Guild team of consultants ... and his colleague Timothy Lister devised a study called the Coding War Games. The purpose of the games was to identify the characteristics of the best and worst computer programmers; more than six hundred developers from ninety-two different companies participated. Each designed, coded, and tested a program, working in his normal office space during business hours. Each participant was also assigned a partner from the same company. The partners worked separately, however, without any communication, a feature of the games that turned out to be critical.

When the results came in, they revealed an enormous performance gap. The best outperformed the worst by a 10:1 ratio. The top programmers were also about 2.5 times better than the median. When DeMarco and Lister tried to figure out what accounted for this astonishing range, the factors that you'd think would matter — such as years of experience, salary, even the time spent completing the work — had little correlation to outcome. Programmers with 10 years' experience did no better than those with two years. The half who performed above the median earned less than 10 percent more than the half below — even though they were almost twice as good. The programmers who turned in "zero-defect" work took slightly less, not more, time to complete the exercise than those who made mistakes.

It was a mystery with one intriguing clue: programmers from the same companies performed at more or less the same level, even though they hadn't worked together. That's because top performers overwhelmingly worked for companies that gave their workers the most privacy, personal space, control over their physical environments, and freedom from interruption. Sixty-two percent of the best performers said that their workspace was acceptably private, compared to only 19 percent of the worst performers; 76 percent of the worst performers but only 38 percent of the top performers said that people often interrupted them needlessly.”
― Susan Cain, Quiet: The Power of Introverts in a World That Can't Stop Talking

“It appears evident that, for the average team, insisting on writing tests first, before functional coding, improves quality.”
― David J. Anderson, Kanban: Successful Evolutionary Change for Your Technology Business

“The thing about Web companies is there's always something severely fucked-up. There is always an outage, always lost data, always compromised customer information, always a server going offline. You work with these clugey internal tools and patch together work-arounds to compensate for the half-assed, rushed development, and after a while the fucked-upness of the whole enterprise becomes the status quo. VPs insecure that they're not as in touch as they need to be with conditions on the ground insert themselves into projects midstream and you get serious scope creep. You present to the world this image that you're a buttoned-down tech company with everything in its right place but once you're on the other side of the firewall it looks like triage time in an emergency room, 24/7. Systems break down, laptops go into the blue screen of death, developers miskey a line of code, error messages appear that mean absolutely nothing. The instantaneousness with which you can fix stuff creates a culture that works by the seat of its pants. I swear the whole Web was built by virtue of developers fixing one mistake after another, constantly forced to compensate for the bugginess of their code.”
― Ryan Boudinot, Blueprints of the Afterlife

“Coding is other type of magic!”
― Deyth Banger

“When you decide to put your business online it is a little bet tricky step for novice computer users because they want to keep data safe & secure.
This problem developed from companies which did not take security seriously”
― Mohamed Saad

“Also, don't forget that some of the most successful people in the world are self-taught programmers. Steve Wozniak, the founder of Apple, is a self-taught programmer. So is Margaret Hamilton, who received the Presidential Medal of Freedom for her work on NASA's Apollo Moon missions; David Karp, founder of Tumblr; Jack Dorsey, founder of Twitter; and Kevin Systrom, founder of Instagram.”
― Cory Althoff, The Self-Taught Programmer: The Definitive Guide to Programming Professionally

“Most improved things can be improved.”
― Mokokoma Mokhonoana

“The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs.”
― Maurice Wilkes, Memoirs of a Computer Pioneer

“Procedural code (code using data structures) makes it easy to add new functions without changing the existing data structures. OO code, on the other hand, makes it easy to add new classes without changing existing functions.”
― Robert C. Martin

“The complement is also true: Procedural code makes it hard to add new data structures because all the functions must change. OO code makes it hard to add new functions because all the classes must change.”
― Robert C. Martin

“Coding is Love & Coding is Life.”
― Biswabijaya Samal

“Coding is Love & Coding is Life”
― Biswabijaya Samal

“AI is the transformer of civilization.”
― Toba Beta

“If a machine ever gains awareness, it will be not due to our careful programming, but due to an unforeseeable anomaly.”
― Abhijit Naskar, The Gospel of Technology

“The only way to make sure that you don't lose your job with the arrival of AI, is to do something that AI cannot do, and the only thing that artificial intelligence cannot do but a human can, is being original. So, do something original and no AI can ever replace you.”
― Abhijit Naskar

“Every machine has artificial intelligence. And the more advanced a machine gets, the more advanced artificial intelligence gets as well. But, a machine cannot feel what it is doing. It only follows instructions - our instructions - instructions of the humans. So, artificial intelligence will not destroy the world. Our irresponsibility will destroy the world.”
― Abhijit Naskar

“People are funny. The longer you are around them, the more you start to realize that everyone makes the same motions over and over again. We all want to believe that every day is different, that every day we change, but really, it seems that certain things are coded into us from the very beginning”
― Jasmine Warga, My Heart and Other Black Holes