Why do we need a "programmer's perspective"? Exercise has nothing to do with programming or engineering specifically. Exercise (ideally, some form of exercise that strengthens muscles that atrophy while sitting) should be a thing for everyone who sits behind for 40+ hours a week.
You're overthinking it. It's a "programmer's perspective" because the author is a programmer. There isn't anything more to it, and as far as I can tell there's no insinuation that it is particularly special.
A cleaner walking 5 hours a day, and a programmer sitting 8 hours a day: that's 2 different perspectives to exercising.
Actually all forms of sports are always a personal perspective. Why ? Because we are all unique biologically and psychologically.
Your own perspective to sports changes over age and other factors (sickness, weight, private life ...etc). That's why you won't run 15 km tomorrow the way you did today.
Actually that’s a common misconception too - you will not get fit from having a physical job like cleaning you will just be tired. So I really appreciate that I can exercise both the brain at work and muscles at the gym. I see some people in the gym who do physical work or night shifts and it’s much harder for them to manage fatigue immunity and make gains (you need proper rest time to rejuvenate).
most people who sit at the desk don't have hours at a time sitting all tensed up and in a bad position because stuff is not going well and they get hyperfocused on running the code again and again, not that that happens often - but sometimes.
Its worse, they have to sit there using the half arsed buggy software that some programmer shat out in order to get promoted to L5 in the 2021 summer of CV driven development and hasn't been updated or fixed since.
I've used half-assed buggy software before, I've worked for the government and cases had to be logged, also I've worked as a data entry worker - and of course I live in Denmark, one of the most digitized countries in the world, where the government gets away with making you use the solutions they had developed with awful UX that - really, one time I got fined 5000 dollars and had a company closed down because I thought what a program was telling me was an obvious bug - but it wasn't - when I complained to the workers and the ministry that required this solution be used they said "Oh yeah, everyone has that problem"
In short I have used just as buggy crappy software as anyone, and I'm a programmer who has been hyperfocused for a day in all sorts of uncomfortable positions, for bonus points I have also worked intense physical labor in jobs where people died, just in case someone was going to play the manual labor card.
I have as yet encountered nothing worse than programming when it is going very badly. When it's going easy it's a piece of cake of course.
You might disagree, but the most important skill of a programmer is problem-solving skills/mindset and a rational approach. A programmer's perspective of many things will be different than the average person perspective that doesn't use those skills to make decisions.
He even wrote about that if you had the time to read the article before commenting:
As a software engineer I though, If I should "pick boring tech", maybe I should also "pick boring sports". So I decided to pick something boring. Something old, 1000s of years old. My rationale being that for older sports there would be more easily available knowledge, failure modes would be better known, and I would be able to better understand if I was doing it wrong.
Well, it might be useful because programmers are likely to spend even more time in front of a screen than the average person, and thus examples from other programmers might encourage them to exercise more. Other who sit for work find computers a necessary evil and prefer to do other things instead of working with them.
well we people just do all kind of stuff and that stuff never ends.. we feel like just few minutes but the reality is the time keep ticking and our eyes just stick to screens... and at that moment we dont even think about the health and body .
you’re more likely to click through if it applies to you “I usually don’t care about strength training but I am a programmer so this interests me! Let’s click through”
Which is much easier than fiddling around with crontab, in my experience.
Yes, you need a systemd service file and a systemd timer file. Creating both is a matter of ~30m. Then, you do `systemctl start` and you're good... As a great benefit, you can see the status of each timer, which is great for debugging quick problems, like permission issues/runtime errors/... when setting the timer up.
Well, it takes 30m the first time, when learning from scratch. When learning the arcane cron entry system, I'd guess it takes even longer than 30m, unless you have a simple time in mind (like "every minute" or something similar - "every second Monday" is definitely more complex to reason about in cron). Again, comparing not knowing systemd timer vs not knowing cron.
Sure, not saying you can just sit down and do it straight away. But the additional complexity of systemd, I think, makes it even more daunting. It’s much like how modern frontend has a million components. I understand there are or were reasons for all of it, but not everyone needs it, and it’s intimidating to a newcomer.
In comparison, cron (and *nix tooling in general) asks you to learn a small bit of that tool’s syntax, and that’s it. You can add complexity if you’d like – read the man pages – but for the most part, you can be productive very quickly.
> Regardless what’s going on, have at least one day per week when I don’t work at all (usually Saturday) and never pull all-nighters (no work after midnight);
Why are you working during the weekend and after work hours?
I've never used Ubuntu, but on Fedora and openSUSE Tumbleweed, I've never run into this issue (and I've had like 50+ tabs open for weeks since i don't really reboot my work laptop unless I have to)
Given a million years, I'd say the human race ending is more likely than the human race figuring out how to run Bloodborne 4 on a Steam Deck, given that in a couple years, Steam Deck 2 will outperform the original SD.
Amazing. This made me want to play BB on my old PS4 that's gathering dust. Then, I remembered it's 30FPS locked, and has pretty bad loading times. I'll wait for the emulator, or a remaster, whatever comes first I guess :))
Apparently someone made it run at 60fps on a PS5 devkit, and it's frustrating because I actually have access to one but there are no instructions anywhere so I can't experience the beauty of Bloodborne in 60fps :-(
The PS4 Pro struggles to run this game at 60fps due to a CPU bottleneck. On the other hand, PS5 runs it remarkably stably at 60fps and even 120fps is decent.
Don't worry, I think it's only a matter of time before you'll be able to do this. Either through an official PS5 remaster, an official PC release (less likely) or via some funky unofficial emulation.
Even though it's only 30fps the game is quite beautiful for being 9 years old and running on a previous gen console.
it is something to worry about if you care about playing the original. I'm only interested in straight ports with minimal QOL features like 60fps(or unlocked if viable), higher resolution and controller rebinding.
I haven't played a single remaster that I preferred to the original game. I'm fine with remasters existing, but only if faithful ports are made available as well.
Those are remakes and not remasters. Different beast.
The trouble with remasters is they're usually farmed out to third-party devs who don't always give it the same attention to detail as the original developers. A prime example would be Dark Souls Remastered, which actually makes some of the graphics worse compared to the original PC version.
The line between remaster and remake is a blurry one.
Nier Replicant ver.1.22... isn't officially called either a remake or a remaster, and a convincing case could be made for either. Yet it changes more than Demon's Souls PS5 does.
It is easy to find criticism of Demon's Souls' remaster's art style by entering that term into your favourite search engine. This isn't "considered" true by "almost everybody".
Regardless of any person's opinion on the changes, being substantially different is enough reason that it isn't a suitable substitute for the original.
Lance McDonald (@manfightdragon) is the someone, I don't think the patch is shared publicly though. He plays it sometimes on his Twitch channel. I've seen LobosJr play the 60 fps version too.
Not sure whether you know about it or not, so: you have to do a little bit of work, but it _does_ run in 4k on PCs. Do some googling, you'll find all you need.
> the writers don't want to repeat themselves because they were taught that it's "poor writing."
Yes! As you say, it massively depends on whether you are writing fiction or non-fiction. In any sort of formal document, especially technical reports, etc, the reader should never have to spend time working out what the author means. I used to be a doc reviewer in a previous life, and lost count of the number of times docs used different terms to mean the same thing, especially where multiple authors were involved, or a single author was writing different sections at different times.
General plea: If you value your readers, please, please get someone else to check a doc to look for these sorts of problems. If multiple authors are involved, always get someone on the team (a lead author?) to do this check even before submitting it for formal review.
Many 'rules' including this one can be broken if you know the tradeoffs and can make the case-by-case choices correctly. But that was a poor example for motivating a behaviour.
reply