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.

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 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.

I was going to say that Cloudflare uses nginx but I found that’s no longer true.

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.

I feel like this is overlooked far too often. I rarely see anyone use data structures outside of (array) list and hash table and any attempt to use something descriptive of the problem is often shot down because of “familiarity,” which is sort of self-fulfilling.

I get away with flagging lists which should be sets, though.

deleted by creator

Yep, employers under capitalism only understand leverage. Job hop, play multiple offers against each other, negotiate a higher salary and have the power to walk. It feels sleazy but it’s self preservation. It’s only as sleazy as their incentive to pay you as little as possible.

“Hard work” was the wisdom passed down but I think it came from confirmation bias. If your employer gives you good raises just to keep you, you’ll feel you deserve it instead of attributing it to a very good job market for workers.

It’s cool, we figure it out after a year or so in this environment (if nobody has told us.)

The biggest issue most people have with it is the dynamic DNS feature, which is automatically enabled and contacts their server to create the record. If you turn this off before connecting the router to the internet, you’re probably good.

The simplified DoH client also only allows either Cloudflare or NextDNS, which aren’t the most privacy-oriented options. Still, it’s possible to set up your own.

Otherwise I’ve never heard of anything major; the devices are cheap and reliable. I’ve had one running constantly for years and only had to reboot it manually once.

Where did you get 100 from? I’m just asking if it’s a real limit or a guess at “some manageable number” under one million.

It can be worth experimenting and tuning this value. You might even find that less than 100 works better.

DMCA takedown from Meta incoming

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.