catacomb

Yeah, I've filled 256GB pretty easily by recording on an action camera all day, maybe for a couple of days. 4TB would be very convenient for a holiday.

Did you pull it before checkout?

Yeah and this still wouldn't cover something like xz-utils because I would only be aware of end user projects and not the libraries behind them. I'd have to draw up entire dependency graphs.

Now run an emulator within an emulator for extra acceleration.

OP:

Jokes aside, I think what you're looking for is called a multiviewer. You want a 2x1 multiviewer to get a view like that, though it might be split vertically rather than horizontally.

Yeah, I don't think it's completely quiet and it also adds up.

I love the combination of auto stop/start, hybrids and electrics in the city. No idea what the real environmental impact is but the silence at traffic lights is amazing.

Brit here. I think we're the same? I've never gone to a concert by car. It's usually in a major city and it's just easier by train. Not cheaper, though.

I've had friends tell me they've been stuck in car parks for hours while leaving concerts, so people obviously do it. It's just not a great idea.

I guess it'd be different if we had massive car parks instead of train stations, which is becoming more the case with shopping.

Ah, sorry.

Don't forget rustaceans for rust!

If you don't already, use version control (git or otherwise) and try to write useful messages for yourself. 99% of the time, you won't need them, but you'll be thankful that 1% of the time. I've seen database engineers hack something together without version control and, honestly, they'd have looked far more professional if we could see recent changes when something goes wrong. It's also great to be able to revert back to a known good state.

Also, consider writing unit tests to prove your code does what you think it does. This is sometimes more useful for code you'll use over and over, but you might find it helpful in complicated sections where your understanding isn't great. Does the function output what it should or not? Start from some trivial cases and go from there.

Lastly, what's the nature of the code? As a developer, I have to live with my decisions for years (unless I switch jobs.) I need it to be maintainable and reusable. I also need to demonstrate this consideration to colleagues. That makes classes and modules extremely useful. If you're frequently writing throwaway code for one-off analyses, those concepts might not be useful for you at all. I'd then focus more on correctness (tests) and efficiency. You might find your analyses can be performed far quicker if you have good knowledge about data structures and algorithms and apply them well. I've personally reworked code written by coworkers to be 10x more efficient with clever usage of data structures. It might be a better use of your time than learning abstractions we use for large, long-term applications.

Good to know the name, I've seen it invoked a few times.

In fact, I had this recently at work where I questioned a decision only for them to retort with one similar characteristic which a prior suggestion of mine shared. This was also a modal fallacy as they only used that one characteristic to come to a conclusion about both.

You also see it all of the time in politics unfortunately, a lot of "yeah but you also..." where we should be hearing good justifications.

I've used it for the exact same purpose, great minds think alike. It's perfect for that scenario given there's no internet.

I just don't use it much otherwise because apps like Signal are far easier to move my friends and family on to and they're more than good enough. The metadata privacy Tor would provide would give me a lot of peace of mind but I know it'll never happen.