Replay.io’s Post

Your tech stack decisions should prioritise 2 things: 1. Quick delivery 2. Speed of iteration Your customers couldn’t care less about your tech stack or how hard you’ve worked. If you care, before your new idea has proven its commercial potential, you're an artist not a capitalist. That's ok but be honest with yourself.

PART 2 Unveiling the Magic: The Software Development Life Cycle 🌟#software Part 2: Our blueprint is taking shape! Designers sketch every detail—retro, futuristic, or wild west? 🎡 Choosing tech tools and design elements, they bring the carnival to life. Developers then build the grand show, followed by testing. Stay tuned for more! 🚀 #SoftwareDevelopment #STEAMspirations #TechJourney #Coding #DigitalMagic

God I'm excited for the next few months of stuff coming out of our product team. My version of the theme is "What you already know as an engineer, but with an easy path to 2.0 thinking". The product team have been on a kick recently around understanding where an engineer's head is at, and working out how we can do something that keeps with our unique selling point (high-cardinality, high-dimensionality wide data with super fast querying and navigation/investigation flows), but allows people to feel like they have some familiar so they don't need to switch mindsets immediately into an O11y 2.0 mindset. I'm totally here for it. I'm utterly giddy about the fact that you're all going to get to see it soon. Honeycomb for Frontend was the start of that (Think about RUM, but make it more useful as an engineering debug tool), but there's more coming. #observability #opentelemetry #debugging

Apart from Android topics, starting in 2024, I'll also be writing about engineering practices, tips, and team culture. I just published my first piece - "The Art of Shipping Faster", which speaks about a few cultural and technical tips to ship things faster, avoid stale PRs and merge faster. #engineering #teamculture

I saw a CTO on LinkedIn asking this recently, and even with years in the software game, pinning down a clear definition is like trying to refactor a legacy system—tricky, but necessary. 💡 Here’s my take: Technical debt is when you choose a solution that works today but may come back to haunt you tomorrow. It’s the trade-off between shipping fast and paying later. So, is this hitting the mark, or am I missing something critical? I’d love to hear how others in tech see it—let’s talk shop! #TechnicalDebt #SoftwareDevelopment #TechTalk #Engineering #Coding

What They Don’t Tell you About Building Tech Peoducts especially software products. Thought to share the process and effort that goes into building the products that we use today. Somethings I’ve learned the hard way, some in the process. I used to be that person that thinks building a successful product is just about being a badass engineer but it goes beyond that. As a user, I think this happens overnight. But I shared my thoughts in this article titled “What they don’t tell you about building Tech Products “ Didn’t go in depth product development, but this will be understood by everyone who reads it most especially if you are not in a product team. Have a read here; https://lnkd.in/ekbMkaTe Have a great Monday.

Upper Management: Trust me, this feature will make waves among our customers. Designers: We can take care of this in conversion; there's no need for 100 similar screens. Devs: Let's release this first and handle any errors if the customers notice them. QA: This feature is breaking the product. Should we release it in this cycle? Customer: We are so excited about what you will release next. PM: 🥲 👍 😅

When we're about to make changes or add new features, it's tempting to go for the quick fix or the immediate best solution. It's appealing to merge similar features based on their current behaviour and characteristics. However, identical today doesn't guarantee identical tomorrow. Features that seem alike now might evolve in different directions. As devs we shouldn’t just look at what works best right now, we might be hitting a local maximum. That means we're doing the best we can for the moment, but it might not be the best choice for later. Always keep the future in mind to avoid tricky decisions down the road.