moograms

Hi, I'm Drew, Stripe's new engineering blog editor. Thanks for sharing your experience! I didn't edit this one, but this is helpful for future posts.

Hi, I'm Drew, Stripe's new engineering blog editor. Thanks for the feedback! I wasn't editing back when this post was written, so I don't know whether or to what extent what you say is true, but the important thing is that I solemnly vow to avoid AI slop in the future.

Hi, I'm Drew, Stripe's engineering blog editor. I wasn't editing back when this post was written, but #2 and #3 will help us shape future posts. Thanks for taking the time to give thoughtful feedback!

Here are my predictions for 10 years out along with upskilling recommendations: https://open.substack.com/pub/drewhoskins/p/the-most-promisi... I agree with many of your points, would just generalize a couple of them. For example, I think there are many pieces of software that need to be complex and excellent, not just those close to hardware. And niche apps are a good (but not only) example of where LLMs will struggle to solo-code because they lack product context. Other key questions for a project: how much training data does the LLM have access to? (Innovative things generally have much less.) How much ownership skill is required to build it?

Not an expert, but it's one of those things where you can never be 100% sure somebody doesn't have a top secret algorithm. But to the best of mainstream knowledge, yes, the encryption is fine. But watch out for quantum computing next decade. That has a chance to make today's encryption breakable.

Fair point. But it's a gray area because "should" only gets you so far. At some point, you have to start assessing their design against what's actually happening in the real world. I'd feel better about Signal's role in this if they made it clearer in their comms that they understand they shouldn't be used.