Christopher Koehler

There's an oft-cited stat from Pendo that 80% of software features are rarely, if ever, used. While it's impossible to know the accuracy of that, it's not hard to believe. I've been part of multiple feature factories, where emphasis was put on new features to 'claim' rather than taking time to ensure we've actually solved the desired problem before moving onto the next. If you're a Product Manager/Leader in the Indy area, join us on August 14 for a conversation around best practices for measuring product success. We'll have food, drinks, and hopefully some great learnings! (Registration link in the comments)

21

3 Comments

Let's 🎉 celebrate 🎉 the fact that AFLAC users have the ability to use passkeys to speed their logins, improving the user experience, and reducing their customer service costs. But I can't overlook this quote: "Passwords are still in place for users who are not ready to move to passkey, or as an alternate path if needed." In other words, users are still subject to the risks of shared secrets. The security needle hasn't been moved in a material way and phishing resistance hasn't been achieved. Progress is good, but let's not oversell the benefits of passkeys in deployments when we haven't removed the risk of shared secrets or weak account recovery mechanisms. What do you think?

32

10 Comments

One of my favorite acronyms in #SoftwareEngineering is WTF - Where to Focus. When you have a small team you should focus as much energy as possible on the pieces that make your business competitive and buy everything else. I guarantee your cost estimate to justify building a tangential capability over buying it is missing a bunch of hidden cost factors.

4

Video from my recent talk is now available! Learn about how we're building our own developer tools to make frontend engineering fast and fun at Datadog

28

Does anyone else remember sitting in class thinking, "Am I ever going to actually use this?" 🤦‍♂️ I still ask myself this weekly when reading blog posts, listening to podcasts, catching up on massive Slack threads, or diving into documentation and feature listings. I don't always use the info, but it feels great when a memory from six months ago suddenly becomes relevant. I always think of that original Jurassic Park Unix scene. This often happens when discussing DevOps and Serverless, where boundaries blur already. Trying to keep all of the AWS documentation in my head while discussing the design of new features and optimizations feels like a superhuman task. What are some things you wish you had remembered when solving an issue or problem? For me, we designed a Lambda function to fail purposefully instead of attempting to recover for efficiency. Unfortunately, the Lambda control plane self-throttles a function once a failure threshold is reached... slowing our processing to a crawl and forcing some quick code changes. 😅 #AWS #lambda #serverless #learninginpublic #hugops

13

1 Comment