Dominic Goulet, MBA

#Fintech organizations have 3 main NEVERS: NEVER want to see downtime NEVER default on regulations NEVER miss a chance to know their customers But achieving this at scale = Ingesting TBs of data = spending millions of $$$ on SaaS observability tools = sharing financial/PII data with vendors = compliance issues This simple yet straightforward (+ extremely costly) gap This is where Incerto’s Observability solution comes in = Single unified platform, custom-built to your infrastructure = 85+% guaranteed cost savings + 100% control = #OwnYourObservability Still on the fence on making the switch from SaaS observability? You’d surely want to hear from our clients from FYERS, Dhan, and other leading orgs. #observability #financialservices #monitoring

21

Example 1. A Convoy as a Distributed Team. There are two agents in this example: Alice and Bob. Bob wants to go home after a party, but doesn’t know the way. He does know that Alice knows the way and that her destination is not far from his home. So all Bob has to do is to follow Alice. But that may not be enough. For example, if Bob sees Alice going down lots of side streets, he may infer that Alice doesn’t really know her way and abandon the convoy, leaving Alice to worry about where she lost Bob, and circling back to try to find him. And if Bob makes a momentary wrong turn, Alice might conclude Bob now knows his way so she can abandon the convoy and leave him to find his own way. While she is in the convoy, Alice has to drive differently, adapting her own goals. ^ A seemingly simple joint-task, like driving to a place together, involves a complex level of co-ordination. Invisible unless observed actively. Now a round of applause to anyone, who ever worked in a project that required atleast 2 teams to work together, that success is hard earned! #devops #changemanagement

4

Massive week for agent launches and funding. Here is everything that you need to know.🧵 1/ Mendable released teams, 2x rate limits, map endpoints, a more reliable and developer friendly API, and more. Nicolas Silberstein Camara + Caleb Peffer https://lnkd.in/gv9x8wmf 2/ Salesforce Marc Benioff + Clara Shih Agentforce launch. https://lnkd.in/gd2JTpf3 3/ Adept Workflow Language (AWL) launched to simplify the creation of AI workflows. https://lnkd.in/gkssiYUa 4/ Cohere launched an improved version of Command R/R+. It has a performance boost on agentic tasks. Sandra Kublik, Aidan Gomez, Nick Frosst, Jay Alammar https://lnkd.in/gcRZqF3E 5/ Magic launched a 100 million token context window. That’s 10 million lines of code, or 750 novels + a recent investment of $320 million https://lnkd.in/gbtVmVxU 6/ Bland AI announced $22M in funding.  Their phone agent can talk in any language, handle millions of calls, and never hallucinate. Isaiah N. Granet https://lnkd.in/g99-QgHt 7/ Jack Altman announced $4.4M in funding for Retell AI https://lnkd.in/gg_uXhtd 8/ $2.6M in funding for Agency! We’re building AI agents that are safe, reliable, and accessible to everyone. Alex Reibman shared how thousands of developers, startups, and enterprises rely on Agency every day. https://lnkd.in/gSbfx_2a 9/ Softgen AI has made building websites easier than ever! Marko O. Kraemer https://lnkd.in/gc_ViK3w 10/ An agent that will roast your website built with Composio, Agency, Browserbase, Ollama https://lnkd.in/gC-3yW9e 11/ AI Newsletter Summarizer: Karan Vaidya https://lnkd.in/gYzfsAxb 13/ MattVidPro AI about Lindy. https://lnkd.in/gR3xiCu2 14/ Mert Deveci ✊ shared a video I did with David Ondrej about the best AI Agents https://lnkd.in/ggKtB_Gv 15/ Abacus.AI AI showed off its software planning agent. https://lnkd.in/gq6FfXKR 16/ Angela Strange from a16z "Every white collar role will have an AI co-pilot. Some roles will be near fully automated with AI agents.” https://lnkd.in/gZpbMexe 17/ Klarna's AI support agent does the work of 700 employees, reducing average resolution time from 11 minutes to 2 minutes. https://lnkd.in/gq-ZZjmg 18/ Box CEO Aaron Levie on why AI agents are a $1 trillion opportunity https://lnkd.in/gujCcgAR Follow Agency and Adam Silverman (Hiring) for all things AI agent-related. Last weeks updates: https://lnkd.in/gkcVwyrX

64

7 Comments

Let's collectively say no to spamming each other, shall we? In EP 002, I chat with Software Engineering Manager, Laura Bélavoir, as she shares her journey from France to Canada, and Drupal to React. We worked together a couple of years back at Commure. She's now at Okta and in this episode we discuss hiring practices, learning Frontend Development, and interviewing preparation. The 24-minute episode drops this Saturday at 9 am PT, just like your Saturday Morning Cartoons back in the 90s 😀 P.S. Ben D. -- I meant to introduce you both months ago when we recorded this episode...🤷🏽‍♂️ and I am just now checking this off my backlog! ✅ ________ Hi, I'm Henry N., a Recruiting Manager and Jobseeker Podcaster. I crowdsource job search stories from guests on my podcast and turn them into custom Notion Playbooks at https://shorturl.at/HhRog // What's your job search story?

32

5 Comments

Episode 2 is live! Laura Bélavoir gives tips on nailing the interview with Software Engineering Managers and learning new skills in tech. Link to our 30-minute episode in the comments. Enjoy!

6

3 Comments

The story of Shopify & Ruby on Rails is perhaps one of the biggest commercial success stories in Open Source. What percentage of Shopify's market cap wouldn't exist if not for Rails? Let's say 20% of Shopify's $138.2B market cap as a benchmark. By that measure, $27.64B of market value gone without Rails. Now think about how massive the total value that would be gone in the markets if Open Source never happened – care to hazard a guess?

6

1 Comment

Not many people know the story of "why" Zenhub exists...so here it goes👇 Back in 2014, the team that would come to be "Zenhub" was a scrappy group of devs and PMs working at a product studio up in Vancouver. When clients are paying you to do work, they (rightfully so) want to understand where that work is at and “when is this going to be done?” The problem was that we could never answer that question… No matter what project management solution we tried (and believe me, we tried them all), we kept coming back to the same core problem. Context switching... Ie. our devs always felt like they were being forced away from where they were working from (ie. GitHub) in order to update our PM tools. So they didn't update them. Needless to say, this wasn't leading to a productive relationship with our clients. So our devs got together on a weekend to try and fix the problem. What they hacked together was a simple Chrome extension to bring a Trello-esque "task board" into GitHub. And as they say, the rest was history. Well, not really, but we’ll save that story for another set of posts… Reducing context switching has been core to our mission from day one. But while GitHub was the home for teams back in 2014, that's changed. Today that home is Slack. While I know people have a lot of mixed feelings about Slack, it has (for better or worse) become where “work” happens in most modern organizations. That’s why today, we’re announcing early access for an entirely new Slack integration that’s going to be a game-changer for how teams use Zenhub. While platforms evolve, that idea of “reducing context switching” has remained a constant, and we’re excited to double down on that mission with Slack. With this new integration teams will be able to create, plan, and track work in Zenhub all without having to leave a Slack channel. If you want to get hands on with what we’re building and join our early access program, check out the link in the comments below. #slack #github #developers #agile #scrum #projectmanagement #devex

62

9 Comments

When there is great uncertainty, there can't be predictability to any useful level. We have to reduce uncertainty to where it can be managed effectively, and we do this by running experiments... trying things. Does the stakeholder like what we've done? Does the customer like what we've done? Are we solving the problem that customers have? This puts us in the 'complex' quadrant of the Cynefin Model, where we have to try and (perhaps) fail, perhaps repeatedly, until we know enough. Yet, we still have a goal in mind and we at least know the first few things that need to get done... or the first thing we need to test to determine feasibility. Apple knew that unless it could source a ruggedized hard drive that would withstand being carried and occasionally dropped, the iPod would not be successful... so getting a commitment from Western Digital (who had been working on such a drive and was almost ready to ship) was the key decision point. The Wright Brothers knew that unless they could figure out a way to turn their airplane without 'skidding' and stalling a wing (a problem that had killed many of their inventive contemporaries) they couldn't build a safe airplane... oh, and find a lightweight, powerful-enough motor while you're at it. It all comes down to reaching decision points: do we know enough to know whether to continue, or whether to cancel our effort? In the example below (waterproofing a below-ground basement), we are going to have to continue. Therefore, we want to continue only at the pace at which we are certain of the decisions we're making. Is what we're doing working? If so, do more! If not, do something else. That is exactly what the contractor did in the post below, making 'MVP' experiments until the path to success was clear, until they had the 'Aha!' moment. So, when do we get predictability with useful accuracy? At the 'Aha!' moment. Figure out what 'Aha!' moments are needed, devise experiments to reach those moments and drive enough uncertainty out (you'll never get to zero) to where the range of uncertainty is acceptable. #predictability #forecasting #estimation #commitment #agile #planning #riskmanagement #projectmanagement

3

3 Comments

Are you ready to unlock the full potential of Product Operations? 🔍 Only 2 weeks left until Product Ops: 101 - Getting Started with Product Operations on October 30, 2024, led by Denise Tilles! With only 2 spots left, this hands-on workshop will give you practical tools to implement and scale Product Ops strategies. By the end, you'll have a clear roadmap to drive better outcomes within your organization. Secure your spot now: https://lnkd.in/exBcs2V5 🎟️ #productops101 #productoperations #productmanagement #workshop

15

3 Comments

I've known Tobi for over twenty years now. Right from the earliest days of Ruby on Rails, when he was building Snowdevil, which eventually became Shopify, to sell snowboards online. His first commit to Rails was from 2004, which improved the ergonomics of controller testing. Just one out of the 131 commits he made to the framework from 2004-2010 -- a record still good enough to be in the top 100 all-time contributors to Rails! But Tobi's contributions to Ruby on Rails extend far beyond his individual commits to the framework, creating Active Merchant and the Liquid templating system, or serving on the Rails Core Team back in the early days. With Shopify, Tobi more or less single-handedly killed the zombie argument that Rails couldn't scale by building the world's most popular hosted e-commerce platform and routing a sizable portion of all online sales through it. In the process, Tobi built an incredible technical organization to support this effort. Shopify employs a third of the Rails Core Team, developed the YJIT compiler for Ruby, and contributed in a billion other ways. They are without a doubt the most generous benefactor in the Ruby on Rails world. So when Tobi asked me whether I'd be interested in joining Shopify's board, I needed no pause to consider the invitation. OF COURSE I WOULD! But to be honest, it wasn't just a reflexive answer to service the gratitude I've felt toward Shopify for many years. It was also to satisfy a selfish curiosity to wrestle with problems at a scale that none of my own work has ever touched. Both in terms of the frontier programming problems inherent in dealing with a majestic monolith clocking in at five million lines of code, and the challenge of guiding thousands of programmers to productively extend it, Shopify deals with a scale several orders of magnitude beyond what I do day-to-day at 37signals. That's interesting! So too is the sheer magnitude of the impact Shopify is having on the world of commerce. While much of the web is decaying to enshitification and entropy, Shopify stores stand out by being faster to browse, quicker to checkout, and easier to trust. That's enabling a vast array of individual entrepreneurs and businesses to have a competitive shopping experience against the likes of Amazon, without needing huge teams to do it. It's always a delight when I find a cool store, and I learn that it's running on Shopify. As I spoke with Tobi about on the announcement show, this was really hammered home after I got into mechanical keyboards. Seemingly every single vendor of thocky and clicky keyboards use Shopify! And when I see that, not only am I sure that buying won't be a hassle, but I also know I'm not going to get scammed. That's the Shopify magic: Leveling the commercial playing field between some obscure keyboard maker and the consolidated titans of e-commerce. And now I get to help further that mission from the inside! What a treat. Thanks Tobi!

1,595

39 Comments

Atlas is integrating with Shopify today. But "integration" is a word that hides a lot of complexity. Here's what it really means for us: ~Real-time data sync. Every order, every customer update - it's all live in Atlas now. ~Context is queen. Support agents can see a customer's entire Shopify history right in their ticket view. No more tab-switching. ~Action, not just information. Agents can process refunds, update orders, and more - all without leaving Atlas. ~Custom fields that make sense. We're not just pulling in Shopify data. We're making it useful for support workflows. ~Search that actually works. Find any order or customer info in seconds, not minutes. Building this wasn't easy. Shopify's API is powerful but complex. We had to balance speed, reliability, and usefulness. But we know that it matters. A lot. E-commerce support isn't just about answering questions. It's about solving problems fast. Really fast. With this integration, we're speeding up resolution times. We're reducing customer frustration. We're helping support teams do more with less. That's not just good for business. It's good for everyone who's ever waited too long for a simple answer about their order. Next up: Making this even faster, smoother, and more powerful. The best customer support system in the world. Btw, check out Atlas for Shopify here: https://lnkd.in/gtkJgdsX

34

1 Comment

Ever wondered how to bring Shopify and Softr together to create something amazing? 🤔 I recently wrote about building a customer support tool by integrating Shopify with Softr using REST APIs. And let me tell you, Transformers are the real MVP here—they don’t just smooth the process, they make it possible! 🚀 If you're using Shopify and diving into the No-Code world, this post is for you! Would love to hear your thoughts and experiences with integrations. 💬 👉 https://lnkd.in/g2CQb7yS #Shopify #Softr #APIs #NoCode #CustomerSupport #Transformers

11

This is not new news. "What’s clear, however, is how powerful these online networks are. Vancouver’s public engagement systems, like those in many cities, lack the safeguards to detect or prevent potential manipulation. And when the same tech-savvy individuals shaping housing policy are also experts in digital systems, it’s easy to see how public processes might be influenced in hard-to-trace ways." https://lnkd.in/grny5jR3

10

Are you fully capitalizing on your Shopify store? As a Shopify App Developer, I often observe a host of challenges that founders face while operating their Shopify stores. I'm curious to understand the issues you're currently dealing with? 1️⃣ User Experience and Conversion: Designing a user-friendly interface that drives conversions can be complex. What obstacles are you encountering in this area, and how are you attempting to overcome them? 2️⃣ Inventory Management: Are you experiencing any difficulties managing your inventory on Shopify? What tactics or technologies are you employing to mitigate this? 3️⃣ Staying Motivated: Running an e-commerce site is not a walk in the park. How do you keep your spirits high during difficult periods, particularly when sales plunge or customer complaints skyrocket? Sharing our experiences and learning from each other is extremely beneficial. I'm eager to hear how you're addressing these challenges and might be able to provide some insights from my own practice. Do share your thoughts in the comments below. #Shopify #Ecommerce #DeveloperChallenges

7

Stop investing $$$ for the features, that are available already... For example: Most Startups don't need a full Payment backend... Mostly software startups offer the same pricing plans, Either they can be: ✅ Subscriptions ✅ Onetime Payment ✅ Pay as you go Models Engineers often jump in to build such systems thinking it as a simple feature to build. That ends up with 100's of expensive dev hours invested in it. Instead of developing that entire structure from the ground up, YOU can opt for a service which can help you solve that problem. Startups can use Stripe for such use cases. In your early days, you can use Even use Stripe's hosted checkout pages or can go ahead to integrate the Stripe's Card.js Library, which can enable to you get this done in a fraction of time. Once you scale up - You can choose to augment that feature into a hosted one (Only if needed). Using already available tools to solve the non-core pains of your software will help you Launch qiuckly while keeping things within budget - which is one of the most crucial aspect of a software startup. What other services you use to save your time during Software development, that can be added to this list? ♻️ Repost if you find this useful, and share with more founders. 🔔 I help software founders to take the best software decisions, for their product development. Follow me for more similar content. #startups #productdevelopment #softwareengineering

2