Florent Lamoureux

NEW: Internal Threads Internal threads allow you to spin up conversations in Slack from Pylon. It's great when you want to start a conversation with someone, but they primarily use Slack (e.g. engineers, product people or anyone who isn't living out of the support system). Common internal threads we are creating at Pylon: 1/ #bugs to report a potential bug 2/ #project channels to ask a team a question about a specific feature 3/ #feedback to report product feedback to the team It's been one of the most game-changing features we've released and we're so excited to share it with everyone. Enjoy!

44

3 Comments

Is this the end of embeddings? Hear from Josh and Tashrish on the pros and cons of using embeddings-based RAG for document data extraction and our experiments with switching to completions-only RAG.

5

I used to work with Ethan Eismann and always admired his passion for craftsmanship and high-quality experiences. My main takeaways: ▀ There’s a real shift today toward making enterprise tools as high-quality as possible, creating fantastic work environments for employees. ▀ The best companies focused on quality blend roles and phases of building. ▀ They don’t spend too long defining something; they make a bet and start building and shaping (planning and building blended) ▀ Engineers, PMs, and designers collaborate in the design process, working together to refine the solution through prototyping and feedback (blending roles)

109

5 Comments

What's the key to DevRel for AI products? 3 takeaways from Bear Douglas at Pinecone 1) Where DevRel lives in the org chart: If within product teams, DevRel is launching feature previews and ensuring developer feedback is integrated into product development. When positioned within marketing, the focus shifts to driving top-of-funnel growth through community outreach and relationship building. 2) Focus on impact: A key part of hiring for DevRel is understanding what the company needs and how developers will impact the bottom line. This helps determine if DevRel should focus on improving documentation, driving growth, or building a community of advocates, based on where it will add the most value. 3) Education: A big part of DevRel at Pinecone is educating developers on topics like vector databases, data ingestion pipelines, and optimal chunking strategies, and doing this across YouTube videos, screencasts, and detailed tutorials. For more, check out the full episode of Crossing the Enterprise Chasm (link in comments)

67

3 Comments

I'm excited to be back on stage at Dreamforce 24 (#DF24) this year! You may recall our previous efforts to extend rollup summary functionality for lookups. While those attempts faced limitations within the Core platform's architecture, we're thrilled to unveil a groundbreaking evolution: the Einstein 1 Platform. Join me and my esteemed colleague, Aneel Yelamanchili, for a captivating session. Witness firsthand how Copy Field Enrichments, leverages Data Cloud to seamlessly integrate data into your CRM objects. This innovation elegantly addresses the long-standing technical challenge of creating efficient and accurate rollup summaries on lookups. Through this session, gain valuable insights on how Copy Field Enrichments can: - Unify your data landscape by seamlessly integrating CRM data with Data Cloud. - Empower data-driven actions with enriched customer insights readily available. - Unlock the full potential of Einstein 1 Platform for enhanced data management and insight-driven AI. The result? Elevated customer interactions and tangible business success. Space is limited! Secure your spot and take advantage of a special 35% discount by registering with code D24DSPK835 at dreamforce.com. Let's revolutionize your data strategy together at #DF24! Date: Thursday, September 19, 2024 Time: 2:30 PM - 2:50 PM  Location: Moscone West, L2, Data Cloud Theater Session Code: 6460 Session Title: Unlock Potential with Data Cloud and Copy Field Enrichments #datacloud #salesforcedatacloud #GenAI

72

4 Comments

👩‍🚀 Fellow Tech People, we're exploring moving away from our custom API/websocket LLM interfacing at LEAGUES in favor of ELL. 🤔 The potential for streamlined API interactions, simplified prompt management, and reusable functions is really appealing. That said, I’m reaching out to the community: has anyone implemented ELL in production yet? I'm curious if ELL is the way to go for long-term scalability and maintenance reduction when interacting with LLMs. And what about Langchain—why choose one over the other? I'd love to hear your experiences and thoughts! #LEAGUES #ELL #Langchain #AI #TechInnovation

7

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

Everyone, today marks a significant milestone here at Sort. We've launched a new way for anyone in your company to help fix your data. We're calling this feature Sort Change Requests and it's available for you to try out on https://sort.xyz immediately. With Sort Change Requests, we've taken software engineering change management best practices and applied them to your database. If you are familiar with GitHub Pull Requests then Change Requests should feel familiar, except instead of modifying your codebase you are modifying your database. Propose your data changes --> have them reviewed by the data team --> then apply them only after sign off. If there's a problem during execution, the changes are automatically rolled back. 😎 Today's launch includes support for Postgres so if you're team is using a different database please let us know and we will prioritize appropriately. Give Sort Change Requests (beta) a try today and let us know what you think. -- Aaron

20

2 Comments

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

Awesome to see how our Pinterest Engineering friends take advantage of an almost *700x performance difference* between Honeycomb and their Develocity (fka Gradle) dashboards to find outlier users, old machine types, or use of specific JDKs. 🔥 We love seeing our customers use Honeycomb in all parts of their development process, leveraging our support for custom metadata (monotonically increasing, unbounded build identifiers are a perfect stealth example of high-cardinality data) and 💥speed💥 to deliver better experiences for their users. https://lnkd.in/eGcKeUvY

59

2 Comments

With Velt (YC W22) we provide features that boost engagement and growth within your product. You can add full-stack features like contextual comments, recording, notifications and more. You can fully customize these components. Make them feel native. Make them your own. Match your brand. Developers have full control: * Custom component layouts * Your own CSS * Dynamic template variables * Conditional component rendering * Custom behaviors and functionality * Component variants * Or build your own UI with our APIs. Learn more👇

29

9 Comments

Classifying transactions remains an unsolved problem. Seems like it's something that someone should've figured out by now. Yet, it hasn't. We've made huge strides on this front and we're publishing an in-depth article about our Classification Engine. Our very own Joel Ray Gregorio, CPA explains how we use AI to help firms dramatically improve their transaction coding. From reducing manual workloads to elevating accuracy, our engine is having a major impact on the way that teams manage financial data. Within the article, Joel covers everything from cleaning up messy books to smart predictions and broader scenario coverage. We also cover the 4 key benefits that Truewind customers – from top 100 firms to solo practitioners – have seen after integrating our engine into their workflows. 🔗 For the full piece, check out the link here: https://lnkd.in/dgJU8NKP

12

This is a cool project, and another example of the emerging "replace stateful storage with S3" trend. I do wonder at what point someone will package this sort of thing up into a FUSE filesystem to make it generally usable across existing services. Or maybe every service has unique enough needs that it's better to handle it custom each time. https://lnkd.in/etcVBfVf

9

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

Why we're leaving 70% of potential revenue on the table. And why it might be the smartest business decision we've made. After our $130M exit with Olapic, we had a choice to make with Remotely. The traditional playbook was clear: - Optimize for maximum margins - Scale rapidly - Raise significant capital - Keep pricing opaque Instead, we chose a radically different path with Remotely. We did something "irrational": showed our customers exactly how much developers make. In an industry where companies typically pocket 70% of what customers pay, we decided to charge a transparent flat fee (that effectively makes our take rate at 18%). Everyone said we were crazy. "You're giving away margin!" But here's what happened: → Customers started referring us to other customers → The best developers chose us over higher-paying competitors → We grew entirely through word-of-mouth while others spent heavily on sales 4 years in: - 300+ developers placed - $37M paid directly to developers - $25M in annual GMV - Small, profitable team - Still charging a flat fee And we’re just getting started :) We’re publicly documenting our journey and sharing our metrics on our newsletter, you can subscribe here - https://hubs.ly/Q02-mH5S0

13

Our Kids & Tech Guidebook launched today! If you have a kid in elementary school this book is for you. It lays out 10 practical steps to help you navigate tech choices for your kids. You can download the FREE guidebook at the link below in my comments. Super easy. Check it out!

27

2 Comments

🎉 Pendo Listen is now available on the Pendo One platform 🎉 Listen helps you turn customer feedback into actionable insights and build products your customers love. Listen enables you to capture feedback, validate ideas using Analytics and Guides, and make strategic roadmaps - so you can confidently prioritize your work and build products. Pendo is uniquely positioned to combine quantitative data (Analytics), qualitative data (Listen), and visual data (Session Replay) in a single platform. Best of all, Pendo Listen utilizes AI at every step to save you time and allow you to focus on what your customers need most. Learn more: https://lnkd.in/eTPR4HiQ

7

Great to see Marqo (and open source) featured prominently in the latest TechCrunch article on the role and rise of vector databases in AI. Although the hype, getting vector search into production is still very challenging. Vector search requires much more than vector similarity alone (i.e. a vector database) and needs to have the embedding -management, -orchestration, -inference and model (re)training. Vector databases get you vector similarity, Marqo gets you into production. Article: https://lnkd.in/gxNqeDXQ Github: https://lnkd.in/gsFRwZT5 Marqo: https://www.marqo.ai/

67

1 Comment

How do you share (or receive) product updates? What strategy strikes the right balance of frequency and granularity? When we first started Koala, we shipped changelog posts every ~week. BUT we've dramatically slowed down how often we share product updates, despite still shipping new features and improvements every single week. And I want to change that – there is simply too much value that customers (and lurkers) are missing out on! #product #startups #engineering

11