Puzzle 🧩🚀’s Post

The buy vs build debate is timeless and exhausting. My default perspective is to buy unless you are somehow creating a competitive advantage by building. Software development is expensive and risky. Depending on the size of your organization, you may not be able to afford developing it yourself, especially when you calculate the total cost of ownership and not just this week's sprint. Make sure you are aiming your finite bucket of cash at whatever can bring your organization the most value. Building commodity capabilities yourself will never be cheaper and less risky in the long run. But my perspective aside, my advice is just make sure to do your homework first - options analysis, options analysis, options analysis. Let facts and analysis guide you. If there is any place you need to ensure the right debates and thinking are going into a decision, it is this one! #solutionarchitecture #enterprisearchitecture

New developers are at awe at how much code they write. Veteran developers are at awe at how little code they write. I see this time and again in many clients: - I’ve had one client whose “CTO” built their own message queue instead of using a proven OSS product… Sure it was cool and I geeked out about it but it was also an epic waste of time. That lack of experience cost the company $75,000 in direct time spent and probably $2,000-$5,000 monthly in maintenance costs that only the CTO could fix. - a dev agency built their own billing subscription system instead of using the many services out there. My client paid an extra $50,000 for a really really bad version of stripe. - another client had gotten their support system built from scratch instead of using one of the many customer service SaaS products out there… ———— Don’t build it yourself unless you have a good reason and that good reason should be backed by financial proof that it makes sense. Sometimes it’s just not fun being wise…. DM me and follow RedCorner if you think your devs are just wasting time and burning daylight. I offer a free technical assessment to give you an idea.

Started the day reading the interview from David Nunez who was leading the documentation team at Stripe. I had heard good things about Stripe docs from developers. This was a chance to hear something straight from the horse's mouth. Here are some of things I liked from the interview and my take on them. 1. Documentation should provide a smooth onboarding experience for the product. In my experience, it is a very critical aspect the technical writing teams should look into. Most people try out things before they make a purchase decision in the SAAS world. Once, one of the software architects mentioned that they have to evaluate 4-5 products in a limited time frame to recommend the best option. Hence, a good getting started plays a key role in product adoption if we can help the users to speed up their onboarding time. David is recommending different people in your company to go through the getting started experience, get the feedback, and fix any loopholes. 2. While extensive documentation is good to have it is very hard to maintain. We may have to trim it down because so many things change in a very short span. However, it is very hard to convince different stakeholders to agree upon remove the existing content. I have seen some of the features everyone thought critical in the initial stages of the product may not have the same priority or hardly any takers a few years later. Those content needs to be updated whenever there is change. For example, the underlying platform like Kubernetes may change key functionalities in their new release that requires a change in every feature. Link to the interview is provided as the first comment.

To $ or not to $... Kondo is currently free. Should it be? Why free: 1. Some embarrassing bugs show up every now and then 🐛 2. Got a few more cool features cooking before it's a V1 we'd be really proud of 3. Value feedback more than anything else. Don't want price to be a barrier to folks trying and telling us how it can be better 4. Haven't built a stripe integration yet 😅 Why $: 1. Product works and does everything it says on the box / landing page. 2. Some have told me unprompted that they'd pay $ for it as-is 😍 3. Got advice from other founders I really respect that I should just charge *something* for it to validate whether the pain is real enough for folks to pay for 4. Aligns the roadmap we're prioritizing to value that users would actually back with their wallets What should I do? (Also, pretty sure I'm just a noob at this and there's some canonical wisdom out there I should just follow on this but am missing. Maybe it's just No. 3 of Why $.)

During 2023 Stripe tools helped some of the world's largest companies like Slack Atlassian and OpenAI recover $3.4b in revenue and Stripe Billing helped businesses recover an average of 58% of failed payments. Reducing churn should be a top priority for businesses; it's 7x cheaper than acquiring new customers, helps boost revenue and maximizes customer LTV. Key to this is having the right infrastructure to enable businesses to identity and understand churn and recover revenues. Stripe has launched a churn management guide for subscription businesses to better understand how to minimize churn. We've also added new and improved features to Stripe Billing, from revenue recovery automations to advanced analytics. Find out more 👇 https://lnkd.in/eR-DHQgp

🚀 Exciting News! 🚀 We're thrilled to invite you to an exclusive webinar featuring insights from one of the top tech companies in the world, Stripe! Join Bunnyshell for "Behind the Code: Stripe's Secret Sauce for Enhanced Developer Efficiency" and dive deep into the strategies that have propelled Stripe's success. 👉 What You'll Learn: - How to enhance developer experience to accelerate software delivery - The benefits of scalable and reliable development workflows - Practical tips for boosting your team's efficiency and happiness This webinar is a must-attend for developers and tech leaders looking to elevate their teams and projects to new heights. Don't miss out on the chance to gain valuable insights and practical advice from the experts! See you there! #platformengineering #eaas #devops #bunnyshell #stripe

Powerful webinar with Stripe on Developer Efficiency. If you are leading / managing an SD team / teams , you should join!

Developer productivity is measured using information (entropy/entropy reduction) and described in bits (and not in the size of the files, but the descriptive uncertainty). The semantics of this differ, but fundamentally this is the most sane measurement, much like length, volume...etc. If folks are interested in the evidence and proofs we have of this, def reach out! #informationtheory #developerproductivity #kolmorogov #chaitin #work #techdebt

"Is it scalable?" Time and again, I've been asked if No-code can scale. Yes, it's scalable. Many successful companies use No-code and support thousands of users. But I prefer a different angle: Scalability is a problem for later. The real challenge is quickly validating your idea. And there's no better way to achieve this than with No-code tools, known for their lightning speed. We need to shift focus from scaling to validating ideas faster.

My team has been hard at work building the next generation developer experience at Stripe—so proud of them for unveiling a step change for people building on Stripe. Today, we're introducing three big new features: 1) Sandboxes: the next-generation of Stripe test mode. You can *finally* create multiple, isolated environments—handy for building a new feature, or just playing around with something new safely. 2) Workbench: our reimagined developer space, available everywhere in the Stripe dashboard. Inspect anything on the dashboard and get under the hood with the raw JSON in just one click. 3) Event Destinations: our webhook tools are evolving to make it easier to get just the events you need, and now delivering to cloud destinations for the first time. Check out the next generation of Stripe—and get early access—here: https://beta.stripe.dev