ersatz ziggurat zoochotic oleaginous sprezzatura tempestuous

I feel like the event size limit is generally much more real struggle for folks but the solution is the same -- use the env var to provide an s3 object key or dynamo item key and load it outside the handler in the setup section.

Leadership suspects or fears that an AI company will capture the market from their workflow-machine business but isn't able to respond because they've built too good of a system for building their workflow-machine. "The Innovator's Dilemma" discusses this pretty extensively.

Wait! Can you fix an issue that's been bothering me since github introduced this? The size/darkness of the day should be normalized so that there's more resolution for days close to the mean and less for outliers. That way one busy day doesn't dramatically change the scale for your whole timeline.

I think the idea of guilds and squads resonated with me, but like most "scaled agile" setups that didn't work with management chains. Is there something salvageable in the wreckage that we still want?