Game Programming Patterns Quotes

“Anytime “mushed” accurately describes your architecture, you likely have a problem.”
― Robert Nystrom, Game Programming Patterns

“Like so many things in software, MVC was invented by Smalltalkers in the seventies. Lispers probably claim they came up with it in the sixties but didn't bother writing it down.”
― Robert Nystrom, Game Programming Patterns

“You can define “decoupling” a bunch of ways, but I think if two pieces of code are coupled, it means you can’t understand one without understanding the other.”
― Robert Nystrom, Game Programming Patterns

“For me, good design means that when I make a change, it’s as if the entire program was crafted in anticipation of it.”
― Robert Nystrom, Game Programming Patterns

“Antoine de Saint-Exupery: “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”
― Robert Nystrom, Game Programming Patterns

“There is no right answer, just different flavors of wrong.”
― Robert Nystrom, Game Programming Patterns

“soapbox”
― Robert Nystrom, Game Programming Patterns

“You have to treat your codebase like a good camper does their campsite: always try to leave it a little better than you found it.”
― Robert Nystrom, Game Programming Patterns

“Making games may be fun, but it certainly ain’t easy. Modern games require enormous, complex codebases.”
― Robert Nystrom, Game Programming Patterns

“The reality was that the code I was looking at was written by people working to meet intense deadlines. They”
― Robert Nystrom, Game Programming Patterns

“Since hardware keeps getting better but our brainpower doesn’t, that trade-off starts to make more and more sense.”
― Robert Nystrom, Game Programming Patterns

“Like so many things in software, MVC was invented by Smalltalkers in the seventies. Lispers probably claim they came up with it in the sixties but didn’t bother writing it down.”
― Robert Nystrom, Game Programming Patterns

“Many people think “object-oriented programming” is synonymous with “classes”. Definitions of OOP tend to feel like credos of opposing religious denominations, but a fairly non-contentious take on it is that OOP lets you define “objects” which bundle data and code together. Compared to structured languages like C and functional languages like Scheme, the defining characteristic of OOP is that it tightly binds state and behavior together. You may think classes are the one and only way to do that, but a handful of guys including Dave Ungar and Randall Smith beg to differ. They created a language in the 80s called Self. While as OOP as can be, it has no classes.”
― Robert Nystrom, Game Programming Patterns

“If you’re worried about performance, at least profile first before changing your code to a less maintainable style.”
― Robert Nystrom, Game Programming Patterns

“Most non-programmers don't think of plaintext like that. To them, text files feel like filling in tax forms for an angry robotic auditor that yells at them if they forget a single semicolon.”
― Robert Nystrom, Game Programming Patterns

“The measure of a design is how easily it accommodates changes. With no changes, it’s a runner who never leaves the starting line.”
― Robert Nystrom, Game Programming Patterns