Developers Quotes

“He liked to start sentences with okay, so. It was a habit he had picked up from the engineers. He thought it made him sound smarter, thought it made him sound like them, those code jockeys, standing by the coffee machine, talking faster than he could think, talking not so much in sentences as in data structures, dense clumps of logic with the occasional inside joke. He liked to stand near them, pretending to stir sugar into his coffee, listening in on them as if they were speaking a different language. A language of knowing something, a language of being an expert at something. A language of being something more than an hourly unit.”
― Charles Yu, Sorry Please Thank You

“For you, it’s all about money, money, money. But what about the forests I say? Some of those trees have been there for hundreds of years. What right have you to destroy that?”
― Emily Arden, Lie to me

“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

“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

“Programmers and software engineers who dive into code without writing a spec tend to think they're cool gunslingers, shooting from the hip. They're not. They are terribly unproductive. They write bad code and produce shoddy software, and they threaten their projects by taking giant risks which are completely uncalled for.”
― Joel Spolsky, Joel on Software

“Google-ing is a skill that should be put on CVs.

Some developers are simply faster at finding accurate answers on Google.”
― Pooria Arab

“Bugs are sometimes the mess we create, Raphael created a bug when he forgot to tidy up his toys.”
― Iria Osara, Teach Toddlers Tech: Debugging

“As for the hedgerows, the law required the developers to commission a hedgerow survey; it found that single hedgerows on the site contained up to eight tree species. An approximate rule of thumb known as Hooper's Rule states that the age of an English hedgerow can be estimated by counting the number of woody tree species growing along a thirty-yard stretch and multiplying that number by 110. This suggests that some of the hedges could have been part of the landscape since well before the first mention of an orchid in English. Neither the survey nor the developer's Environmental Impact Statement noted this.”
― Ben Jacob, The Orchid Outlaw: On a Mission to Save Britain's Rarest Flowers

“If I am crazy... what are the Developers of Lufia?”
― Sino Melo