Edit: Really enjoy threads like this, because you learn and see so many Pov.
My favourite answer (not in this thread unfortunately) was:
*”If you write a story, the number of words you use can affect the reader’s experience.*
*Use too many words, and the reader takes a long time to get through the book, has difficulty remembering everything, and can’t separate what’s important and what’s not.*
*But use too few words and the reader will get an incomplete picture, make mistakes in understanding the story, and eventually become disinvested in the book.*
*A poorly optimized game is like one of these examples. Either too much goes in, making it difficult for the hardware to cope, or not enough goes in, making the game buggy and broken. (Sometimes both, but that’s beyond ELI5).*
*When it comes to optimising a reader’s experience, it is not about putting more or less words in but choosing the right combination of the right words at the correct time in the plot. Optimising a game is similar concept.*
*Most importantly, no matter how well you write a book, there are always people who will think it could’ve been written better, especially by them. “*
In: 404
I had a trial at a game company in Germany with zero in the name who were working on a game based on a certain top model TV show. They asked me to work on some code written by the lead dev. This was PS2 code and my job was to make.it more memory efficient.
The code is in question was putting clothes on the models. I looked at the code and took out the bit that did the work and saw that it only used 1kb. I was fresh out of uni and had absolutely no idea how to reduce that memory usage further. I realised then that console development was not for me. The optimisation required for a console with limited memory is crazy compared to pc games. Needless to say my trial was cut short.
Latest Answers