Dalmo Cirne

Having a ton of fun writing an ORM for V2 of Case Kit. Typescript has such an incredible type system. I have autocompletion for column names, the ability to include relations, relations of relations, etc etc etc... all returning properly typed data (no classes in sight). It's been really satisfying seeing it coming together, and it's been great getting my hands dirty with some (relatively) complex generics. And to head off the obvious question… why aren’t I just using Prisma? Well there’s a couple of things I’m doing differently that I think are marginally better: there’s no code generation involved here, it’s just types (inspired by Drizzle); there’s no Rust binary you need to deploy, and it hews much closer to Postgres behaviour and syntax (the aim here is not to abstract away which database you’re using). But the real blocker to me using Prisma was that its extensions don’t support modifying queries of nested relations - a hard requirement for me due to the way I have multitenancy and soft deletes set up. It’s not shown in the video but the Case Kit ORM lets you write simple middleware that will be applied to every level of a nested query. Perfect for setting timestamps or adding clauses on tenant id or things like that.

21

My biggest takeaway from #ELCAnnual2024 last week was that trust and psychological safety are the foundation of everything we do. Whether I was listening to a talk on improving team velocity, product-engineering alignment, measuring performance, leading through change, or collaboration — trust was at the core. Without trust, your team will struggle to work through conflict.  Without trust, your team will become disengaged and stop delivering to its highest potential. Without trust, interactions will feel adversarial rather than collaborative. Here are 3 ways to build trust in your team: 1. Communicate the “why” behind decisions, rather than focusing on the “what”. 2. Start collaborating early in the process, asking for input and ideas on how to approach a project. Don’t show up with the solution and throw it over the wall to your team. 3. Address tension and conflicts directly. Working through conflicts builds trust because it shows you care about the relationship. What are your favorite ways to build trust on your teams? Check out all of the great resources from ELC: https://lnkd.in/gdZRuz-a

15

"Most people instinctively avoid conflict, but as Margaret Heffernan shows us, good disagreement is central to progress. She illustrates (sometimes counterintuitively) how the best partners aren’t echo chambers -- and how great research teams, relationships and businesses allow people to deeply disagree." I wish you very best thinking. 😊 #conflict #disagreement #management #leadership #diversity https://lnkd.in/dC6mcRQM

3

This is really great and resonates - thanks Bryan Solar for the link! Couldnt align more to this - why add YAF (Yet Another Feature) when you can refine, prune, and streamline a feature in your existing product offering... On the engineering side this is also beneficial as it is less Cognitive Load and more time to cover Engineering PASS (Performance, Availability, Security, & Scalability)

15

🧠Planning for agents One of the big limitations for agents working reliably is their ability to plan. I talk about that in a new blog post. Covers: - What is planning? - How to improve planning? - Generic vs custom cognitive architectures and more! https://lnkd.in/gwi3WAK3

217

6 Comments

Your most important outcomes as a PM will not be driven by you. At least, not entirely. For outcomes that truly matter to the business (revenue, retention, CAC...), your work needs to work in symphony with all the other departments to have impact. This was my key takeaway from Nick Boccone's Outputs vs. Outcomes workshop at #ProductTO last night. Outcomes are events. They can happen without your involvement. Outputs are actions you and your team take. Sometimes, they inform outcomes — but never on their own. It led me to revisit this recent podcast from Leah Tharin featuring Kyle Poyar; this might sound like "just GTM stuff" that doesn't impact you... but until you realize how the business engine works, and the role each department plays in that engine, you're very limited in the outcomes you can drive as a Product Manager. https://lnkd.in/gg3s28-R #growth #productmanagement

15

4 Comments

Familiarity Levels at Work, and Meeting Scheduling Novice: You are surprised by their calendar blocks Journeyman: You already schedule around their blocks Expert: You know why those blocks exist and when they are negotiable Elite: Already synced over chat

7

2 Comments

Building a reliable RAG system isn’t just about performance—it’s about trust. Matt Turk's blog post breaks down the importance of this for both technical and non-technical folks—highlighting how Cleanlab's TLM, paired with Pinecone’s vector database, delivers high-quality data retrieval, accurate, context-aware responses, and scalable performance to meet growing demands. 👏

6

Dropbox CEO Drew Houston on solving the biggest problem with modern work: “It's a thousand paper cuts. It's like, 'Oh, I can't find the thing I'm looking for, and now I've got 10 different places where my content lives.' The complexity has exploded, which means the idea of having one organized place for your stuff is further and further out of reach for people every day." Listen to the latest podcast episode of Working Smarter.

3

So true! In my opinion, every effort, whether it's new features or services, should include the creation of proper data and analytics to measure its effectiveness and adoption. The necessity of a feedback loop through telemetry and analytics cannot be overstated. It turns data into actionable insights, enabling iteration and refinement of the offerings. Without this, we risk repeating the same errors or just offering the wrong solutions. understanding the customers and having a constant feedback look is a must!

14

Many businesses claim to be tech companies—but are they really? 💡 In my latest Substack post, I delve into: The true definition of a tech company. Heuristics to determine if your organization fits the bill: Do you use data to drive decisions? Are you constantly automating processes to improve operations? Are technologists making strategic decisions at the highest levels? Drawing from my experiences at Carvana, we explore what sets genuine tech companies apart from those that simply use technology. #techindustry #innovation #leadership #datadriven #automation #techleadership #carvana

3

In this exciting episode of the Mob Mentality Show, we are joined by Kyle Griffin Aretae to dive deep into the nuances of Test-Driven Development (TDD) and the crucial concept of "Goal-Centricity" in Agile practices. Kyle breaks down why TDD is so much more than just "test first" and challenges common misconceptions about this used development practice. If you're a software developer, Agile enthusiast, or just someone looking to refine your team's development processes, this episode is packed with insights you won't want to miss. https://lnkd.in/gUV9Ffwc https://lnkd.in/gmXf6fJ7 Chris Lucian We explore why treating TDD as merely writing tests first misses the larger picture and how adopting a broader, more progressive approach can help your team build better, more maintainable software. Kyle shares his thoughts on the primary value proposition of TDD, focusing on **fast feedback loops** and the **refactor step** at least every 5 minutes. He explains how smaller, healthier TDD cycles allow developers to stay nimble and avoid the trap of feedback loops that last 30 minutes or more. Thus, when fast feedback loops with constant refactoring are in place as the foundation, then the "test first" aspect of TDD really shines. A key takeaway from this episode is the impact of **social programming**, TDD, and **CI/CD (Continuous Integration/Continuous Delivery) pipelines**. We explain the importance of the "Pipeline First" principle when writing new code. We then dive into maybe Kyle's most controversial take on TDD: the idea that creating a **mini-plan** (a rough roadmap of what to do next) before writing tests might actually be more beneficial than strictly adhering to "test first." This, Kyle argues, leads to more robust code when integrated into strong social programming practices. We also touch on the application of **Maslow's Hierarchy of Needs** to TDD and the importance of satisfying basic development needs (like fast feedback and clean code) before tackling more complex issues. The episode continues with a discussion on the intersection of **Goal-Centricity** and Agile. Kyle questions whether Agile methods are effective without first agreeing on a clear goal. We explore scenarios where goals are unclear or where methods are imposed without understanding the desired outcomes. Kyle shares a fascinating example of a code freeze during "Black Friday" and the unintended consequences of such decisions. We also reference a powerful quote by **Deming**, "A goal without method is cruel," explaining how the opposite can be just as problematic.

10

5 Comments

Head of People and intimidated by compensation? 😥 Hear it straight from Head of People at Immutable, Ami Patel, who was new to building comp practices too. What Ami found was that comp is actually: • Way more fun than you think (I can attest to this), • Great if you like solving ambiguous problems, • All about making the complex, simple. One tip Ami goes on to share is to not tackle this alone. Even if you’re standalone — use your network. Compensation is a universal language. Most of the things you’re solving have been tackled by someone else. At the very least use that network as a good sounding board to talk through what you’re thinking. In the end, it’s resting with you to help create pay practices that are competitive, fair, understandable and actually rewarding. If you’re interested in catching the whole conversation or hearing more interviews like these, check out the FNDN Series here 👉 https://lnkd.in/gT66zBjR

49

8 Comments

I'm still leery of calling today's AI "intelligent" or "reasoning", but I like how Perplexity is starting to experiment with how best to communicate the trade-off between quality vs. speed in the design of its in-product tooltips....

7

2 Comments

In this talk, #Couchbase's Ben Greenberg breaks down keyword, semantic, vector and hybrid search approaches. He'll explore how each method works, their advantages and disadvantages, and practical use cases 🔎

1

I appreciate intelligent discourse no matter how aligned it is with my thinking. This article is worth your time.

2

When innovation and leap-frogging competition is direly needed, the lack of technical prowess in mgmt layer is most acutely felt. Because, they often hold the most business context to match a business problem to a technical solution, having technical wherewithal is paramount. Don’t outsource the technical thinking to your team. Be that manager.

10

1 Comment

🚀 Excited to share my recent interview with Harry Guinness for LeadDev on Retrieval Augmented Generation (RAG) and its potential to tackle generative AI hallucinations. In the article, we discuss: How RAG enhances large language models with up-to-date data. Benefits in reducing hallucinations and improving AI reliability. Practical applications and cost considerations. Challenges in deploying RAG pipelines. Proud to highlight how RAG can help establish "ground truth" and build traceable citations, enhancing AI transparency and trustworthiness. Read the full article here: https://lnkd.in/gjarDhBX #AI #GenerativeAI #RAG #MachineLearning #ArtificialIntelligence #LeadDev #TechInnovation

10

1 Comment