Admittedly I haven't been to many concerts, but 'national security reasons' seems like a reasonable rationale to me because a packed concert sounds like a great place to set off a suicide bomb vest for maximum impact. Have a cut-out who doesn't raise any red flags buy the ticket and hand it off to the person wearing the vest. No ID check? Mass panic ensues when the vest goes off, and people are hurt in the stampede for the exits even if the blast radius of the vest itself isn't all that large.

I complain about movie costs while I watch movies at home, drive a VW that was under $40k new, live in a state with a minimum wage over $17 an hour, and refuse to pay $14 plus tip to a food truck that doesn't provide seating when I can pay $12 and no tip at a fast food restaurant that does provide dine-in eating.

Some of us live our principles, we're not all just whinging hypocrites.

As someone who lives alone, two ways I address this aspect: talk to yourself out loud and to your pets like they're people, and also write these things down in a journal. Every night after I get into bed but before I turn out the light and fall asleep, I write a journal entry. Sometimes they're quite mundane, exactly like your examples. "I cooked a steak for dinner that turned out better than I expected" or "Tomorrow I'm thinking about making some bread." There's no pressure on length of entry, I fill anywhere from three sentences to a full page each night, but it helps fill the 'how do I communicate this minor accomplishment or discomfort that nobody else cares about' need for me.

For attachment, I'd evaluate their conductive epoxy or maybe glue down the underside of the component and then smother the lead with the silver conductive ink. But again, just hypothetical since I have a quickturn shop make cheap prototype PCBs for me and either hand solder or use a stencil, paste, and a hot air gun for my hobbyist projects.

https://www.chemtronics.com/circuitworks-conductive-pen

https://www.chemtronics.com/circuitworks-conductive-epoxy-2

I grant that SpaceX engineers are smart people and can figure out how to make Starship and Superheavy reliable and reusable.

But if they have to launch 10-14 times in order to get the propellant to the LEO depot in order to fuel the Lunar Starship, can we actually deliver that many launches worth of LOX and LNG to the launch pads in the timeframe needed to prevent it all from boiling off once in orbit before Lunar Starship can get there, get refueled and head to the moon? I don't know the answer to that, and to me that seems like the hard problem.

[1]: https://dor.wa.gov/taxes-rates/other-taxes/capital-gains-tax

[2]: https://finance.yahoo.com/news/jeff-bezos-moved-florida-impa...

The Bezos Earth Fund: https://www.bezosearthfund.org/

> However, we have never before applied a killswitch to a rule with an action of “execute”.

> This is a straightforward error in the code, which had existed undetected for many years

So they shipped an untested configuration change that triggered untested code straight to production. This is "tell me you have no tests without telling me you have no tests" level of facepalm. I work on safety-critical software where if we had this type of quality escape both internal auditors and external regulators would be breathing down our necks wondering how our engineering process failed and let this through. They need to rearchitect their org to put greater emphasis on verification and software quality assurance.

> Critical infrastructure still written in C - particularly code that parses data from untrusted sources - is technical debt that is only going to get worse over time.

But hasn't all that foundational code been stable and wrung out already over the last 30+ years? The .tar and .ar file formats are both from the 70s; what new benefits will users or developers gain from that thoroughly battle-tested code being thrown out and rewritten in a new language with a whole new set of compatibility issues and bugs?

[1] https://en.wikipedia.org/wiki/Aeronautical_Telecommunication...

It doesn't say she chooses to use it; it says she can't work without using it. At my workplace, senior leadership has mandated that software engineers use our internal AI chat tooling daily, they monitor the usage statistics, and are updating engineering leveling guides to include sufficient usage of AI being required for promotions. So I can't work without AI anymore, but it doesn't mean I choose to.

I've done it. We already had a YAML parser in an internal library I maintain since we were already ingesting YAML files for other reasons, so when we later added new files for a different reason that someone decided should be in JSON instead, it was easier and cleaner to keep using the existing YAML parser we already had incorporated rather than add a separate JSON parser along side it.

"Experts say that airdrops, another measure Israel announced, are insufficient for the immense need in Gaza and dangerous to people on the ground."[1]

"[T]he airdrops have an advantage over trucks because planes can move aid to a particular location very quickly. But in terms of volume, the airdrops will be 'a supplement to, not a replacement for moving things in by ground.'"[2]

The airdrops killed people when 1) the containers landed on occupied tents and, 2) containers landed in the water and people drowned attempting to retrieve the aid. Trucks can also delivery vastly larger quantities of aid substantially faster and cheaper than planes.

[1] https://apnews.com/article/gaza-starvation-israel-palestinia...

[2] https://apnews.com/article/israel-hamas-gaza-airdrop-humanit...

I've conducted two phone screens this month and asked each candidate to implement FizzBuzz in their language of choice after giving them an explanation of the problem. Both took more than ten minutes to write out a solution and we don't even require them to run it; I'll excuse trivial syntax errors in an interview setting if I can tell what you meant.

When CS students can't write a basic for loop and use the modulo operator without relying on AI, I weep for their generation.