3 ms·
Basically you're paying for someone who has seen shit fail 42 different ways and has a pretty good feeling/knowledge what works in which case based on their exp
by theshrike79 4y ago
Basically you're paying for someone who has seen shit fail 42 different ways and has a pretty good feeling/knowledge what works in which case based on their experience. And they also know which solutions are overkill.
Simpler is always better, don't do stuff for your CV, build it so that you don't need to wake up at 3am on Christmas to fix some obscure deadlock issue.
Log stuff so that you can tell most of the time what went wrong just by looking at the logs and graphs.
But also be mindful of costs, logging everything to Cloudwatch can get surprisingly expensive.
Benchmarking is important, you can use the logs to see where you're actually spending time and optimise it if possible.
Sometimes the illusion of real-time is better than being real time. Everything that can be cached, should be cached. Utilise the TTL in Redis to make stuff simpler.
- lylejantzi3rd 4y agoOk, so how do I convince a prospective employer that I'm capable of these things? Well, except for seeing shit fail 42 different ways. We have a bit of a chicken and egg problem there. How can I have seen shit fail 42 different ways if I need to see shit fail 42 different ways to get the job?
- theshrike79 4y agoNot all games are 1M DAU, you can leverage knowledge of smaller games first. Only the biggest games with huge marketing budgets go from zero to 1M DAU in a day, so there's always the possibility of slowly improving the system while the player count grows.