Hard disagree. In fact, learning how to apply clean code and architectural patterns in game dev has kept projects manageable and on track and done nothing but level up my general software ability.
You can do the above in C#, I haven't written Java in a decade so can't comment on that. I don't really understand your argument though - the options approach is extremely readable. You can also do the options approach in C or C++. The amount of stuff that you can slap into one line is an interesting benchmark to use for languages.
This is a philosophy, or "opinion", and should not be confused with truth. If the world was 100% evil people and beings, across all of history, forever, the present would look very different than it does now. And none of us know what the future holds.
Interesting. When I do not feel up to the task of working, whether it is a physical, mental, emotional, spiritual, or arbitrary cause, I use one of my provided PTO days and email the team a short "I will not be showing up to work today" message, without explaining the cause.
I similarly don't bat an eye when a coworker takes off for whatever reason. We're allotted PTO. Why jump through hoops to convince ourselves that it's ok to use it?
I don’t even use a PTO day if I’m just feeling “blah” as long as I’m available via Slack to answer questions and can attend ad-hoc meetings. There are so many times I’ve had to/chosen to work late, I don’t say anything.
I don’t think I’ve taken a “sick day” once since going remote over 5 years ago. But for the last 10 years I’ve been leading initiatives first at startups and then at consulting companies and I mostly have autonomy and the trust to get things done.
It's because the GP doesn't value you as a person or trust you. In that worldview, you cannot allow any autonomy and all time not spent at work must be tightly regulated. It will also spill in other areas, and you can bet the GP is not well liked by their colleagues.
This looks interesting. Maybe I'm not in-the-know, but why would you offload such important aspects like `sync` to the client instead of building in some protocol to ensure that file integrity is maintained? With this kind of design choice, it seems quite easy to lose data, unless I'm missing something.
For a game I'm making, I have a helper function that takes in a specified time (as a float) and returns a (heap based) wait instruction. The times are literals sprinkled throughout the code base of callers of this function, so I maintain a cache of time -> wait instruction to reduce allocations.
Wouldn't your life be much simplier if you'd represented time as integer milliseconds? I totally get it being too late now, but I think that's an argument for making floats a little bit unpleasant to start working with.
In that case and in some others it doesn’t, but in general it does:
https://stackoverflow.com/questions/17661428/async-stay-on-t...
Probably it makes sense to say that async await can try to use a continuation passing style or run on a different thread because there is no actual guarantee that it will use one or the other.
Hard disagree. In fact, learning how to apply clean code and architectural patterns in game dev has kept projects manageable and on track and done nothing but level up my general software ability.