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?

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.

I really liked how coupling is described as “knowing.” I find we talk about “does x need to know about y?” more than we do “is x overly coupled to y?” because the former is a relatable indicator of the latter.

F5 is American, they just had a Moscow office.

However the creator of nginx, Igor Sysoev, is Russian.

I use a UK keyboard, | is pretty easy to access and $ is Shift+4.

I’m guessing you mean more exotic keyboards. I’ve used a Swedish keyboard while helping a friend and I had to ask where every key was. You probably just learn the combinations eventually.

https://www.cloudynights.com/ is probably the best astronomy community about, the subreddit never compared.

obscure corporate jargon like KPIs (key performance indicators), KRIs (key risk indicators) which, after having thrown them at me during an interview for a college intern position, made the interviewer wonder why i got so flustered. i would hesitate to throw any acronyms around in any interview, let alone for a college student.

by the way, i got the internship. the acronyms weren’t even used in my position.

Ah, it might be a regional thing. In the UK, the cheapest Vitamix is almost £400 where the Magimix was about £200 at the time. They might be pretty comparable but the prices don’t quite work out the same here.

Totally agree though, I was getting through a £50-75 blender each year for really silly breakages with no spares available.

A decent blender. Not anything industrial like a Vitamix, it’s a Magimix which was about half as much but still durable and has replaceable parts. It’s fine for what I need and is lasting much longer than the pile of crap I had before.

Vacuum pack bags for clothes is another one. I like to keep my wardrobe seasonal but I don’t have much space, so packing it down helps.

Also anything reusable: PTFE/silicone baking sheets, rechargeable batteries, reloadable floss handles. All of these have saved recurring purchases, money over time and reduced waste (which made me feel good.)

To be honest, I agree they should be able to be larger at times.

I had a lot of disagreements when I was on a new codebase, knew what I was doing and I was able to push a lot of code out each day.

The idea is to have them small, easily readable with a tight feedback loop. I argued that bootstrapping a project will have a lot of new code at once to lay the foundations and my communication with the team was enough feedback. If I split it up, each PR would have been an incomplete idea and would have garnered a bunch of unnecessary questions.

That said, I think it’s generally pretty easy to put out multiple PRs in a day, keeping them small and specific. As you say, half of the job is reading code and it’s nicer to give my coworkers a set of PRs broken down into bite sized pieces.

I’d be pulled up at my job for any PR exceeding a few hundred lines. I don’t even know what they’d do if I just dropped a 15000 line stinker.

Have you seen the Star64?

Nice try, boss.

Yeah, I think that comes from the developer having high standards for hardware security. The effort put in is a waste if the hardware fails. I would have thought Samsung would have been suitable too, though.

What about /e/OS or plain old degoogled Lineage? I like it as a phone OS, it’s just a shame the app ecosystem is so dependent on Google’s services.

Yeah, this is one of those things which sounds great on paper but also introduces problems. I’ve seen people get really annoyed when exception messages are translated because it makes them harder to search for online. That would need to be solved too.

I’ve had huge issues collaborating on a spreadsheet with a Spanish client. It tries to open the sheet in your locale and then can’t find the functions. Insane that Microsoft didn’t even add some metadata to allow me to work on it in Spanish.

Bottom left is when I make a kubernetes cluster to serve up a mock weather API for practice.

Exactly. I used PHP for years, I haven’t “not used it.” It was the first programming language I seriously learned. Writing good code was tedious if not impossible and that became even more obvious as I expanded to C#, Java, Python and C++; none of which tolerated any of the bad and unconventional practices I’d inevitably picked up. Keep in mind, I was actively trying to avoid bad practices and pay close attention to types but still got kicked to the curb hard when I tried other languages. I haven’t had that since.

I appreciate it’s changed since, I’m happy to see it’s not the same dumpster fire it once was, I also don’t care. I don’t actively trash it, I just think there’s usually a better option.