ℍ𝕂-𝟞𝟝

  • 0 Posts
  • 45 Comments
Joined 2 months ago
cake
Cake day: July 14th, 2024

help-circle






  • Jobs disappeared, most people got other jobs, some better, most worse and the unluckiest starved.

    What happened is that people started to stay longer in school, agricultural labour withered, and with it, kids having to work the fields at a very young age. People became more educated, resulting in more democratic societies, more equality, and a higher standard of living.

    This was not because of the machine looms and steam engines, but because greedy fucks used them to put people in a position where they had no choice but to push back, and that labour action created unions, five-day work weeks, 8-hour days, paid time off for sickness and leisure, and pretty much everything we take for granted.









  • Despite what others are saying, I think you are right in a lot of ways.

    There definitely is a set point where your body feels comfortable. You can get above and below a few kilos, and your body will return to that set point if you return to what you eat normally. That’s why it’s hard, to move the set point, you have to get around 5 under and keep at it. So when you are 5 under and your weight loss suddenly stops, that’s when you really started to push the kilos down, that’s why it suddenly gets harder. And you should go that 5 kilos past your set point because you will gain it back when you stop eating less.

    With me, with a resting consumption of around 1800 kcal, how it went is that I did 6 months of trying to keep it below 1500 kcal, targeting 1400 if I can - but no less, and more or less kept it. My results have been going from 124 kg to 110 then rebounding to 114, then another round of doing the same got me from 114 to 100 then rebound to 104. After the ~4 kg rebound, it stabilized. Just now, a month after finishing, I just ate nothing but shitty McDonalds for 3 days (have been on the road a lot) and my weight went from 104.2 to 103.9.

    I guess what I’m saying is that your only real way of affecting the system is cals in vs cals out, but as you say, the inside of the system is not simple. Also, don’t crash diet, and even if you feel like eating less on one day for some reason, keep your diet from the other side as well. Every time I ate less than 1400, the next day I fucked it up and went to 1800-ish, every single time. It makes it much harder.




  • To be honest, I’ve seen a lot of code in my line of work, and my experience says that if the speed of a language is your concern, you’re either in high-frequency trading or working on some real-time use case, or you’re wrong.

    Most time you perceive as lag as a user comes from either atrocious programming, or network lag, or a combination of the two. A decently, not even well, but decently written Python vs Assembly subroutine will have differences in execution time measured in nanoseconds. Network calls usually measure in milliseconds, and something like a badly written DB query that reads a ton of data from a disk will do seconds or worse.

    My point is, I’ll take a not-badly written Python program over someone claiming to have chosen C/C++ for the blazing fast speed in a user facing application, when half of CVEs ever have been submitted over memory safety problems in C/C++.