[DiscordArchive] Isn't it more like, make sure you aren't writing stupid code for stuff you don't need?
[DiscordArchive] Isn't it more like, make sure you aren't writing stupid code for stuff you don't need?
Archived author: vblanco • Posted: 2022-06-20T19:19:40.851000+00:00
Original source
actual micro-optimization can be done later once you can bench, but seleting the proper structures and data flow is critical
Archived author: Nix • Posted: 2022-06-20T19:19:54.148000+00:00
Original source
Like IHM mentioned, it is very common to despite understanding the requirements to write the right thing first try
Archived author: Nix • Posted: 2022-06-20T19:20:05.544000+00:00
Original source
but at the very least it'll be closer to what you want, and as you just mentioned then you can optimize further later
Archived author: vblanco • Posted: 2022-06-20T19:21:05.808000+00:00
Original source
i do believe that in the context of DBs, thinking it super properly from the start is critical. After all migrating stuff is a bit of a pain
Archived author: vblanco • Posted: 2022-06-20T19:21:19.363000+00:00
Original source
and the data model of the DB means your game data model is different
Archived author: Nix • Posted: 2022-06-20T19:22:11.612000+00:00
Original source
For sure, but it is very unlikely for you to model even that perfectly, but giving good effort from the start is important
Archived author: vblanco • Posted: 2022-06-20T19:22:27.744000+00:00
Original source
i once saw an indie team who had an atrociously hacky data model for quests and save states, and they were like halfway through development and *couldnt save their game*
Archived author: vblanco • Posted: 2022-06-20T19:22:29.101000+00:00
Original source
like lmao
Archived author: Nix • Posted: 2022-06-20T19:22:46.896000+00:00
Original source
<:KEKW:666849321462792234>
Archived author: vblanco • Posted: 2022-06-20T19:22:48.823000+00:00
Original source
plus it was a mess of the highest order to create quests and crosslink them or check them in tools