noroot
Joined 5 years ago
Joined 5 years ago
She also had to go through a very expensive process to renew her British passport last minute.
Silly system.
Even putting aside the MITM and how horrendous that is, the amount of time lost from people dealing with the fallout got to have cost so much time (and money). I can't fathom why anyone competent would want to implement this, let alone not see how much friction and safety issues it causes everywhere.
The whole operation log was already so nice. It's saved me a few times when I did some stupid things, but also invited me to experiment and learn :).
I have been super happy to discover jj a few months ago. I am on the path to go from barely getting by with git ui's to be able to do vcs magic with jj.
Been using jj without significant issues for about a month and been super happy to be comfortable using the cli and slowly ramping up to more complicated operations.
The documentation still assumes a lot of inherent knowledge which sometimes makes it a little difficult. I love seeing blog posts like these and hopefully some more in depth resources will appear over time. Steve's guide is good, but there are still gaps for me :).
Next I want to learn some more revset language and become a bit more fluent with rebase operations. I love the more simplified cli, conflict resolution and op log!
There clearly still is some untapped potential in this space, so I am glad benbjohnson is exploring and developing these solutions.
Great that the new release will offer the ability to replicate multiple database files.
> Modern object stores like S3 and Tigris solve this problem for us: they now offer conditional write support
I hope this won't be a hard requirement, since some S3 compatible storage do not have this feature (yet). I also do use the SFTP storage option currently.
I don't know nor understand why it doesn't work and if it's a bug in the power bank or the laptop
The issue is that the defrost mode will defrost all the ice from the fins, but it freezes again before it can all drain through the small drain hole on the bottom of the housing. It's somewhat a known issue with air source heat pumps, sadly. I've not run into this issue myself, but on a Dutch speaking forum (tweakers) there is a long thread about this modification to "survive" the cold spells with this small modification.
You can manually attack the ice with a heating gun or hair dryer to remove it, but that's a faffy.
I think manufacturers should, and probably will, add something like this themselves in the future.
For me another issue was that I needed to do more keystrokes for the same behaviour (search a previously ran command and execute it).
Fuzzy shell history search is just one of those mind-blowing things. I love my history, it's such a trove and I can trust it to work as some kind of external memory (it's enough to vaguely know the kubectl command, or that I want to "du -h | sort" to see what is using disk space, etc).
At home, for some hobby projects, I've been using earthly. It's just amazing. I can fully run the jobs locally and they are _blazing_ fast due to the buildkit caching. The CI now only just executes the earthly stuff and is super trivial (very little vendor lock in, I personally use woodpecker-ci, but it would only take 5 minutes to convert to use GH actions).
I am not a fan of the syntax. But it's so familiar from Dockerfiles and so easy to get started I can't really complain about it. Easy to make changes, even after months not touching it. Unless I update dependencies or somehow invalidate most of the cache a normal pipeline takes <10s to run (compile, test, create and push image to a registry).
This workflow is such a game-changer. It also allows, fairly easy, to do very complicated flows [1].
I've tried to get started with dagger but I don't use the currently supported SDK's and the cue-lang setup was overwhelming. I think I like the idea of a more sane syntax from dagger, but Earthly's approachability [2] just rings true.
[1]: https://github.com/phoenixframework/phoenix/blob/master/Eart...
[2]: https://earthly.dev/blog/platform-values/#approachability
I've been using dvorak for 10+ years now and have always used it on my (Android) phone as input method too. In my experience it's not a positive nor a negative to use dvorak on a mobile phone. My brain is so used to dvorak now that I just keep it on dvorak.
I have a fairly small house, with only 2 adults, that's full electric (appliances, cooking, hot water, heating). We have a dishwasher (used every other day) and we also use a washing machine (and sadly often the heat pump dryer because there is no space for a drying rack).
We use, all in, about 4000 kWh/year. About 750 to 1000 of that is for heating the house and hot water. My idle usage is higher then your average, which is somewhat crazy. I have about 30-40W for the ventilation system, about 20W for modem/router/wap, 10W for home server and the rest is for fridge/freezer I guess.
Even just cooking on the induction hob, or using the (electric oven) will already blow your entire day budget. Let alone a dishwasher or washing machine cycle.
I'm fully aware that the biggest improvement can be made in being aware of your usage (which I am, I monitor it carefully) and try to be more mindful about it. Yet it's not easy to lower the numbers significant.
Some years ago, as a single, I also was (well) below 1000 kWh/year. But that was without a dishwasher, or dryer. And generally cooking less often/fancy then my wife currently does. Work from home with 2 adults (with big monitors, a beefy desktop, etc) also adds energy usage.
Hopefully it gets backed and I'll be able to see if I can make it productive for coding and writing at the end of the year.