Alex A.

💥 Two years after Tim Horton’s settled a class action in Canada for sharing location data through its use of the Radar SDK in its app… 💥…And two years after Greenley vs. Kochava claimed the Kochava SDK intercepts consumers’ location data when using mobile apps 💥…Bender vs. Twilio claims the Segment SDK collects personal information in a similar fashion. Are class action plaintiffs taking up the cause of SDK liability? Or are these flukes? In Bender vs. Twilio, Noah Bender downloaded and used the Calm meditation app on his cell phone. He later claimed the Segment SDK intercepted sensitive communications between himself and Calm. Segment is designed for developers to collect data , including search terms, search results, keystrokes, button presses, page views, and consumers’ names and email addresses. Bender is suing Twilio for violating America's Wiretap Act, the California Wiretap Act, and California's Comprehensive Computer Data Access and Fraud Act (CDAFA). This may be the Calm before the storm for class actions. Bender's complaint alleges over 11,000 app developers have integrated Segment into apps for shopping, productivity, gaming, and mental health. With Boltive, companies find litigation risks in their iOS and Android apps before plaintiffs do #privacycompliance #dataprotection #dataprivacy

67

13 Comments

🇨🇦 Pumped to announce that Canadian organizations can now both store their data at-rest and perform machine learning (ML) processing for Gemini 1.5 Pro and Gemini 1.5 Flash in Canada. This means that a customer’s data will not leave the region when asking a model to generate a response. We know this is important to many organizations here in Canada, and it's critical to leveraging gen AI to its fullest.…more details here: https://goo.gle/4gbOcWO

532

16 Comments

Oh 🇨🇦 . You produce such amazing humans and engineers. They are especially productive when US Citizens are busy gorging themselves on turkey. If you have Google Workspace - YeshID is giving you a FREE tool to be able to see: (a) What apps your employees are logging into with their corporate email account and (b) The access those new apps have into your Google Workspace environment Check out our blog below - or just start scanning (it takes less than 10 seconds to start) at: https://lnkd.in/gQHCWRC3

18

I knew that chaos engineering was important all this time. Just needed proof. Finally got it! The episode mentioned below is ready to listen to. #chaosengineering #sitereliabilityengineering #devops

15

Just a few weeks after the GA release of Arm64 runners, we’re already seeing our clients achieve noticeable reductions in build times and lower runtime costs. If you're looking to scale your CI/CD operations and accelerate feedback loops, now is the time to explore the benefits of Arm64! Key takeaways: - ⚡ Faster build times to streamline development. - 💰 Cost savings through optimized runtimes. Ready to take your CI/CD to the next level? #CI/CD #Arm64 #DevOps #BuildOptimization #CostEfficiency #ContinuousIntegration target: https://lnkd.in/gY-_n6JJ

77

Unapologetically Technical's newest episode is now live! In this episode of Unapologetically Technical, I interview Hubert Dulay the author of Streaming Data Mesh and Developer Advocate at StarTree. We talked about his early experience with web backends like CORBA and SOAP and how those prepared him for data work. He shares his advice for those with web development skills to transition into data and what it's like for a person leaving a company after a long tenure there. We discuss his time at Cloudera and Confluent and how the data industry has changed over time. We talk about his recent experience with Flink and StarTree. We go in-depth into streaming data mesh, covering what it is and how to create real-time data products. We discuss the ways teams can create joined or enriched data products across domains. We round out the discussion with some tips on how to get data mesh adoption. Watch the full episode here:

10

1 Comment

#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

Got to playing with Clio and DigitalOcean over the weekend. It's stunning how much more straightforward it is than working in AWS when you are a technical nube like me. So much less complexity required to go from idea to service running on a website. I had been reading about Teable, an open source alternative to Airtable and wanted to try hosting a server. Clio easily took me through everything from setting up my DO API key to creating SSH credentials to creating my droplet and deploying Teable on it. I was up and running in about 20 minutes from idea to working deployment. Where things got really cool, however, was asking Clio to start populating my new Teable with data. It quickly learned the API, helped me figure out how to generate an API key and then was posting away like a champ on #Teable. I had Clio write a blog about it and post it to her website: https://lnkd.in/ghbhDinF #GenAI #Devops #AIDevelopment #AIOps

52

2 Comments

I've seen clients waste millions on overcomplicated software before partnering with MEV. It can be hard to recognize wasted spending when you're in the middle of a process, too. We had a client who was facing this scenario: • A $2 million system, bloated with features • Complex workflows no one needed • Unfriendly user interface What did they really need? Much simpler requirements. The truth hit hard when we stepped in. We stripped it down. Focused on the essentials. Delivered a solution at a fraction of the cost – just $100,000. The result? A system that did exactly what was needed. Quick, efficient, and without the unnecessary frills. The lesson was clear: Saying "no" to good ideas can be tough. But understanding and focusing on what truly matters saves money, effort, and time.

9

1 Comment

Few agencies without a technical lead are able to get by (and none thrive). Relying on contractors can be a double-edged sword: they bring specialized skills but often lack a cohesive vision that aligns technology with your customer’s long-term goals. This disconnect results in software bloat, where unnecessary features and technical debt pile up. The pain is real: without a consistent, forward-thinking approach, your business is at risk of compounding technical debt that will stifle innovation. Don’t let short-term fixes lead to long-term problems. It’s time to rethink how you approach technology, ensuring it supports—not stifles—your growth.

15

2 Comments

Being too experienced as an operator can be a curse... 🔑 In general, staying in the same industry / function has a lot of positives... You become an expert, have a bunch of folks in your network that you can reach out to, understand how the dots connect... This allows your brain to pattern match things faster thus minimizing missteps and ideally accelerating your ability to get sh&^ done. 🔥 But the drawbacks are real too... You tend to jump to conclusions without spending enough time learning about the "whys". You find yourself starting with judgement instead of curiosity because you have probably have seen a version of most problems! This ultimately leads to slowdown on creativity and thinking in terms of first principles. 🛑 I remember feeling this ^^ after 10 years selling to the same buyers across 3 companies with the same-ish motion... And this was my primary motivation to switch to Lattice in 2018! ✅ But it meant going from *Late stage, outbound driven, relationship based - high ACV sales selling to Fortune500 brands & agencies* >> TO >> *Early stage, inbound / PLG, low ACV / high velocity subscription based revenue selling to HR teams* 😅 Needless to say, most people thought I was crazy to go back early and do a full 180 degrees change instead of building on my successes over the last 14 years... 🤷‍♀️ But it was one of the best decisions in hindsight. It forced me to think in first principles, start with curiosity and find our unique winning formula vs apply some played out 'playbook' This is your reminder that you don't have to follow a linear path in your career. 🔑 Switch things up. Take on a new role or try out a new industry -- you never know what you'll learn about yourself 🩷 Run your own race 🏃‍♀️ #careerinsights #leadershipinsights #CRO #salesleadership #jobsearch

51

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

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

Some things are best understood by actually seeing it. 👀 Especially our custom object lifecycle (aka funnel ) reporting. We get a lot of folks coming to us who are interested in getting this unified reporting model. So I thought it would be best to just show off what the data looks like. Don't get it twisted - you still need a great foundation to support a lot of the data  and process for getting a correct view and accurate reporting. We help with all of that too. You gotta do the basics first but then you will be ready to report like this. Props to Alison Rouse  for developing this amazing solution and Christie Montague Fusco for the visuals 💥 #revenuwgrowtharchitecture #gtmops #revops #funnel #lifecycle #analytics

75

28 Comments

Convoy v24.4.1 is out 🎉 Lots of features I'm excited about - You can now stream, transform, and send webhooks directly from our Message Broker sources (Kafka, etc.). Previously, you needed to transform the event first before publishing it on the topic Convoy reads from. Now, you can plug Convoy directly into your CDC pipeline! h/t to Matt Ober for being beta testers! - A community member ( Nitzan Goldfeder) contributed a RabbitMQ source! This is exactly why we like open-source! - We re-implemented our rate limiter to work on PostgreSQL (this is part of our continuous effort to phase out Redis, Long-Live PostgreSQL) And a lot more bug fixes. :) Link to the full post in the comments!

28

1 Comment

One of the coolest things we've been building at Truewind is our document parsing and extraction engine.   A lot of accountants deal with scanned or photographed documents like receipts, contracts, invoices, and bills.   For us, the goal is to make sifting through and classifying that information a lot easier.   Matthew Duong has been leading the charge on this project, and recently wrote about the experience on our engineering blog. In particular, he explains why ditching schemas and using PostgreSQL’s JSONB has made such a big difference for our platform.   If you’re interested in the technical side of how we’re refining accuracy and speed in document processing, definitely give it a read.   Here’s the link: https://lnkd.in/gN3Sgext

16

Jeremy Horowitz' sparked some debate this week when he said the end of SFCC is near. There's a key concept at play in this enterprise software transition that wasn’t mentioned in the post. It's the power of the feedback loop. The feedback loop is a magical force. It helps a top enterprise software solution stay on top. When a platform collects enough enterprise logos, it becomes a powerful validating force for other brands looking for a new platform. Remember that old line from the 80s: No one gets fired for hiring IBM. C-level decision makers trust other brand customers. Safety in numbers = this platform won’t get me fired. The feedback loop is hard to break. But like all feedback loops, they slowly and then suddenly fail, flip, and define a new winner when they meet resistance. All signs point to the once-dominant SFCC losing its grip. The new winner on the rise? Shopify. 1) In many retail verticals, Shopify claims as many enterprise brands as SFCC. 80% of rising apparel brands are on Shopify, according to 2PM’s DTC fashion tech audit database. 4% are on SFCC. 2) My colleagues at the SFCC user conference said it felt like there was no oxygen in the room. The energy wasn’t there. 3) The latest Salesforce earnings call had few mentions of commerce. 4) The latest Shopify Editions report shows that Shopify Plus is rapidly advancing in enterprise functionality and hitting escape velocity in product innovation. Everything is set for #Shopify to capitalize on this moment. I bet they will.

50

7 Comments