Adam Bard

3 reasons why we brought north of 25 meetings for our team this business week without any adspend or organic traffic. What we do have is our outreach, and let me breakdown why our outreach is so damn effective. 1. Data Engineers A genuine money printer with AI currently is prospecting in creative ways. Things like social media engagement, job postings, strategic hires, funding rounds, media articles… these events are all public data that we can feed to LLMs and do nice stuff… shoutout to Clay 2. Multi-Channel Outreach - 100% TAM maximum If you’ve used Sales Nav or Apollo, you’ll relalize not all contact data is available. Some people have emails we can find, phone numbers, LinkedIn, X… Well whatever channels are available, and there will be atleast 1, let’s tap it. Get the word across to 100% of your TAM with cold-calling, email, and social media DMs. 3. Relationship Selling Now this is an idea we’ve been toying with. This is the framework we use to write our copy, the message-market-fit. Be humanlike, cut the fluff, and cater to the prospect. “Hey <name>. I was Impressed by your practice. Wondering if you experience the following revenue pains…” We aren’t AI generating heaps of BS, nor are we wasting time with a story. Lead with value while retaining the conversational tone. Sales people are great. Data people are great. You need the best of both though 🚀

5

4 Comments

Thrilled to share with you what I've been building this quarter — the Amplitude Insights Digest! 💌 Each weekly digest email summarizes emerging trends within your key metrics (WAUs, new signups, retention, and more) along with highlights of the most-viewed charts in your organization. Pumped to ship this feature with my amazing team — Jacob Newman, Meredith Fay, PMP, Alan Lee, Brian Soe, Jessica Q., Armin Balalaie, Jeffrey Wang, and many others at Amplitude! #AmplitudeShipWeek

33

1 Comment

WAIT Are you telling me that now Shopify is using LLM's to make more simple the generation of GraphQL queries?? 😮 .dev Assistant gotta be one of the best features for developers from Shopify, you don't know how complicated it can be for someone to jump into GraphQL without previous knowledge (and the docs are not so easy to read for the beginners). This definitely will push a lot of new features and developments within stores! 🙌 🙌 🙌 This is an amazing way, and a very useful one too, of using LLM's instead of just adding a chat helper to your favorite instant messaging app 😅 Check a demo video from Shopify here! https://lnkd.in/eQcbUg2D #Shopify #ShopifyPlus #GraphQL #Storefront #APIs #LLM #FrontEnd #Learning #Lifehacks

7

1 Comment

🌟 Exciting times ahead! Next week, my team at Shopify will be coming together to “burst" in-person. This will be my first time meeting the majority of these super humans in real life and I couldn’t be more thrilled. Shopify thrives as a remote organization, but the value of in-person connection cannot be overstated. Meeting face-to-face allows us to build deeper relationships, foster trust, and enhance collaboration in ways that virtual interactions sometimes fall short. It’s about those spontaneous conversations, the shared laughs, and the energy that comes from being in the same room together. These moments of in-person engagement are integral to creating a cohesive and motivated team and will propel us forward in the months to come. I feel very thankful that Shopify believes this as well and allows us to prioritize opportunities to gather. I’m looking forward to the shared brainstorming sessions, meals, and most importantly, the connections we’ll strengthen during this time together. See you in Toronto! 🚀🇨🇦🙌 #remotework #engineeringleadership #distributedteams #remotecollaboration

36

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

Something you can’t do with Shopify flows’s native actions to make api calls is do anything with the response that you receive. Thats what this action in flow helper is for.

19

🧵 The Hidden Developer Growth Secret I Learned From Early Shopify Days (It's not about the tech stack...until it is.) In 2006, I was a young dev in Ottawa running IT services. One coffee chat with Aydin Mirzaee changed my entire perspective on building software. Here's what actually matters: Code Isn't Your Ceiling From: "I need to master the latest framework!" To: "Wait, these founders are teaching me how to think about problems" Learning how successful devs approached problems > memorizing syntax The Real 10x Move From: "Must learn every new tech!" To: "Must understand why this feature matters" Watching early Shopify's obsession with merchant problems taught me more than any architecture doc. Community Compounds From: "I'll just learn online" To: "These local devs are sharing real-world battle stories" Truth: Building alongside others beats watching tutorials. Growth Is Messy From: "Need perfect code!" To: "Need to solve real problems" Plot twist: Those local meetups taught me how to balance technical debt with business needs. Mindset > Stack From: "Ruby vs PHP vs Node?" To: "How are we measuring user impact?" The tech stack debate doesn't matter as much as understanding your users. The Hidden Truth: While everyone's chasing certifications... Real engineering wisdom comes from: Seeing decisions play out Watching products evolve Understanding user impact Building alongside others Sharing real failures What I really learned: Technical skills are table stakes Problem understanding is rare Community beats credentials Impact over implementation Measure what matters Want real growth? Join local dev communities Ask about failure stories Learn decision contexts Share your struggles Build relationships Because while everyone's copying FAANG architectures... Understanding why decisions were made matters more than the decisions themselves. What unexpected lesson changed how you build? Share this with a dev who needs to think bigger 👇 #DeveloperLife #WebDev #Engineering #StartupLife P.S. Great code starts with great problem understanding and the actual need. Everything else is just implementation details.

4

3 Comments

If you haven’t met Hamish McKay. Do it. Incredible. We have won a 5-star review on the app store every 3 days all year. Testament to the depth of problem Order Editing has solved for Shopify brands. Fewer support tickets, returns, and canceled orders. More post-purchase revenue and customer retention (long term). Often SaaS products try and dress up and look fluffy - Self-service editing and upsells ROI is so direct and on point! Review #132.

49

4 Comments

🚀 Heads up, folks! We just launched Zenie AI and Team Inbox, and things are about to get faster, sharper, and seriously efficient. With Zenie AI and Team Inbox, you can now: ⚡ Create campaigns that now build themselves faster than you can think 🎯 Segment so precisely that it feels like Zenie’s an expert mind-reader 📊 Unify and organize your data—no more “Can we get this from the data team?” emails. 💬 Manage all WhatsApp communications in one place with Team Inbox—say goodbye to scattered conversations Try it out today at https://lnkd.in/gf58UDJX 🚀 Here’s a video to see for yourself how Zenie makes busy work a thing of the past— https://lnkd.in/g59pafG4 #zepic #zenie

12

1 Comment

Sup fam!! Relationships are everything!! They're the core of your engineering platform. Your team's design docs, software patterns, pull requests, and GitOps workflows all need to pass through a complex network of relationships before becoming meaningful to stakeholders. Before that, they're just bytes sitting on Jeff Bezos' disks. How are your relationships doing? Which relationships need some light touching up? Which ones need some serious investment? How about that one person on that one team? How about on _your_ team? Are you tracking these gaps with the same effectiveness you're tracking tech debt? It takes an intentional effort to build meaningful connections and to show peers you're a stakeholder in _their_ success. It's worth your time -- not to mention you'll feel great!! Want to optimize your engineering platform? Start by investing in your relationships!

38

First day back at work in 2025! I’ve just spent some time diving deeper into the (New) Customer Accounts feature in Shopify, and I'm currently scoping out the migration for one of our clients. There are definitely some trade-offs to consider with the new system, and certain workflows will need to be adapted (like birthday capture, for example). But the good news is, there are already plenty of app extensions available to help bridge those gaps and enhance functionality. Check the curated list from Shopify here: https://lnkd.in/d2wCargV This will be a major focus for many agencies in 2025 as more businesses migrate to this new structure and unlock its full potential. 💡 #NamaStudio #ShopifyExperts

5

2 Comments

I don’t post a lot on LinkedIn. I find a lot of the posts are obvious statements of well known ideas or successes. I’ve decided to start posting on LinkedIn, to share, to vent, to find a little group therapy so to speak. I’ve been managing software engineers for over 10 years now. Coming from an IC background, making the transition from IC to a first line manager hasn’t been easy, but it has been rewarding. I don’t read a lot of books, in fact, just a few, and not really related to software engineering or management or the like. Most of my experience has been self learned, through failures, through mistakes; hard knox so to speak. I like leading a team, but don’t feel like a leader. I position myself as a team member on a team that has joint responsibility for success and failure. Leading by example when I can, and being led by others at times. Of course I get to make some of the decisions, but I rather see the team lead itself. It is more rewarding that way. What I find most intriguing is that one size does not fit all. The hardest part of managing is the people. Each person is unique with different experiences, different motivations, different ethnicity, different backgrounds, different home lives. You aren’t given a prebuilt team that is optimal for success. You are given the raw materials, some that are a good match for the job and others that need to be coached, developed, and nurtured. None of my team members ever took a compatibility test to determine how well they’d work with me or each other. Some are meticulous in the way they operate, some are “cowboys” (sorry for the gender team). Some can deal with ambiguity, the technical complexity, the problem solving, the scale, the quality, etc. Some need to be shown how to unblock themselves, how to find a way forward with little experience or the lack of confidence. Some flourish in an environment full of chaos, others struggle. What makes a puzzle interesting is that it takes different shapes and sizes and time to solve. Apparently there is a character limit on posts. This is my first post, it is raw and unfiltered (no help from ChatGPT). It probably lacks context and clarity, but might resonate with some. I’ll post a continuation in the coming days to help tie these thoughts together with other thoughts still yet to come.

110

9 Comments

Monitoring usage for Canopy AI has been interesting. Some people frame things super well and get great results. Others ask a four-word question, and somehow still get some okay results (just because we have a lot of content + I categorized everything for the RAG), but not always. We do some prompt augmentation, but we should do more. Currently, we inject things in certain scenarios or when it fails. Ideally, we would have a two-pass system for every request, where everything goes through a prompt improver. You can't assume users will ask the right things. All kind of obvious things I had already considered but left for a later version after initial usage. The cool part is this would've been hard to do last year due to speed/cost; now you can just "pipe" things multiple times using the same high-quality model you call at the end.

5

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

It's easy to forget how cool and extraordinarily unique (in the grand scheme) being a software dev really is... We have the ability to affect thousands of lives in a (hopefully) positive way with comparatively-low barrier to entry. A modest example: 8hr dev time saves 100 people 1hr a month for next 5yr... That is 8hr scaled to 6,000hr. What professions in the entire history of human kind have allowed this kind of scalability? Artist, writer, musician, entertainer - sure, but arguably more limited reach and higher barrier to entry. Other professions have this ability now, for example a teacher on Youtube with a million subscribers... but how did they get that ability? Thru software developers 😉. Enjoy it, dont let yourself forget how valuable you are.

6

Quick story time!📸 When RenoAssist approached me about building Canada's most comprehensive renovation directory in Webflow, I knew we had to get creative. Jack Hunter (their brilliant founder) had this amazing vision, but Webflow CMS alone just wasn't going to cut it. Instead of saying "it can't be done," we said "let's make it happen!" The solution? A beautiful tech sandwich: Webflow's sexy frontend (because we're not savages 😉) Xano doing the heavy lifting backend Cloudflare keeping everything fast and secure The results have blown everyone away: ✅ Lightning-fast directory searches ✅ Perfect URL structure for local SEO ✅ Real-time sitemap updates ✅ Smooth pagination that handles thousands of listings And yes, we still use Webflow CMS for the simple stuff - because sometimes the original recipe works just fine! Huge thanks to Jack Hunter for trusting the process. Sometimes the best solutions come from pushing boundaries! 🙌 Who else is out there pushing Webflow beyond its limits? Would love to hear your stories! #WebDevelopment #Innovation #ClientSuccess #nocode #webflow

28

6 Comments

With over 12 years in the Ruby on Rails ecosystem, I’ve had the unique opportunity to work across a spectrum of environments—from dynamic startups to large, established organizations. Reflecting on my journey, I wanted to share a bit about what I’ve been up to and what drives me. 🔍 What I've Been Up To: 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗳𝗿𝗼𝗺 𝗦𝗰𝗿𝗮𝘁𝗰𝗵: I've had the pleasure of taking projects from the initial idea all the way through to a fully operational product, tailoring solutions to fit specific needs and goals. 𝗧𝗲𝗮𝗺 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴: One of the highlights of my career has been assembling and leading teams for startups, fostering collaboration, and steering projects towards successful outcomes. 𝗔𝗱𝗮𝗽𝘁𝗶𝗻𝗴 𝗮𝗻𝗱 𝗜𝗻𝗻𝗼𝘃𝗮𝘁𝗶𝗻𝗴: Navigating diverse challenges and adapting to the needs of both startups and larger organizations has been both rewarding and insightful. I’ve always been passionate about leveraging technology to solve real-world problems and helping teams achieve their best. If you’re interested in learning more about my experiences or just want to connect and share insights, feel free to reach out! Reach out to connect or discuss experiences—I'm excited to engage with this dynamic community! #RubyOnRails #TechJourney #StartupLife #TeamBuilding #ProjectDevelopment #Technology

17