Patrick Thomas, Senior Security Partner @netflix, is speaking @LocoMocoSec next week!
Register now to see his talk 'Productizing Security For Leverage and Scale' on June 30th🤙
⛵ Waikīkī Marriott Resort
🏝️ O'ahu, Hawai'i
☀️ June 27-30th
🌟 @coffeetocode
I love formal forecasting exercises (esp those run by @Magoo) because they really force you to slow down consider all the potentially relevant facts, and introspect your biases. FWIW I was 80% here, but I think I was undervaluing the "autopilot" nature of modern CI/CD.
That's what myself and 26 others sought to gather over the weekend. The panel we put together forecasted a 72.8% belief it would happen. Here's the spread of forecasts
https://t.co/fS70r6WCNf
Of the ~950 people I follow on twitter, some hacky profile scraping says that about 60 of those currently have a Mastodon link. So for me that's basically from ~0% to 15% exodus (or at least strongly hedging) in a *week*.
@ropnop@nart_nos@hez0_ ...now I just wanna spend the rest of the day ducking with serviceworkers. Also, doesn't this seem like a pattern that could be codified in a browser mechanism the same way httponly is? (Or is it and I just missed it?)
Know how many blog posts I start writing but never finish? *HEAPS*! Sometimes the story just doesn't work out as expected, sometimes I calm down and change my mind, other times... I'm a busy guy 🤷♂️ Are there any here I really should finish?
When looking at a big backlog of known work we want to drive, it's *so easy* to just group into themes and call it good. I can think of times I've done that which really, really would have benefitted from asking if the framing leads to an ability to confidently prioritize. 2/2
Someone asked today "Is that list of 'goals' *really* a list of goals, or just a some themes of work?"
I *love* that question & the insight behind it. True "goals" help prioritize among possible work, themes really don't. 1/2
Chrome was delivered without any sprints at all. The team came in at 9 and left at 5 (figuratively, people actually kept their own ~8h schedules) every workday for a couple years like clockwork. No drama. No broken marriages, no broken families.
@caseyjohnellis@timb_machine@UK_Daniel_Card Hah, funny you mention that. @ramimacisabird was saying that the other day, and we've been talking about what an updated, more thoughtful/communicative view would look like. What aspects looking most wrong or dated to you now?
Congrats to @Resourcely! Clear, exciting product vision at that critical touchpoint of developer velocity, security, and cloud resources.
Very pleased to have joined this round, and looking forward to seeing where @travismcpeak and @0xshellrider take this idea.
Hello world! We're on a mission to make cloud security easier for users. See our funding announcement (https://t.co/uBm6JTCAct) and blog post (https://t.co/xXLAUz4Pes) for more details.
We're #Hiring!
Web timing attacks: super cool in principle, still super janky in practice. Seems like TimeTrial (https://t.co/tVkldL3epu) and Nanown (https://t.co/TPKkst2VPm) still best tools, but really janky to get running & require a known-good case. Anyone got suggestions? Banging my head.