Yahui Jin

Last Tuesday, Malsgufa, our legacy CMS backend, was shut down. This milestone for BI's Tech and Product team culminated years of planning, effort, and execution. Malsgufa's first commit was on July 25, 2014, leading to 5,186 commits across nearly 30 repositories. Built and maintained by scores of engineers, its deprecation represents significant cost savings (20 production replicas, 3 instances of Solr, and an insane number of Zookeeper instances!), reduced security risk, and the elimination of an often-blamed boogeyman. The journey began in January 2020. Our challenge: moving traffic off Malsgufa without rebuilding everything in Muse. Initially, we tried GraphQL as an intermediary between Viking and our services, but progress was limited by Viking's complex Angular/Vue architecture. In January 2023, we pivoted to the strangler fig pattern with a shim. This approach proved far more effective – all Malsgufa traffic went through the shim first, with verbose logging to track unhandled requests. Meanwhile, we built Story Versioning API (SVAPI), incorporating lessons learned from Malsgufa's limitations around history and publishing states. We ran four major migrations (stories, custom pages, slideshows, and videos), building support in Muse and shimmed compatibility for Viking. Traffic gradually decreased from a torrent to a trickle, leading to the gloriously uneventful shutdown. Next, we will deprecate Viking by Q2 2025, unifying our users in the Muse ecosystem to create the industry's most innovative CMS. Special thanks to the entire Story Creation team: Chase Gruber, Chris Speziale, Daniel Arita, Danny Feliz, Dasha Lary, Dawin Camillo, Eric Saam, Frederica Chen, John Laslo, Kelly Filush, Morgan Cohn, Sarah Pai, Tyler Greenfield! Thanks also to DaD, Engagement, Helpfulness, Cloud Engineering, Test Engineering, and Operational Excellence! Finally, we recognize Malsgufa itself. Developed as a unified CMS backend to support Business Insider's expansion into new markets, it served our global newsroom reliably for a decade, publishing millions of stories despite no major changes in recent years. While it became less sustainable as our business evolved, it deserves our respect. Thank you, Malsgufa. May you rust in peace.

41

6 Comments

The Stoke Space team in Seattle has built a rocket company faster than many people can build software. Morgan Beller breaks down how this is helping them capture a huge opportunity: https://lnkd.in/gc5jv2-c 

28

2 Comments

How do you keep engineering teams aligned with business goals while embracing innovation? Ada, the world’s leading customer service automation company, found the answer with Jellyfish. When pivoting to a generative-first strategy, Ada faced a key challenge: balancing innovation with supporting existing customers. They needed clarity on how their teams worked and invested their time. With Jellyfish, they achieved: 🚀 A 14% improvement in cycle times 🎯 Ranked in the top 97th percentile for “days with commits” 📈 Over 10% growth in technical investments “Jellyfish has become our go-to dashboard to understand how we’re operating as a team at a glance,” says William Mora, Head of Engineering at Ada. Now, Ada’s team is striking the perfect balance—focusing on reliability, experimentation, and investments that drive their business forward. Read the full story. Link in comments👇

26

5 Comments

If you're running a data or AI-focused startup, connect with Stephan Goupille and his team! When three of the industry's brightest data minds join forces to back your venture, you get more than just funding – you gain invaluable operator expertise. They understand the challenges and opportunities you face because they've been there themselves.

6

While some folks hire entire Figma design teams for their personal websites, I'm here at 6:30 AM explaining to my partner why I need a third coffee to "write stuff." 2022: "I'll share monthly insights about building companies!" 2024: checking it -> Writing consistency matches crypto winter performance 📉 But look - AI got better at English faster than I got better at writing. That's what we call product-market fit. New strategy for 2025 - Actually write 12 articles - Convince partner these dawn coffee raids are essential business ops Track my progress (or lack thereof) here: https://lnkd.in/e6bkkxvH P.S. If my partner reads this - yes, this is exactly what I'm doing at 6:00 AM either wiring or reading the book. Note: Will open source my coffee consumption metrics in Q3 2025. Full transparency, like web3 promised.

30

1 Comment

In my experience of interviewing and working with many product leaders, a common trait among the great ones is treating their craft more as a science than an art. Delighting users, creating magical experiences, and ultimately developing software that users love to use is a science. An immediate red flag during interviews is when product leaders can't express details beyond "talking to customers" on how they build lovable products. While talking to customers is paramount, I listen for the structure and tools they use to become customer-centric and experts in the users they serve. Here’s what I look for: Methods to Listen For When Evaluating How Product Leaders Create Lovable Products: 🗺️ Journey Mapping: Understand what users do before and after they interact with your product or attempt to accomplish their job. 🔑 Key Moments Identification: Reveal the key moments that matter in the user journey. 😌 Emotional State Awareness: Understand the emotional states of users and how they change as they progress through the journey. 📊 Data Collection and Analysis: Collect and analyze data to understand funnels, drop-off rates, attrition, etc. I’m also on the lookout for specific techniques on how the product leader builds high-performing product teams. Here are some of the practices to listen for: 🏆 Recognition and Rewards: Establish clear KPIs that define success, create accountability, and drive alignment. Implement a system for recognizing and rewarding team achievements and individual contributions. 🤝 Consistent 1-on-1s: Conduct regular one-on-one meetings to mentor and guide the career and development of the product management team. 👥 Team Collaboration: Allow teams to craft their process and evolve it over time. My favorite team performance ceremony is the retrospective, where the team can gather in a safe place and collectively define how they will improve. 🔄 Cross-Functional Alignment: Create alignment between product, engineering, sales, marketing, and leadership. This involves regular cross-functional meetings, transparent communication of goals and progress, and a unified vision that ties the efforts of all departments together. Ensuring that all teams are moving in the same direction is crucial for driving consistent and sustainable growth. Overall, there are many important items across both themes that define effective product leadership. By listening for a product leader who employs these structured methods, companies can make a better hire to turn insights into actionable strategies, ensuring that the user experience is not left to chance but meticulously crafted and continuously improved, while building and managing high-performing teams that drive success.

17

4 Comments

A handy visual guide for Product folks about to contemplate and communicate, well, just about anything. As with so much in our domain, simple at surface, elaborate to execute, but priceless when proper.

16

4 Comments

After 10+ years working with early-stage startups it’s fair to say I’ve seen I’ve seen some things (& some things I will never unsee), learned some things, earned some stripes, some scars, and some measure of expertise (one hopes) helping more than a dozen startups find product-market fit. While I’ve enjoyed year-long runways at well-funded startups that were eventually acquired, or went public, or very publicly imploded—what really taught me the real meaning of Lean startup was working with self-funded founders who had ten compelling concepts but resources to build one. When you don’t have a year to be wrong; you learn to get it right very fast. If you are a founder facing your own set of high stakes decisions & tradeoffs; we can help. For free. You can book a 1 hour chat with us to talk through all the things racing through your head. We know what’s involved in getting something tested, validated, and built; this is what we do every day all day. We might not have all the answers but there is a good chance we can give you some clarity, some calm, some options. Call us at 1.844.4FLAGRANT or DM me. And if you want to get a sense of what we are like as hoomans- check out our Delightful Reveal series. It’s all the things we have been reading, watching, listening to, & enjoying. https://lnkd.in/gfrz9tQS #startups #entrepreneurship #socialentrepreneurs #innovation

32

5 Comments

At InVision, we worked with some amazing software vendors. I know I've talked about most of these in the past; but, I just want to give a final shout-out to some of my favorites: * LaunchDarkly - feature flags completely changed the way we approached product development. And, allowed us to all but eliminate our incidents and outages (shameless plug for my own book: https://lnkd.in/ehxiy6bY). * Postmark - delivered all of our outbound emails and powered our inbound reply-by-email workflows with flawless uptime and befuddling performance. * Pusher - powered our real-time collaboration via WebSockets, bringing our UIs to life and keeping browsers synchronized. * Intergral | FusionReactor APM - gave us deep insights into our JVM performance, allowing us to track down SQL, API, and processing bottlenecks. * Datadog - truly world-class metrics, alerting, and monitoring. * Adobe ColdFusion / Lucee CFML - the programming language and application server that allowed us to move fast, keep things simple, respond to users, and build wonderful things. * Cloudflare - your CDN, WAF, and web workers took a beating so that our origin servers could stay online. * Amplitude - connected me to the users by giving us insight into what our users were actually doing (or not doing). At one point, I think we had over 300 different SaaS subscriptions; so this list is faaaaar from exhaustive. And, I'm sure I'm forgetting other beloved services. And, many of our teams worked with entirely different technologies. This is just my little corner of the organization. And, I couldn't have done it without them. Thank you so much! ❤️

113

18 Comments

Ever wondered where the perfect balance between tranquility and innovation lies? For me, it’s Seattle. Unlike the Bay, Seattle has a more serene environment that’s perfect for focusing on building products and businesses. The city’s vibe encourages deep work and creative thinking, free from the overwhelming hustle. But let’s be honest, Seattle’s founder and investor communities aren’t as vibrant as those in SF. Yet, this city holds a special place in my heart – a blend of my love for startups and the charm of Seattle. I believe in Seattle’s potential and I’m on a mission to help ignite its startup community. From connecting with fellow founders to engaging investors, let’s come together to build something extraordinary here. Seattle has all the ingredients to be a startup hub – talent, innovation, and a supportive ecosystem. What it needs is a spark. Let’s be that spark.

1

I've been interviewing a lot of people, so I get some variant of this question a lot. What does Remi actually do? I explain our unique business model & opportunity in my latest post. https://lnkd.in/gswR5anB

13

2 Comments

Making progress on my sprint for Maria Gabriela Ochoa Perez Waechter's YIBL-BAM. On to STRY0006--adding a top level (L1) navigation link to create a new contact. I jumped back into the core UI and dug up tables and got it working, but it turned out it is much easier with a nice UI in the Experience's advanced settings. Typical for me! On STRY0007, I was adding a pre-configured list filter to show me contacts to whom I have not yet out, reached (???). This is the main list of lists you see in the left hand nav and it's very common to want to change these. In the old UI it was a right click and a couple of records, but this one had me scratching my head even though I had done it before. I found my way back to the UX List table, which has more checkboxes than almost any form I have ever seen (Literally 1 Million Checkboxes https://lnkd.in/g9Nv7ivi), but hey, I'm not here to judge. Is there an easier way? Probably, but I couldn't find it so I don't care about an "easier" way, just as long as there is "a" way. Thanks MGOPW! #ServiceNow #ServiceNowDev #YIBL #BuildAlongMonth #UIBuilder https://lnkd.in/g65v22J8 https://lnkd.in/gKM3pi-i

8

Three Wins I Hope Every Founder, Builder Experiences 1. Hands-On with the Cool Tech Nothing beats diving into promising tech and seeing the impact firsthand. Getting up close with foundational models and LLM applications over the last three years is an experience I hope everyone got a taste of. 2. The Magic of an Aligned Team Being part of a team that’s not just smart but also daring greatly and committed to winning together - that's the best. A great mix of people bringing purpose, energy, and good vibes. 3. The Win of Creating Real Value Watching ARR take off, seeing customer value grow significantly, and knowing your work drives real impact - that's amazing. ----------- Looking back on the past three years at everc, I'm grateful for all that and more. From the hands-on work with LLMs to the friendships, amazing memories and lessons — What a ride. Together, we tripled ARR, drove significant customer value growth, and built a product group focused on speed and impact. A big thank-you to everyone who made this journey special ! Keep on keeping on — daring greatly, building, pushing forward, and inspiring each other. So long, and thanks for all the fish 🐟🐟🐟 ----------- What’s Next for Me? Exploring: • Zero-to-One LLM app product opportunities • Fractional product roles in early and mid-stage startups Who are the startups you know that could use an expert product hand to drive significant impact quickly?

67

16 Comments

Big news from WeaveGrid! We are excited to announce that we have raised $28M in strategic funding led by Woven Capital, Toyota's Growth Fund. I came to WeaveGrid three years ago with the goal of building a real ecosystem of OEM partners to create a more efficient grid full of EVs. Today we're taking that one step further in announcing investment from the world's largest automaker, Toyota Motor Corporation. With this strategic round fundraise, I look forward to continuing to scale our solutions across brands, utilities, and geographies, allowing us to support grid resilience and enable widespread EV adoption. Consider the grid… WOVEN 🪡 ⚡ 🚘 Woven Capital 🤝WeaveGrid = #WovenGrid #electricvehicles #ElectricFabric #climatetech #sustainability #energy

71

6 Comments

"Early-stage startup" and "maternity leave" sometimes feels at odds. Many parents opt for the big companies during their parental leave years, but I've taken three maternity leaves at early stage startups. As I transition back into full-time work after this last parental leave, I took some time to reflect on how the three leaves I've taken have been similar or different. I hope it is useful to others! (link in comments)

41

7 Comments

A clear articulation of Elon’s clearly stated direction at Tesla re/ working in the presence of one’s teammates in the office, on the factory floor, etc. It’s simply a matter of optimizing productivity, creativity and results, in my experience. That’s doesn’t mean there aren’t workable exceptions for some companies. It’s a choice. His choice is clear. My point? “choose carefully and wisely”. It’s really hard to push on this ime. It’s way harder to have the market put us out of business because someone else slept on the factory floor to drive results and we chose not to. 🙏🏼🇺🇸🚀 https://lnkd.in/gK8Xaven

9

These are some great thoughts on engineering metrics; I agree with much of this. Metrics have always been a great way for me to identify areas for conversation within the team itself and as an engineering executive looking across teams.

7

2 Comments