finaard

> As for the second part (separate authentication methods), sure, would be rather problematic if they require you to have a phone, but that's a completely separate and different issue.

It's getting somewhat annoying nowadays with banks pushing that crap, but fortunately legislation for access of people with disabilites forces them to provide tokens still.

A lot of them now switched to banking apps on the phone acting as token without a chance to opt out, though, so as a result I've stopped doing anything bank related on phones nowadays.

It heavily depends on "what kind of DC". A lot of current DCs are not really well protected against a lot of known threats - and that's just a design tradeoff.

High value data is already protected a bit better (or at least should be - the usual trend, management gets lazy when nothing blows up). I'm old enough to have sat in the meetings for "so, apparently a plane crashing into one or more of our locations is a viable risk now" - and a DC hardened for "somebody tries to land a 747 on that thing" should also survive a small drone with a bit of explosives.

While for the younger ones the "we lose several availability zones within days" is a new thing now - it really isn't. We were planning for that back then as well, just that we didn't call it "availability zone" or "cloud" yet.

Well, that's why you had /usr/xpg4/bin, /usr/ucb/bin, .. so you'd have all the variants of all the tools readily available.

I'm still searching if somebody else made something for tiny tooling before I start throwing something together. Getting something just working is easy nowadays, and makes things that we considered not worth the effort before viable, but making sure it actually is good, doesn't have unintended side effects, and has good documentation (which I'm still typically writing by hand) adds quite a bit of extra effort on top, which still makes sharing the better option than just doing everything yourself for a lot of things.

Both. My standard phone defacto already is a burner phone, so I'd just either wipe it or pick something new up when travelling to that kind of countries.

Similar for a notebook - I'd travel with an empty one, restore it after arriving, and wipe it again before leaving. I have infrastructure in place to make that easy and secure for me to do.

I find modern smartphones more and more unusable, both OS becoming more hostile towards the user, and applications widely moving to dropping logins in regular intervals. That has been happening for years already, so I slowly moved more and more stuff back to a computer.

By now I'm at a point where I no longer even backup my phone - there are a bunch of apps, but I can just install them and log in again on a different device as needed.

The final step to make it truly throwaway was me doing a custom matrix bridge for SMS earlier this year - I had voice routing setup for a while already. So now my old SIM cards are in a 4G modem at home, and the phone I carry around with me just has a data SIM. Huge quality of life improvement, as I can terminate as many numbers as I want there, and have access to both voice and SMS data from my computer as well.

That's not the problem for me - I carry a bunch of tokens with me anyway (all my banking stuff is on hardware tokens, for example). My problem is more: My browsers run in containers or VMs, intentionally without hardware access. Getting passkeys to work there would be quite a bit of effort.

Verbosity can be fine, but you'd want a simple enough text, with the verbosity separated. I still write emails with footnotes, and thanks to UTF-8 I now have all the numbers available.

Amusingly enough the advent of HTML-emails didn't produce any better formatted mails, despite the extra formatting options, than what you can do with a plain text email supported by a proper text editor.

Depends - if parallel decompression of any bzip3 archive is possible I'd consider it fair, if it requires special flags on archive creation I'd consider it unfair. I didn't see any description about that on that page.

pbzip2 only can do parallel decompression on archives created with pbzip2, otherwise it'll fall back to single thread. There nowadays seems to be lbzip2, though, which claims to be able to add SMP support for standard bzip2 archives.

I'll need to try that next time I'm working with large archives - I learned about the pbzip2 limitations the hard way last time I was shuffling around a few multi-10GB archives, and was trying to speed things up fully utilising my 32 core threadripper.

One of my customers now added a policy that junior developers may use AI assistance, but are expected to write code by hand. Only proven developers can use AI to generate code, and are then expected to understand the generated code, and take ownership.

I've worked at places very popular with candidates before, and was involved in hiring. For the first screening a CV/cover letter would get roughly one minute of our time. If it took longer than that to get an overview of what you claim your skills are you were out. Same if anything made reading it harder, which includes lots of spelling mistakes.

The main power advantage of the apple chips is when the system is mostly idle - under mid to high load power to watt has been comparable for a few years already (at least AMD and Apple, intel was way behind - but I guess they caught up recently). The main reason behind my M3 MBP back then wasn't so much power efficiency - but that I can get it with 96GB of RAM.

It's nice that I can go a full office day without charging - the previous x86 notebook couldn't, but a decent one from the M3 generation probably could as well. But also if I put proper load an that thing the Macbook battery is done in less than 2 hours.

There are various "air mouse" variants that properly work with MacOS as well. I have one with some media/navigation keys on the front, and a tiny keyboard on the back - kodi I can navigate just with the navigation keys, and if I want to do a bit more (but not get out the proper keyboard) I just flip it around, and can do that as well.