I guess that’s implied in the command “on screen”

well I wouldn’t say great because your mobility is still a bit limited with a headset and it gets hot really fast. But, it’s a great way to gamify exercise and that works for many people

that’s ok facebook, you’re on many blacklists as well

We’ve actually taken that complex and valid system and clipped its wings to do something way less useful :')

that’s … way too pragmatic for a government project

well yes, but I don’t think it’s necessarily bad to go about it like you described, as long as you know that you’re not actually using the smaller issues to procrastinate on the big issues. Tackling the smaller issues first can help you to understand the bigger issues better, both consciously and subconsciously, so as long as it doesn’t actually matter in which order they’re done, I think it can be more effective to do the smaller ones first. That all goes out of the window of course if you’re using the small issues to avoid having to think about the bigger ones

I guess I don’t understand this obsession with speed?

for me it hasn’t been build speed but rather execution

I’ve run into problems with dayjs slowing down requests where I need to do a lot of processing. There are arguments to be made about replacing dayjs with datefns and how I should’ve been doing it differently anyway, but fact is that if the whole execution environment was twice as fast, it probably wouldn’t have been much of a problem at all

ᕕ( ᐛ )ᕗ

the mass tachyon flow sensor has been acting up again

I literally don’t know what TypeScript is

then perhaps you should learn about it before you offer your opinion

just substitute “fucking” and it works alright enough

We do what we must, because we can

there’s no way engine burn time is graduated in seconds on a spacecraft in 2023, that’s way too coarse