That’s fair. I don’t mean to invalidate your personal experience with cast iron rusting, but I do want to present a counter experience so people don’t think it’s definitely like that.

By the time my cast iron cools, I’ve left the kitchen, so tbh i generally clean it before the next time i cook with it, and have never had rust issues no matter what i cooked in it last. Every once in a while i notice the seasoning getting a little thin after scrubbing it, so I reseason it with a single layer on the stove.

With my carbon steel wok, i regularly clean it by tossing it on the wok burner at full blast until it’s entirely red hot and everything has carbonized off of it, and maybe splash some water in to help clear that off. Then i wait for it to cool enough and reseason it with a quick wipe of oil while it’s still hot enough for the remaining heat to polymerize the oil.

Basically, I’ve never spent significant effort taking care of my cast iron of carbon steel cookware, and it’s all still perfectly functional and non-stick and not rusted.

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 also prefer the cold myself, but you know it gets much colder than 0°F in lots of places right?

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.

For a person making $30,000 a year, a $1,000 fine could mean very significant impacts on their daily life.

For a person making $30,000,000 a year, a $1,000,000 fine may mean they can’t afford an extra Ferrari.

For a person “making” $30,000,000,000 a year, a $1,000,000,000 fine may mean they can’t… Buy another island? You still have $29,000,000,000 that you can do who knows what with. This is the entire GDP of some countries. I also don’t know if this one is a realistic example.

Anyway, proportional is nice, but really you need a progressive system to really match the weight of punishments, as far as impacting your daily life or happiness.

~220% total comp for me last year, switching companies from a job with okay but below market pay, and becoming a senior software engineer in the move. I think I can feasibly double one more time if I try, but it’d be a bigger push and likely involve working for FAANG. Anything more that is outside my reasonably likely career path.

Because I can’t afford 120TB in SSDs…