Achievement unlocked: body weight (80kg) deep squat 🏋️✌️
Achievement unlocked: body weight (80kg) deep squat 🏋️✌️
Open Source Software and publications by Christian Kruse
This page contains random thoughts and impressions by me.
Achievement unlocked: body weight (80kg) deep squat 🏋️✌️
OH: „Coffee so black it has an event horizon”
It's ridiculous that we are not able to make a disruption free phone call on a train in 2017. Call gets cancelled every few km…
Deadlift went up to 90kg at 3x12 (up from 60kg)
With 3500kcal a day I finally make some progress in weight lifting 😍 increased squats to 120kg at 3x12 this week
I hit a new running PR: a pace of 04:20 per km on a distance of 7.5km ✌️🎉
You went to Japan for the food, why am I not surprised? 😂
The second day after a workout is always the worst 💪
I noticed a new behavior. I lost 37kg in 6 months, and now, as I have finished losing weight, every time I eat above my calories I feel guilty. Yesterday I ate about 50 kcal over my need for that day, and I thought about an hour if I should go for another walk just to get rid of that surplus.
Although my goal is to gain some muscle weight (which means I have to have a caloric surplus) I am still in that „eat less!“ mindset. That's an interesting new behavior for me.
OH: „sweat is fat crying“ 😂
I ordered the Apple Watch Series 3. While it is a lot of money for a silly watch (the most I spent on watches before the Apple Watch was about 80€ for a G-Shock) I noticed that my Series 0 watch is my most used Apple device over the last three years. I use it every day, mainly for activity tracking during sports and for calorie counting. The fitness marketing totally worked on me. I'm even excited for the new device 😝
Apple is using some interesting tech for web pages on the iPhone X (via @ttepasse).
Chris Wellons writes in this article about gap buffers and their performance indications when using multiple-cursors.el. He states that because of the technical implementation of changes in Emacs as gap buffers things like multiple-cursors.el
are a performance hit and thus should not be used. Instead one should use search & replace as well as macros.
I totally disagree. Performance is nothing I should be molested with as a user. When I choose to use a tool I look at the mental overhead it adds. Will it disturb my workflow? How much thought do I have to invest to use it properly? How much thought is necessary to solve my editing problems?
Macros, for example, add a lot of mental overhead. I have to be aware of many things: I have to ensure that the cursor is at a defined position before executing it (often done with a movement to the beginning of the line), I have to ensure that cursor movements are reproducible in the different contexts, etc, pp. It totally disturbs me in what I am doing right now.
Search & replace on the other hand add a bit of complexity, but much less than macros. The biggest difference is that I can't see my changes before executing the replace.
This is fixed when using multiple cursors: I instantly see my changes and can adopt them, e.g. in case of typos. Also more complex edits are possible since all cursor movements are done on all cursors.
I just don't care about the performance. Make it fast enough that I don't get annoyed by lag, that's good enough for me.
This FSFE campain is pretty neat: public money, public code. Basically it says that all software developed with public money should be FLOSS. I signed it and you should consider signing it, too.
José Valim, inventor of Elixir, wrote an interesting blog post about the fallacies of web application performance. He writes about some common misunderstandings on this topic, including my favorite one: performance is only a production concern. Hint: it isn't!
I stumbled upon an interesting article about choosing Elixir for the (healthiness) of the code and not because auf performance reasons.
While I agree that performance alone is a bad reason to choose a tech stack I still think that performance is important. On the other hand expressiveness and effectiveness of the language are important as well. He makes a pretty good case.
Although I'm not a Firefox user these days I have to say I'm impressed by their last release. After years of ignorance followed by years of „we're not that slow really“ they finally got noticeably faster. It feels much less sluggy and websites which were slow on the older releases now feel much more responsive. Kudos!
When you search the web on mobile the top search results are always AMP… this is at least true for news articles. I noticed that a few months ago, sadly.
Making progress in the gym feels so good. Hard work pays off!