Rishab Hegde

Here’s another interview question I like to ask when hiring for Amplemarket. 👇 “What piece of common wisdom in your field do you disagree with?” It could be anything: A technical best practice you were taught early on and have since moved away from. An industry trend that everyone’s obsessing about but you see as a red herring. A conventional strategy you’ve challenged and adapted to unlock new opportunities. You learn a lot about a person by learning what they disagree with... ...and also in how they communicate their disagreement . But it's also relevant to Amplemarket's culture: We constructively disagree We challenge conventions We ask “why?” And we go back to first principles. We can’t build a great platform or a winning pro-sports team by copying what’s out there! We're challenging the assumption that finding and connecting with your perfect buyers has to be hard. Or that it has to take hours of manual work. Or, of course, that the SDR role is dead. 😉 (No, it's not! It's evolving. 👊 ) So: what industry conventions or trending knowledge do you disagree with?

40

7 Comments

We like writing engineering content Our engineers are at the center of what we build and our accountants experience. We're defining what AI-native looks like for accounting. We like writing engineering content because we want engineers who join us to know how we think about problems. This week, our very own Matthew Duong wrote a piece on Single Sign-On (SSO), breaking down the essentials and actionable tips (link in the comments) For founders, improving the login process and making it easier to access your platform means a simpler experience. For enterprises, it means reducing the number of passwords users need to remember, reducing the risk of security breaches. Shout out to Amer Taleb who joined us recently and took our content game to a new level. We have a lot more coming soon: new product features, employee spotlights, and our view of the AI Accounting space. Happy Friday from everyone at Truewind!

36

2 Comments

I cancelled our team's subscriptions to Github Copilot & ChatGPT after 10 days with Cursor 🌟 What Sets Cursor Apart Seamless Onboarding: The transition was remarkably smooth, reminiscent of Chrome's early days. Cursor's team clearly understands that muscle memory can be a significant barrier to adoption, and they've crafted an onboarding experience that makes the switch a delight. LLM Flexibility: The ability to switch between different Large Language Models, bring your own, or use the default Claude 3.5 Sonnet is a game-changer. This flexibility proves to be a massive advantage, freeing users from being tied to a single AI model. Multi-file Editing with Composer: This highly anticipated feature delivers 80% of the time, and when it works, it's phenomenal. It explains code changes, shows inline diffs, and allows for selective application of changes. My favorite one - https://lnkd.in/g4aYJbJQ. Contextual Awareness: The ability to @mention files, folders, and invoke web searches has transformed how I approach parallel feature development. It's like having a hyper-aware coding companion. Intelligent Auto-complete The tab auto-complete function is surprisingly powerful, working seamlessly across lines and files. It often feels like it's reading my mind, significantly speeding up coding sessions. Smart Inline Editing Cursor's understanding of the existing codebase shines in its inline code editing capabilities. It's prevented me from creating redundant utility functions by suggesting existing, similar functions—a huge time-saver. 💡 Pro Tip: Embrace smaller, more frequent code iterations. Commit changes often; you never know when you might need to start over on a change set. 🔧 Areas for Improvement Composer occasionally has UI glitches, taking over the entire window or hiding its title bar. Familiarizing yourself with keyboard shortcuts can help navigate these issues. Sometimes there's a disconnect between Composer's suggestions and what it displays. 🤔 Is Cursor Worth the Hype? For me and my team, it's a resounding yes. We're transitioning to Cursor as our primary development environment. I've noticed a significant reduction in my use of standalone AI consoles like Claude or ChatGPT, as Cursor integrates these capabilities seamlessly into the coding workflow. 🔮 Looking Ahead This shift to Cursor is part of our broader strategy to embrace AI-native development practices. I'm excited to share more insights in future posts about how we're leveraging AI to enhance our development processes. I'm curious to hear from other developers: What are your favorite Cursor features or hacks? How has it impacted your workflow? #DeveloperProductivity

22

4 Comments

Immersive agencies have a major advantage over other tech agencies: Nobody can solve client problems with emerging tech like you can. And absolutely nobody has the stories to tell that you do. Old Reese’s Peanut Butter cup commercials used to have a pair of phrases: “You got your peanut butter on my chocolate!” “You got your chocolate in my peanut butter!” And then the catch phrase: “Two great tastes that taste great together.” That’s immersive tech and … anything. Your agency isn't just working with AR and VR. You’ve also got customers exploring: – Haptics – AI (obviously) – Edge computing – UI/UX innovations – Volumetric capture – DevOps integrations Immersive agencies are transforming entire industries. Tell your stories about the problems you’ve solved in: – Manufacturing – Architecture – Medicine – Training – Safety – Retail You could be a web agency talking about how you added AI to your CMS. *snore* But you're not. Embrace the fact that you’re creating the future. And don’t be afraid to talk about how hard it is (because it is). I'll be sharing some writing prompts and opening lines just for you on Monday. ↳  Follow, bell, you know the drill. ------------------------------- I'm Jason and I never click the "Rewrite with AI" button. DM me if you run an immersive agency and want to turn your story into leads

45

3 Comments

Kyle Poyar's excellent post on Lenny Rachitsky's newsletter today contains a ton of great info for any product leader to noodle on (link in the comments below). One thing Kyle and I were talking about that I saw at both Hootsuite and SecurityScorecard was looking at a company's "in-app expansion & paywall strategy," especially in B2B SaaS within the first 90 days of joining an organization. I found that many organizations either lack a Paywall Strategy completely or are way too aggressive with one. In the past, I've definitely found myself too aggressive with my team to push upsells, but having a balancing act between making sure you're deriving value from features that customers care for without being annoying is supercritical. For those who don't have one, you're leaving money on the table, and it's time to change that! I find it's as simple as ensuring PMs and PMMs spend some time during Product Discovery on pricing and packaging but then bring that to the Product Design team to do their magic on how the paywall will interact with the UX. The latter is often missing and left for someone to do on Pendo or Appcues. #productmanagement #pricing #productmarketing

23

4 Comments

Have you ever thought about how compliance laws are a lot like design systems? I recently spoke with Joe Toscano, founder of DataGrade, and he made a fascinating comparison. Joe explained how Brad Frost's atomic design methodology took an engineering approach to design: → Creating standardized elements → Templatizing them → Scaling them across a system This led to the rise of human interface guidelines (HIGs) from tech giants like Google, Apple, and IBM. But here's where it gets really interesting: Joe argued that privacy laws and regulations are like the ultimate HIG for product design. Just like how HIGs provide rules and constraints for design systems... Compliance laws set guardrails for what we can and can't do with user data. If we design something that isn't compliant, it doesn't matter how sleek the UI is. Legal requirements become the top-level framework we have to design within. That's what got Joe into studying laws - to understand this new "design system" for building products. So next time you're cursing a lengthy legal doc or trying to make sense of GDPR... Remember, it's all just part of the atomic design of compliance. — Do you agree with the analogy of compliance laws as the ultimate design system? Why or why not? Hear more of Joe's unique perspectives on the intersection of product, privacy, and law on the latest episode of The Minimum Viable Podcast.

4