catacomb

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.

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.

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.

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

Dual Core - For Aaron

I've worked in two open offices and, yeah, I largely hated it. One was just to enable micromanagement and prevent you from taking any breaks. The other was the opposite, in a very small company, having far too many distractions from music to complete nonsense conversations.

I've now moved to a fully remote role and we get far more done. No distractions and a tidy environment (my home) to think. The "random interactions" occur in group chats and the odd meet-up. Mixing the right people is sufficient and the setting is largely irrelevant.

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.

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.