I like the idea, but I can’t come up with any method that won’t devolve into most reviewers only checking the highlighted parts tbh.

No, this is actually the first time I’m hearing that this exists unfortunately.

I was obsessed with making variations of it on TI calculators in high school lol

I live in DFW right now. I’ll admit i don’t commute through downtown proper daily, but even when i do go through downtown after work it’s bad, but not nearly as bad as plenty of other places in thr US.

15-45 minutes… I’m not exactly knowledgeable about pizza delivery logistics, so forgive me if I’m wrong about specifics. There was a decade or so where every chain promised delivery in 30 minutes or the pizza was free, but that’s no longer a guarantee these days.

Pizza delivery has electronically heated insulated containers for the drivers to keep the pizza in during the drive. Generally I think they group up orders so one delivery driver will hit up maybe 10-20 deliveries in that one run. It’s normally not driving 20 miles just to deliver one pizza.

Our cities aren’t densely built up, except for New York. The actual urban area of most cities generally has far fewer people than the suburban metroplex surrounding it. 6.5km is literally larger than all of downtown Dallas, depending on how you define downtown.

Even our cities are designed for car travel, so unless it’s rush hour you’re still faster by car. Unless there’s a concert or other event happening, it doesn’t take nearly 20 minutes to traverse downtown Dallas in a car.

Are you in the US? I’ve literally never seen a delivery driver on a bike, except for that action movie about bike couriers in NYC.

I’ll say that if the really talented people are signing on to this, that could be noticeable. I know Amazon tends to just churn through devs every year, but actually good software engineers are surprisingly hard to find.

Zelle is free. It sucks, but it’s there.

I think someone else said what it actually is in another comment. It’s functionally identical 90℅ of the time for me anyway,and I use CLI and vim on it.

It works fine for small projects. I think that with more than 2-3 devs a PR based strategy works better for enforcing review and just makes life easier in general, since you end up with less stuff like force pushes to fix minor things like whitespace errors that break everyone’s local.

If it’s a private repo I don’t worry too much about forking. Ideally branches should be getting cleaned up as they get merged anyway. I don’t see a great advantage in every developer having a fork rather than just having feature/bug branches that PR for merging to main, and honestly it makes it a bit painful to cherry-pick patches from other dev branches.

Everywhere I’ve worked, you have a Windows/Mac for emails, and then either use WSL, develop on console in Mac since it’s Linux, or most commonly have a dedicated Linux box or workstation.

I’m starting to see people using VSCode more these days though.

I didn’t realize just how siloed my perspective may be haha, I appreciate the statistics. I’ll agree that cyber security is a concern in general, and honestly everyone I know in industry has at least a moderate knowledge of basic cyber security concepts. Even in embedded, processes are evolving for safety critical code.

… You know not all development is Internet connected right? I’m in embedded, so maybe it’s a bit of a siloed perspective, but most of our programs aren’t exposed to any realistic attack surfaces. Even with IoT stuff, it’s not like you need to harden your motor drivers or sensor drivers. The parts that are exposed to the network or other surfaces do need to be hardened, but I’d say 90+% of the people I’ve worked with have never had to worry about that.

Caveat on my own example, motor drivers should not allow self damaging behavior, but that’s more of setting API or internal limits as a normal part of software design to protect from mistakes, not attacks.

My take was that they’re talking more about a script kiddy mindset?

I love designing good software architecture, and like you said, my object diagrams should be simple and clear to implement, and work as long as they’re implemented correctly.

But you still need knowledge of what’s going on inside those objects to design the architecture in the first place. Each of those bricks is custom made by us to suit the needs of the current project, and the way they come together needs to make sense mathematically to avoid performance pitfalls.

I was gonna say, the OP here sounds perfectly good at computers. Most people either have so little knowledge they can’t even start on solving their printer problem no matter what, or don’t have the problem solving mindset needed to search for and try different things until they find the actual solution.

There’s a reason why specific knowledge beyond the basic concepts is rarely a hard requirement in software. The learning and problem solving abilities are way more important.

Thinking about it a bit more, I think it’s more like the metrics used to get in front of a human (the automated/hr part) aren’t well matched to the actual goals. We end up interviewing a lot of people who are good on paper according to the first sort, but actual good hires within that aren’t as common as we’d like. But none of the engineers ever know about any of the people who were disqualified due to having an unimpressive resume…

So in the end, the initial sort does indeed end up wasting time and money, but no one’s gotten around to making a good solution for this yet. The alternative so far is to interview a bunch more people, which is also really expensive anyway.

Basically, we have no efficient way to find people who are bad on paper but are actually quite skilled.

That… Isn’t what I’m saying? I’m saying they won’t bother to go to the interview phase with those people most of the time because they have higher probability options to try instead.

Usually getting in front of a human for an interview is the hardest step. Once you’re talking, you can generally show your expertise, and most interviewers I’ve known are receptive to any sort of past experience that’s techy and related enough, or even just problem solving related.