Romi Gubes

At Speakeasy we love working with devex leaders like Michael Heap to continuously raise the bar for what is "best in class" 🔥 We've been super lucky to work with him on what makes a great developer experience for iac and terraform. Come hear him and Thomas Rooney talk through how you can leverage OpenAPI and your API supply chain to build a provider and unlock the Terraform ecosystem. Link to the livestream in the comments 👇 #terraform #codegeneration #openapi

36

3 Comments

Shoutout to our amazing engineering team, led by Moiz Virani, who keeps such a steady pace of execution *and* a high bar of excellence. The results? This team is consistently sipping highly performant and actually useful features and products based on customer feedback. Excited to see that now our customers can : - customize the style of emails that are suggested after calls, either at a global org level or reps can define their own emails. - fully customize their own summaries, and define different summary styles whether it's a CS calls, active prospect, partnership call, etc. - login to our admin and web apps with multi-factor authentication - write summaries, signals and fields extractions into Google Sheets - integrate natively with Chorus - write summaries into Salesforce cases and yes, this is just the last 4 weeks of releases (!) Gearing up for 2 BIG product announcements soon but it's good to remember that a great product gets built week by week, making improvements along the way, and it all comes down to the team executing it.

49

2 Comments

New on the Review: Conventional wisdom teaches managers to avoid “anti-patterns,” general practices that are deemed unproductive, like micromanaging. But Will Larson, a veteran engineering leader and CTO at Carta, argues that not every anti-pattern is bad, and makes a case for the three that eng execs should explore: 🔍 1) Shying away from micromanaging. “New engineering managers are often advised to ‘step away from the code.’ But an extremely high-functioning exec understands the domain they are operating in at some level of detail,” he says. “As you get too far out of the details, you just become a bureaucrat. Too many well-meaning engineering managers end up as bureaucrats.” 📏 2) Pushing back on flawed metrics. “Often when people start measuring, there's always a concern that their measurement is flawed. And that's true for all functions,” he says. “But I’m a believer in measuring something imperfect, but useful, versus holding out for the perfect metric while measuring nothing in the interim.” ☔ 3) Serving as the umbrella for your team. “In the past, I used to think I was energizing my team by sparing them the details. But now it feels like lying to them,” he says. On a tactical level, Larson adjusted this habit by buffering less information. “That means even if it’s disappointing for folks, I’d rather them process news bit by bit, rather than deal with a huge ocean of mess all in one moment.” Link to the full article in the comments.

196

8 Comments

In November, we released a new product for SaaS companies called Census Embedded – it lets you embed our 200+ integrations directly into your application with a world-class API. We made our battle-tested connectors accessible to any developer. Since then we've helped companies like S&P Global, Metronome & Labelbox add these integrations to ingest/export billions of records. Today, we're making it easier than ever to implement with Embeddable Components. If the v1 was like Stripe's API, this launch is Stripe Checkout/Elements. Developing integrations is challenging because each API has varying requirements – different required fields, nuanced sequences of API calls, weird combos of CRUD operations, and more. We've spent years perfecting the transfer of data between 30+ data sources and 200+ destinations. We’ve solved scalability, reliability, observability, and UI quirks too! We’ve developed a sync and data mapping UI that accounts for the quirks in all 6,000+ combinations of those sources and destinations. Embeddable Components save you the hassle of reinventing the wheel in your own app. Offer your end users full customization of their data synchronization into and out of your app (or thoughtfully constrain those options).

97

6 Comments

At the beginning of this month, the infra team at Orb gathered for our Q2 infra offsite at HanaHaus in Palo Alto. Orb's customer growth in Q1 far exceeded even our optimistic projections — and is often the case in any org, this put a tremendous amount of load on Orb's infrastructure stack. Here's what is top of mind for our team as we look to the next few months: 1. We take uptime & reliability extremely seriously and have a strong track record of this — we proactively invest in our stack to avoid scrambling when issues happen. Over the last six months, we've invested in read/write workload isolation, more robust rate limiting, and making it much easier to spin up tenant-specific clusters of our core services and datastores. This has been a huge win already for our largest customers and in Q2, we're driving towards complete tenant workload isolation all the way from the API layer down. 2. Infrastructure often gets saddled with a really tough oncall rotation. At Orb, we share this workload across engineering with a larger rotation, but infrastructure owns the horizontal platform to make product engineers successful. In Q1, the infra team invested energy in aggressively making oncall better, and in the last month the number of overnight pages has dramatically decreased. Example investments include automated alerting and triage for long transactions and expensive queries. 3. When we first started building out Orb, we were careful to be pragmatic in where we spent energy with respect to scaling efforts. One of the choices we made was to use RDS Postgres as a job queue — although this has worked very well up to thousands of asynchronous jobs each minute, we've hit the EOL signs you'd expect (https://lnkd.in/gyQVEhKQ). We're spending time on moving to a different job queueing solution this quarter. 4. In Q1, we rearchitected parts of our ingestion and compute services to more aggressively pre-compute data, to avoid variable load through the API. We're finding that this is also going to help us ship much faster alerting features in Q2, enabling Orb customers to more efficiently power flows like spend management on Orb (without needing to pay for dedicated provisioning). If you're interested in joining this small but mighty infra crew, we'd love for you to apply (DM me, or look for link in the comments)

44

2 Comments

I spoke with Eric Ignasik and Michael Sols from The Software House about dealing with silos at work. 🎙️ We discussed how Technology Managers can help their engineers gain deep operational expertise and take full responsibility for product/feature delivery. The best practices I described in this interview come straight from Payhawk. It doesn’t mean they can simply be copied — but they might be inspiring to some. Happy reading 👋🏼 ➡️ hubs.ly/Q02xn9j-0 #softwaredevelopment #cto #softwaredelivery

152

4 Comments

Great essay by Omar El-Ayat and Nic Poulos. If you are a domain expert founder building vertical software, I highly recommend checking out Euclid Ventures as a first-check/ preseed investor.

12

1 Comment

Learn how PerfectScale + Karpenter can provide an additional 30 to 50% in cost reductions on top of what can be achieved with Karpenter alone. https://hubs.la/Q02ywfZ90 #kubernetes

7

How does Chronosphere achieve an actual uptime of 99.99%+? By using Chronosphere of course! In our latest blog post, Chronosphere’s May Lippert shows how she leveraged PromQL to craft actionable alerts tailored to our own environment and needs based on years of on-call cycles. Follow the step-by-step approach as she peeled back the layers of complexity, utilizing tools like Chronosphere's Query Builder and PromLens to debug and fine-tune her PromQL queries. More here: https://lnkd.in/gCexCtEF

59

1 Comment

During Dyn's scaling journey, we got several inbound investment and acquisition offers. We evaluated each one, and we kept saying: "No, we choose to keep the company." We had other growth plans, and those offers didn't make sense at the time. That's where my philosophy around preserving your optionality was formed. It's not this pessimistic, downside protection approach that some people think it is. It doesn't mean you shouldn't raise a ton of money or score a massive valuation or seek a huge exit. It means you should always maintain your ability to do those things — IF and WHEN they're needed to grow your business. At Dyn, because we preserved our optionality, we were able to say no to deals that didn't make sense. We eventually took in outside money when we were at scale (loads of secondary for founders!), and that helped put us in position to say yes to the right deal: Our successful acquisition by Oracle. When you over-capitalize and over-fundraise, you eliminate your optionality. You may have to say yes to deals you don't want to do — either because you have no other outs or because you no longer control your own company. So when an opportunity comes your way, always make sure you can answer "yes" to these 3 questions: Is this the best thing to do for our business? Is now the best time to do it? Are we able to do it?

62

2 Comments

Building WIN-WIN tech partnerships - how do we do it? 📌 Technical partnerships facilitate our growth Let's break it down how do we find them: Networking is our main strategy → finding connections via events or common communities. We prioritize quality over quantity, currently partnering with 10+ companies, including Triple Whale, Northbeam, Videowise, Social Snowball ☃️, Motion (Creative Analytics), Foreplay.co, Superfiliate, AdBeacon, and FERMÀT. Our selection criteria: 1️⃣ Our ICP overlap. 2️⃣ Our services complement each other. 3️⃣ We have good relationships with the founders/partnership team. 4️⃣ They committed to win-win relationships. 🔗 It’s all about finding mutual value & fostering relationships that help grow together. This is how we invest in and find the right tech partners. Let's connect and explore how we can create value together! 🚀

11

2 Comments

"Collaboration may sound straightforward, but it takes a lot of effort, communication, and focus to make it happen. And this need for teamwork is particularly true regarding making IoT technologies more seamless and reliable." Naama Zarfati, Augury’s Senior Product Manager for Connectivity, is sharing how she leads teams that align with each other and embrace best practices across the industry, allowing us to arrive at the next generation of IoT. Check it out here 👇 #IoT #Augury #IndustrialAI

8

💡64% of outcomes come from just 4% of causes This insight comes from recursively applying the Pareto Principle (or the 80/20 rule) which states that roughly 80% of outcomes come from 20% of causes. This can be seen in many different areas and disciplines - 20% of patients incur 80% of healthcare expenses - 80% of a company’s profits come from 20% of customers At Cruise, we employed this principle through continuous application of Pareto analysis, helping us work effectively towards improving the safety of the car. The idea is to rank occurrences of problems by frequency, and focus on the highest ranking issues first. By addressing just 20% of the top causes, you can expect roughly 80% of problems to be addressed. Additionally, by continuously applying this principle in a cycle, addressing the most impactful causes each time, you can achieve a form of exponential improvement, as each cycle’s improvements build upon those of the previous one. So when you’re overwhelmed by tasks and demands, just remember that if you focus on just 4% of them, you can achieve 64% of the results! With a little prioritisation and focus, you can significantly improve your output 📈

14

2 Comments

Business tasks I automated to save time, effort and cash and make sure the service was a great experience for my clients: 1. Onboarding once someone bought one of our programs *that sounds like one process, but Included: - Contracts being sent for signing with reminders if necessary - Payment collection and receipt delivery - Welcome email with explanation of what to expect as their next steps so they feel taken care of, welcomed and assured that they’ve spent money well - Login detail delivery to the membership area and clear instructions where to start, what comes next, and how to get support - Client’s first 1:1 session booked, details of the session and reminders sent - An intake form so everyone has clear records on the client to refer back to - with reminders if the client didn’t complete it This whole thing happened by pushing a single button. Then I automated: 2. 80% of delivery (I could work 10 hours per week and still bank $40K/month) 3. A process for nurturing every lead that came through the business - getting them ready to buy 4. Lead follow up to keep adding value and bringing them further into our world 5. Session booking with appropriate forms so the team coach had details before the call to prepare well 6. Client check-ins so we ensured everyone was happy multiple times through the journey so they felt cared for and we could ensure satisfaction These saved approximately a fuck load of time and boring repetitive tasks that I’d otherwise have to do or pay someone to do. I’m gonna show you how I did this on day 2 of my upcoming online training. DM coach if you’d like to do the same in your business.

4

Thanks for the insightful pitch strategies. When can I get a slot to pitch to you?

3

TimeRequest Automated Validation Rules are a powerful TimeControl function! Create conditional time off request approval paths right inside TimeControl.

2

1 Comment

📣 Elevate Your Social Media Game with Redis Solution! 📣 Ready to take your social media engagement to the next level? Redis Solution has you covered with expert strategies and powerful insights! 💡 Learn how to boost engagement with these essential steps: 01️⃣ Choose the right Platform 02️⃣ Search for keywords 03️⃣ Recognize the elements of an interesting post 04️⃣ Create unique content 05️⃣ Make powerful headlines 06️⃣ Determine the ideal time to post 07️⃣ Promote sharing And when it comes to mastering your finances, Redis Solution has all the tools you need! 💰 Reach out to info@Redissolution.com or visit Redissolution.com to learn more. #RedisSolution #SocialMediaEngagement #FinancialManagement #BoostYourBusiness #DigitalMarketing #ContentStrategy #EngagementTips #BusinessSuccess #FinancialInsights #MarketingStrategy #SocialMediaMarketing #DigitalStrategy #ContentCreation #FinanceManagement #BusinessTools #SocialMediaTips #MarketingTips #FinancialForecasting #Budgeting #CashFlowProjection #FinancialAnalysis #VarianceAnalysis #ExpenseBudgeting #SalesForecasting #DigitalEngagement #OnlinePresence #ContentMarketing #EffectiveCommunication #BusinessGrowth

1

I built a little productivity tool and it just went live on chrome web store🚀 Remember how Medhat Elmasry always gave us the emails and password to copy and paste when he taught us .NET? I was very tired of manually filling out sign-up forms every time (even if it’s copy pasting). So I built TestViper! It’s a little chrome extension which speeds up your workflow and save you a ton of time. 🔑 Key Features: • One-Click Autofill: Instantly pre-fill sign-up forms on your .NET web applications with a single click. No more repetitive typing! • Efficient Testing: Focus on what matters – your code. TestViper handles the mundane task of filling out forms so you can concentrate on development and testing. • Consistent Data: Ensure consistency in your test data with pre-defined email and password values. Avoid errors caused by manual data entry. 🧠 Why Install TestViper? • Boost Productivity: Reduce the time spent on repetitive tasks and accelerate your development process. • Improve Workflow: Simplify your testing routine, allowing you to focus on improving your application's functionality and performance. • User-Friendly: Designed for developers of all levels, TestViper is straightforward and hassle-free to use. 👇🏼 How It Works: 1. Install the TestViper extension from the Chrome Web Store. 2. (assuming you have your razor/mvc/blazor app running), navigate to the Register page of your .NET web application. 3. Click the TestViper icon in your browser toolbar. 4. Click ‘Fill With New Email’ and watch magic happens✨ 👋🏼Sayonara to the tedious task of manually filling out sign-up forms forever, download TestViper today and experience a faster, more efficient way to test your .NET web applications! ⚡ Download TestViper Here https://lnkd.in/gbd9S5G7 Would really appreciate if you could give it a try and leave a review so I know how to improve it🙏🏼 #buildinpublic

20

3 Comments

We're leveling up our content game at Fillout - first video guide below!

23

3 Comments