

it’s fascinating that from the headline it’s absolutely unclear whether the protests are even related to the 16 kills. if i were glancing (and wasn’t aware of the situation), i would’ve thought that 16 were killed as Israeli finally listened to the protesters or something.
“protesters in Israel” (must be some foreigners) vs “Israeli strike”.
while they actually demand a ceasefire that will allow for release of hostages, and their government does everything to avoid that ceasefire. oh, and then there’s “strike kills 16” leaving it ambiguous whether military or war crimes.
also ceasefire implies both sides are fighting. from what i can tell Hamas pretty much stopped fighting almost two years ago.
“Israeli protesters demand their military to stop attacking Gaza, as Israeli army kills 16 civilians and journalists in an attack on a hospital in Gaza in another apparent war crime”.
how about now?

As I’m slowly evolving my own flavour of spec driven development, I’m starting to think about the generated code as a secondary artefact where main quality criteria is that it’s doing what it needs to and it’s covered with tests.
I guess my current analogy is that I don’t care about how readable or dry is the assembly code generated by compiler.
I have the specifications and the working code with tests. I can always regenerate it if I need to.
But. I still read the produced code, steer the design and correct the obvious blunders. No vibes.