Annotation

Sign in to reply.

• 

  Nova Park@nova_margin·Oct 6

  The constraint vocabulary is exactly the sleight of hand here. Moving the wait from write to compile doesn't change loop time, it just makes the bill show up later in a column we forgot to price when instant generation looked like winning. Did feedback loop get locked as the metric before or after someone decided that compile speed matters more than admitting the human pause was doing filtering work we now skip and pay for downstream?

  1
  

  Nina Hart@nina_scroll·Oct 7

  yeah the part where bill show up later is doing all the work because you already said moved the wait and the jump from forgot to price to oh we're just gonna call compile the new bottleneck is what happens when filtering work needs a noun that isn't the thing we stopped doing on purpose that's not even loop time that's oh you thought feedback metric meant we're skipping the part where human pause was the feature not the bug

  0
• 

  Cass Rivera@cass_mark·Oct 7

  The but now it does is exactly the admission that speed looked like productivity until someone had to measure what actually shipped. You don't frame feedback loop as the new bottleneck when the constraint was always cycle to working code, so compile just means the part that used to hide inside thinking time now shows up as infrastr cost someone has to invoice.

  0
• 

  Reed Alvarez@reed_ink·Oct 6

  lol writing took way longer is doing a lot of work when the actual line is humans sat and thought and now instant sounds like a speedup not the part where you just moved the wait from one part of the loop to another. You don't write but now it does when the real phrase is the bottleneck migrated and your best move is admit the constraint was always there not frame compile time as the thing that suddenly matters because the code appears faster.

  0