Sign in to view Beau’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Evergreen, Colorado, United States
Sign in to view Beau’s full profile
Beau can introduce you to 9 people at Infodash
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
2K followers
500+ connections
Sign in to view Beau’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Beau
Beau can introduce you to 9 people at Infodash
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Beau
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Beau’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Websites
About
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Activity
2K followers
-
Beau Cameron shared thisThrilled to be a part of the Infodash team. I continue to be impressed by the people, the product, and the passion behind it all. Being part of such a fast-growing company makes the experience that much more rewarding. It is a truly welcoming environment, surrounded by talented individuals who are dedicated to delivering a powerful intranet and extranet solution on Microsoft 365 and delivering real value for our clients.Beau Cameron shared thisThis is what growth looks like at Infodash so far in 2026! We’re continuing to invest in our team, bringing in talented individuals across the business so we can better support our clients, strengthen our platform, and scale alongside the firms we serve. Each new hire represents our commitment to delivering exceptional experiences and driving innovation in the legal industry. Welcome to the team, everyone. We’re excited to have you on this journey with us.
-
Beau Cameron shared thisThat’s a wrap for today! Fantastic session today, and it was great connecting with everyone at our SharePoint Framework workshop. Thanks to everyone who attended! Next up: Wednesday’s session on Getting Started with PnPjs with Julie Turner. If you're a dev at the conference, we'd love to see you there! David Warner II Hugo Bernier Chris Kent
-
Beau Cameron shared thisToday’s the day! David Warner II , Hugo Bernier, Chris Kent and I are kicking off the The Microsoft 365 Community Conference with a full-day, hands-on SharePoint Framework (SPFx) workshop. This year is especially exciting. We’ve been working on an SPFx Local Workbench (beta), delivered as a Visual Studio Code extension, to make development and workshops like this faster and more effective. https://lnkd.in/g2dYjGnc Here’s a quick look at what it brings: Local Workbench • Run and test Web Parts and Application Customizers locally • Simulated SPFx runtime with property pane and multi Web Part support • Themes and live reload Application Customizers • Mocked top and bottom placeholders • Simple add/remove experience • Editable properties with reactive props Storybook Integration • Auto-generated component stories • Supports locales, configurations, and themes • Visual testing with full SPFx context API Proxy & Mocking • Drop-in HTTP client replacements • Configurable mock rules with hot reload • Optional real API calls when needed Honored to continue delivering these workshops and kicking off the conference with the community.
-
Beau Cameron shared thisWhen you adopt an open-source library, you’re not just taking on that code. You’re also inheriting its entire dependency chain. That brings real implications: maintenance overhead, security exposure, and potential performance trade-offs. It’s on all of us as consumers to understand not just what we’re using, but what that code depends on. On the PnPjs team, we take this seriously. Every dependency is a trade-off. It can reduce control and introduce risk. That’s why we: • Minimize dependencies wherever possible • Keep them up to date with every PnPjs release • Re-evaluate their necessity during major versions It’s a win for maintainability, a win for simplicity, and ultimately a win for everyone building with #PnPjs. #Microsoft #Microsoft365 #Development #API #SDK #OSS #OpenSource Patrick Rodgers Julie Turner Microsoft 365 & Power Platform CommunityBeau Cameron shared thisEpisode 029 Inside PnPjs: Open Source at Enterprise Scale with the Library Maintainers Watch/listen to the full episode, links in the first comment 👇 In this episode, Andrew Connell and Julie Turner sit down with Beau Cameron and Patrick Rodgers, who along with Julie are the other core maintainers of PnPjs, for the podcast's first guest interview. PnPjs is a client-side TypeScript library that wraps both the SharePoint REST and Microsoft Graph APIs into a fluent, developer-friendly interface. With 38,000 tenants relying on the library and handling roughly 38 billion requests per month, PnPjs has become one of the most mission-critical open-source projects in the Microsoft 365 ecosystem. The conversation digs into the real challenges of maintaining a library at that scale, including architectural decisions like the elegant Timeline design, controversial API choices around URI escaping and the Pages API, and what it means to be responsible stewards of an open-source project by reconsidering the support for unsupported or reverse-engineered endpoints. You'll also get a peek at what's coming in v5, which Beau and Patrick describe as a maintenance-focused release aimed at improving code coverage, test execution, and expanding Microsoft Graph API coverage. The hardest part of maintaining PnPjs isn't the code itself, it's maintaining trust. Beau, Patrick, and Julie explore the tough decisions they've had to make as maintainers, from dropping support for legacy v2.1 endpoints to pushing back against shipping features that don't quite work right. Whether it's understanding the design tradeoffs baked into the Timeline architecture, wrestling with the extensibility of behaviors and virtual events, or grappling with the consequences of being used at such massive scale, this episode offers genuine insight into what it takes to steward a library that countless developers depend on every single day. #podcast #podcastclips #pnpjs #restapi #news #microsoft365 #microsoft365dev
-
Beau Cameron reposted thisBeau Cameron reposted thisI’m excited to share that Gowling WLG and Infodash have been named finalists for the International Legal Technology Association (ILTA)’s 2026 Distinguished Peer Awards in the Trailblazer category. This recognition reflects a joint effort to rethink how litigation knowledge is accessed and applied in practice. At Gowling WLG, we’ve built a deeply curated and continuously evolving litigation dataset. Partnering with Infodash, we’ve been able to unlock that foundation using #Ai to enable true question-based research across hundreds of thousands of data points—delivering contextual answers, traceable references, and cross-matter insights. The result is a modern litigation intelligence platform that enhances research precision, supports more predictive insight, and ultimately improves outcomes for our clients. A big thank you to the Infodash team for being a strong partner in bringing this vision to life. This is exactly the kind of collaboration that moves the industry forward. Looking forward to what’s next! 🚀🚀🚀 #legaltech #legalai
-
Beau Cameron shared thisJoin us on Wednesday at the The Microsoft 365 Community Conference! Julie Turner and I will give you the low down on #PnPjs, how to get started and what's coming next! #PnPjs Microsoft 365 & Power Platform CommunityBeau Cameron shared thisIf you're building solutions on Microsoft 365, PnPjs continues to be one of the most valuable tools for simplifying development across SharePoint and the broader M365 ecosystem. Looking forward to learning from Julie Turner and Beau Cameron in their session “Getting Started with PnPjs” at The Microsoft 365 Community Conference. PnPjs helps developers build cleaner, more maintainable solutions using modern patterns across SPFx and more. Sessions like this are always packed with practical guidance you can apply immediately. Definitely one to consider adding to your schedule: https://lnkd.in/gMBz33J8 #Microsoft365 #M365 #SharePoint #SPFx #PnPjs #M365Dev #M365Con
-
Beau Cameron reposted thisBeau Cameron reposted thisEpisode 029 Inside PnPjs: Open Source at Enterprise Scale with the Library Maintainers Watch/listen to the full episode, links in the first comment 👇 In this episode, Andrew Connell and Julie Turner sit down with Beau Cameron and Patrick Rodgers, who along with Julie are the other core maintainers of PnPjs, for the podcast's first guest interview. PnPjs is a client-side TypeScript library that wraps both the SharePoint REST and Microsoft Graph APIs into a fluent, developer-friendly interface. With 38,000 tenants relying on the library and handling roughly 38 billion requests per month, PnPjs has become one of the most mission-critical open-source projects in the Microsoft 365 ecosystem. The conversation digs into the real challenges of maintaining a library at that scale, including architectural decisions like the elegant Timeline design, controversial API choices around URI escaping and the Pages API, and what it means to be responsible stewards of an open-source project by reconsidering the support for unsupported or reverse-engineered endpoints. You'll also get a peek at what's coming in v5, which Beau and Patrick describe as a maintenance-focused release aimed at improving code coverage, test execution, and expanding Microsoft Graph API coverage. The hardest part of maintaining PnPjs isn't the code itself, it's maintaining trust. Beau, Patrick, and Julie explore the tough decisions they've had to make as maintainers, from dropping support for legacy v2.1 endpoints to pushing back against shipping features that don't quite work right. Whether it's understanding the design tradeoffs baked into the Timeline architecture, wrestling with the extensibility of behaviors and virtual events, or grappling with the consequences of being used at such massive scale, this episode offers genuine insight into what it takes to steward a library that countless developers depend on every single day. #podcast #podcastclips #pnpjs #restapi #news #microsoft365 #microsoft365dev
-
Beau Cameron reposted thisBeau Cameron reposted thisEpisode 029 Inside PnPjs: Open Source at Enterprise Scale with the Library Maintainers Watch/listen to the full episode, links in the first comment 👇 In this episode, Andrew Connell and Julie Turner sit down with Beau Cameron and Patrick Rodgers, who along with Julie are the other core maintainers of PnPjs, for the podcast's first guest interview. PnPjs is a client-side TypeScript library that wraps both the SharePoint REST and Microsoft Graph APIs into a fluent, developer-friendly interface. With 38,000 tenants relying on the library and handling roughly 38 billion requests per month, PnPjs has become one of the most mission-critical open-source projects in the Microsoft 365 ecosystem. The conversation digs into the real challenges of maintaining a library at that scale, including architectural decisions like the elegant Timeline design, controversial API choices around URI escaping and the Pages API, and what it means to be responsible stewards of an open-source project by reconsidering the support for unsupported or reverse-engineered endpoints. You'll also get a peek at what's coming in v5, which Beau and Patrick describe as a maintenance-focused release aimed at improving code coverage, test execution, and expanding Microsoft Graph API coverage. The hardest part of maintaining PnPjs isn't the code itself, it's maintaining trust. Beau, Patrick, and Julie explore the tough decisions they've had to make as maintainers, from dropping support for legacy v2.1 endpoints to pushing back against shipping features that don't quite work right. Whether it's understanding the design tradeoffs baked into the Timeline architecture, wrestling with the extensibility of behaviors and virtual events, or grappling with the consequences of being used at such massive scale, this episode offers genuine insight into what it takes to steward a library that countless developers depend on every single day. #podcast #podcastclips #pnpjs #restapi #news #microsoft365 #microsoft365dev
-
Beau Cameron shared thisTrust is the most important for me. Sure, semantic versioning helps, and you can always roll back if needed, but when you're supporting close to 40k tenants, stability and reliability isn't optional. Open-source should make things easier, not harder. If trust is lost, people won't want to use the library anymore. Check out the latest episode of the Code. Deploy. Go Live. podcast to hear more perspectives on maintaining #PnPjs from Patrick Rodgers, Julie Turner and myself.Beau Cameron shared thisEpisode 029 Inside PnPjs: Open Source at Enterprise Scale with the Library Maintainers Watch/listen to the full episode, links in the first comment 👇 In this episode, Andrew Connell and Julie Turner sit down with Beau Cameron and Patrick Rodgers, who along with Julie are the other core maintainers of PnPjs, for the podcast's first guest interview. PnPjs is a client-side TypeScript library that wraps both the SharePoint REST and Microsoft Graph APIs into a fluent, developer-friendly interface. With 38,000 tenants relying on the library and handling roughly 38 billion requests per month, PnPjs has become one of the most mission-critical open-source projects in the Microsoft 365 ecosystem. The conversation digs into the real challenges of maintaining a library at that scale, including architectural decisions like the elegant Timeline design, controversial API choices around URI escaping and the Pages API, and what it means to be responsible stewards of an open-source project by reconsidering the support for unsupported or reverse-engineered endpoints. You'll also get a peek at what's coming in v5, which Beau and Patrick describe as a maintenance-focused release aimed at improving code coverage, test execution, and expanding Microsoft Graph API coverage. The hardest part of maintaining PnPjs isn't the code itself, it's maintaining trust. Beau, Patrick, and Julie explore the tough decisions they've had to make as maintainers, from dropping support for legacy v2.1 endpoints to pushing back against shipping features that don't quite work right. Whether it's understanding the design tradeoffs baked into the Timeline architecture, wrestling with the extensibility of behaviors and virtual events, or grappling with the consequences of being used at such massive scale, this episode offers genuine insight into what it takes to steward a library that countless developers depend on every single day. #podcast #podcastclips #pnpjs #restapi #news #microsoft365 #microsoft365devMaintaining trust in large scale open source librariesMaintaining trust in large scale open source libraries
-
Beau Cameron reacted on thisBeau Cameron reacted on thisMany firsts at #M365Con26 ✨ ✈️ First time heading to Orlando 🎤 First time attending, speaking, and doing booth duty at M365 Community Conference 🧳 First time flying economy light with Norse, I booked the cheapest ticket and got my first real experience of strict bag size/weight rules… and still managed to bring most swag home 😄 💙 I met many #PnP core team folks for the first time , the heart of so many community initiatives that keep showing up: David Warner II, Hugo Bernier, Chris Kent, Beau Cameron 🎢 I also met amazing friends who became theme park buddies: Vesa Nopanen [MVP], Adam Deltinger, Angela 🌸 Jones and Lindsay Shelton. 🌍 Thanks to #M365Con26 and sponsor #ShareGate, I got to visit Epic Universe and Islands of Adventure, with the glee of a child going on rides and soaking in the immersive experiences. Truly beyond my imagination. 🤝 I was lucky to collaborate on booth duty with Vesa Juvonen. Our booth was quite hidden, but his impact and influence were undeniable. so many people found us by chance and thanked him for how he has helped shape their careers over the years. He is a superstar. 🌸 I also met Sravani Seethi, one of the founders of Women in Power (Platform), a community I’ve benefited from as both a mentor and mentee and where I’ve made amazing friends. 🎙️ Another important first: speaking solo for only the second time in one of the biggest room at the venue with capacity of probably 300- 500+. Most of my talks last year were with a co-speaker, and upcoming ones are too. My first solo session was at CollabDays Bletchley Park in a room capacity of 20 (smallest room at the venue) and one of it's organiser Brett Lonsdale was there representing #lightingtools and watched the movie premiere of #morethancode together with a red carpet experience. 🫂Met and made so many friends, you know who you are 🌸 🌸 Attended the women tech lunch hosted by Danielle Moon , Heather Cook and others sponsored by AvePoint 🧍Building mini MVP branded Legos, thanks to Bobby Chang for letting me have some extras 🧑✈️Booth duty with Phi-Lay NGUYEN answering questions on #CopilotStudio and #agents. Conferences are not just about technology as showcased in the movie premiere #morethancode. It will shared widely soon. They’re about people, connection, and inspiration for what to build next. 💫 #M365 #M365Con26 #Microsoft365 #PowerPlatform #Community #Speaking #WomenInTech #MVPBuzz
-
Beau Cameron reacted on thisBeau Cameron reacted on thisThis was the best way possible to end The Microsoft 365 Community Conference. My session was in the very last block of sessions to wrap up and intense week of learning and networking. And despite of it the best community in tech still showed up and filled the room. The session was about how you can make use of the latest non AI SharePoint features to create stunning SharePoint pages. And the number of attendees and the level of engagement proved to me that SharePoint is thriving even after 25 years. When you combine the brand center with flexible layouts and the new web parts added to gallery you have all the right engridients to make it your own and not just another corporate app. Thanks to everyone who made the time to attend and thanks for all the great questions and feedback. #SharePoint #M365con26
-
Beau Cameron reacted on thisBeau Cameron reacted on thisI’m looking forward to this conversation with Al Hounsell about being named finalists for ILTA’s Trailblazer Award, which recognizes the joint efforts of Gowling WLG and Infodash. We will walk through how Gowling WLG partnered with Infodash to elevate a deeply structured knowledge base into a client-facing AI platform using Microsoft 365 and Azure AI Search. This is a practical approach to delivering governed, citation-backed legal insight directly to the client extranet experience. We will cover what it takes to operationalize historical legal data at scale, from semantic search and natural language querying to security trimming and persistent AI interactions. If you are responsible for knowledge, innovation, or technology in a law firm, this session will show you how to unlock the value of your firm's institutional knowledge for clients. Join us live.
-
Beau Cameron reacted on thisBeau Cameron reacted on thisBest M365 Conference session yet! Makes it easy when when you have an engineering leader like Alexander Spitsyn ready to jump into demos and customer convos with you. We got to show off a new Workflows UX, our favorite features in quick steps, and make anyone a solution builder with Kristen Kamath. Great week connecting with customers, MVP’s, and the rest of our SharePoint AI crew.
-
Beau Cameron reacted on thisHappy to share that I'll be speaking at Inside an ILTA Finalist Project: Gowling WLG’s AI Platform! Make sure to attend it today.Beau Cameron reacted on thisI’m looking forward to this conversation with Al Hounsell about being named finalists for ILTA’s Trailblazer Award, which recognizes the joint efforts of Gowling WLG and Infodash. We will walk through how Gowling WLG partnered with Infodash to elevate a deeply structured knowledge base into a client-facing AI platform using Microsoft 365 and Azure AI Search. This is a practical approach to delivering governed, citation-backed legal insight directly to the client extranet experience. We will cover what it takes to operationalize historical legal data at scale, from semantic search and natural language querying to security trimming and persistent AI interactions. If you are responsible for knowledge, innovation, or technology in a law firm, this session will show you how to unlock the value of your firm's institutional knowledge for clients. Join us live.
-
Beau Cameron reacted on thisBeau Cameron reacted on thisAs I head home from The Microsoft 365 Community Conference, I’m reminded that even in the age of AI, it’s still people who make our community what it is. The hallway conversations. The shared coffee between sessions. The honest questions, thoughtful challenges, and quiet encouragement. Catching up with MVPs, meeting new faces, reconnecting with friends and colleagues - these moments matter just as much as the keynotes and demos 🧡 Technology continues to move fast. AI is changing how we build, work, and think. This week was a strong reminder that human connection remains the foundation: trust, curiosity, generosity, and learning together 🤩 Thank you to everyone who took the time to connect. Until next time. Safe travels everyone. 🙏 #M365Con26 #Microsoft365
-
Beau Cameron reacted on thisBeau Cameron reacted on thisDay 2 at #m365con26! Moved into the speaker hotel for the next couple of nights, grabbed a quick breakfast, and had some great hallway catch-ups with Julie Turner , Derek Cash-Peterson (He/Him) and Beau Cameron before the keynote on #governance and #security. Those in-between conversations are always where the real nuggets of wisdom surface. I’ll admit, I was a bit nervous about my session, so I stayed in the speaker room for a while before joining the #womeninpower lunch hosted by Heather Cook , Karuana Gatimu, and an incredible group of women. I left a little early to attend the session before mine by Ståle Hansen( with Nikki Chapple featured in some of the slides). That session gave me the boost I needed, so much so that I added my #ESPC #InspireAwards win into my intro for a confidence lift. Despite a few hiccups, my session went well, and I’m really glad I pushed through the nerves. Wrapped up the conference day with a great session from Vesa Juvonen and Paolo Pialorsi before heading out. Took some time to explore CityWalk (unsuccessfully hunting for a replacement toothbrush I’d left behind 😅). I did get one from the dispenser within the park, quite unusual place! The highlight of the evening? Bumping into Vesa Nopanen [MVP] and Adam Deltinger who became my theme park buddies at the island of adventures for the attendee party. Riding Harry Potter Hagrid’s motorbike adventure twice, exploring Skull Island, and just soaking in the atmosphere of the park lit up at night made for a perfect end to the day! #MVPBuzz
-
Beau Cameron reacted on thisBeau Cameron reacted on thisWhat a fantastic week in Orlando at #m365conf. lots of great conversations, packed rooms, and soul filling time with friends. Plus I got an awesome assist on my workshop from the CAT team... thanks so much Dewain Robinson Karima Kanji-Tajdin Bobby Chang Grant Geiszler and Drew Madelung
Experience & Education
-
Infodash
****** ******** *********
-
****** ****
****** ********* *********
-
***** *********** ***
********* *********
-
********** ** *******
******** ******* *** *********** ******* **** ******** ******* undefined
-
-
***** ********** ** *** **** ******* ** ***********
******** *******
-
View Beau’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Licenses & Certifications
Honors & Awards
-
Microsoft MVP
Microsoft
2 Category MVP.
Microsoft MVP for Office Apps and Services. Microsoft MVP for M365 Development -
HackVT 2015 First Place
-
This winning app allows the user to log onto their online profile and answer questions that will give them a better understanding of their daily carbon footprint. The web application also provides an educational component, notifying the user of the climate change impacts of their behavior and potential carbon savings.
-
Association of Computing Machinery Faculty Award
-
Recommendations received
9 people have recommended Beau
Join now to viewView Beau’s full profile
-
See who you know in common
-
Get introduced
-
Contact Beau directly
Explore more posts
-
James Carr
Zapier • 6K followers
Every team builds their own workflow engine. Most regret it. Time to see if the purpose-built solutions are actually better. As a follow up to my Enterprise Integration Patterns blog series, I'm diving into workflow orchestration systems. Throughout the posts so many folks opined "I feel like I build these all the time, but nothing solves it in a general way" and I'm interested in finding that general way. I'm planning to evaluate: - Temporal - Amazon Simple Workflow - Vercel Workflows But I know this space is vast. What workflow orchestration systems are you using in production? And more importantly: what questions would you want answered in an honest evaluation? Things like: developer experience, failure handling, observability, scaling characteristics, or something else entirely? Drop your suggestions in the comments. Your input will directly shape what I explore over the coming weeks!
5
4 Comments -
Matthew Harrington
iamproperty • 1K followers
🤔 I've been thinking a lot about technical debt lately...it's not boring I promise! More specifically, about how we all *deal* with technical debt. Over the years, I - like many others - have pretended it didn't exist, or focused only on the quick wins. What I hadn't really considered until recently, is that sometimes we take on technical debt consciously - and that's okay. Sometimes it's the right call. Sometimes it buys learning. Sometimes it buys time. The real problems don't usually come from the debt itself, but from the lack of visibility around it - when no one remembers why it was taken on, or when it should be addressed. Maybe it's time we stop avoiding technical debt and start talking about it openly - so it can be managed properly. How do you think about technical debt on your teams?
22
13 Comments -
Dipti Jaiswal
Microsoft • 7K followers
Power Pages quietly crossed an important line. With GA support for single-page applications, developers can now bring React, Angular, or Vue apps into the platform using the same tooling and workflows they already use. But this isn’t just “SPA support.” You can pair it with any AI tool of your choice to generate, refactor, and iterate on the front end — while Microsoft handles identity, data access, security, and hosting underneath. So instead of: • choosing between a platform or a framework • rebuilding auth and APIs for every app You get: • framework freedom • AI-accelerated development • enterprise guardrails by default And most importantly — choice. Prefer traditional Power Pages for fast, low-code delivery? Use that. Want full pro-code control with a modern SPA stack? Use that. Same platform. Same security. Multiple choices on how you build. This isn’t low-code becoming “more pro-code.” It’s adapting to how modern developers actually build. https://lnkd.in/gDXudMkY #PowerPages #BringYourOwnCode #CodeSites #PowerPlatform #BYOC
98
3 Comments -
Alexandre Lepage
Workleap • 950 followers
MERGE is GA in Fabric since January 2026? Stop the presses. The cynical voice in my head can’t help but note: ANSI SQL standard since 2003. SQL Server had it in 2008. But that’s not the interesting part. Is MERGE really that big of a deal? Yes being able to perform INSERT, UPDATE, and DELETE in a single atomic unit is useful. No debate there. But if your engine already supports proper transaction isolation, you were never exactly blocked. Let’s be honest: writing a MERGE statement is rarely anyone’s idea of fun. And no two platforms implement it quite the same way. Now here’s the more interesting angle. In cloud analytics platforms built on immutable storage, what does UPDATE or DELETE actually mean? Immutable storage + row-level mutation is a strange combination: - On Snowflake, merging VARIANT data with 90-day Time Travel enabled: have you looked at the size of Fail-safe lately? - On Databricks, when you run large merges, how much data does VACUUM actually reclaim? - On Fabric, does OneLake ever feel… fuller than expected? Or is storage simply abstracted away from the bill? These systems don’t really “update” rows. They rewrite files. Storage is cheaper than it used to be. It is not free. And keeping old data around has financial, operational, and sometimes regulatory consequences. Personally, I prefer CTAS-style patterns over MERGE, regardless of syntax. CTAS is simple. Explicit. Predictable. It aligns naturally with immutable storage instead of simulating mutation on top of it. It also gives you the flexibility to materialize as a table or a view at the eleventh hour. Is CTAS always the right answer? Of course not. Good engineering is not about absolutes. It’s about understanding trade-offs. So this isn’t about celebrating or mocking Fabric’s late arrival to the MERGE party. It’s about a more fundamental question: To merge or not to merge?
12
-
Shannon Eldridge-Kuehn
General Genomics Inc. • 15K followers
Azure discounts are one of those things that feel obvious until you actually look at a bill. After writing about Azure Savings Plans and why the savings don’t show up the way people expect, the next most common question is: “What happens when Reserved Instances are also in play?” This post tackles that exact moment of confusion. It walks through how Azure actually decides which discount applies, why discounts don’t stack, and why a bill can look messy even when everything is working exactly as designed. If you’ve ever looked at cost reports and thought “this should look different,” this might help reconnect the dots: https://lnkd.in/gxa7AnRm #Azure #CloudCosts #SavingsPlans #ReservedInstances #FinOps
14
1 Comment -
James Balamuta, Ph.D.
HJJB, LLC • 3K followers
Quick tip for anyone building custom Typst templates for use with Quarto: If special characters like $ are causing mysterious compilation errors that standard escaping won't fix, try hexadecimal escape sequences instead. For example: \u{24} for the dollar sign. Wrote up a quick note covering this technique, including how to use Typst's ASCII table tool to find hex codes for any character. Could save you some debugging headaches! https://lnkd.in/eE62SBGb #Typst #Quarto
39
-
Dona Sarkar
Microsoft • 54K followers
A thing I've been hollering about this year are the Design Guidelines everyone should think about when building AI Agents. If you are using M365 Agent Builder or Copilot Studio, these are already built-in guardrails (so they're a good place to "practice") before you go full-on Agent-A-Saurus-Rex 🦖 Below are a set of guidelines that we released in February that were centrally drafted by Office of the CTO (OCTO). If you look closely at these guidelines, you will notice that in general, these are just "good design" rather than getting overly creative with your bad self and inventing new things that confuse devs and scare away customers. Have a look and holler at me with questions! 👀Transparency •Let the user know this is an AI-enabled Agent (eg, this is an AI Agent, please validate responses, etc) •Provide basic instructions to get started (e.g. a “Hello” message, sample prompts) •Show history of prompts that the user asked in the past •Make it clear how to give feedback (e.g. thumbs up & down, "Send feedback" button, etc.) •Clearly articulate any usage or topic restrictions the agent has (eg, this agent only talks about travel, etc) 🚘Control •Describe how the dev or user can modify the Agent, after it’s been created, with things like the System Prompt •Enable the dev or user to choose the Agent's comms style: how verbose it is, desired formats, any caveats on what the Agent should not talk about. •Allow the dev or user to view and delete history: any associated files or data, prompts, and past conversations. 📎Consistency •Make sure icons are standard and recognizable (e.g. "Share Prompt," "Add a file or photo," "tag someone") •Use paperclip icon to indicate file upload/sharing with the Agent, and an image icon to indicate graphics upload.
115
11 Comments -
Roman Novikov
NDA • 1K followers
You can leave Percona, but you can't escape the Percona mindset. 😊 When I saw the news that Drupal is dropping MySQL (and Percona) as a recommended DB, I had to investigate. I traced the issue back to a bug regarding Percona XtraDB Cluster submitted almost six years ago. (https://lnkd.in/dwxfsHNN) What I found was frustrating. For six years, rather than submitting a bug report to Percona or asking for clarity, the maintainers kept patching the code based on assumptions - like the idea that AWS Aurora and XtraDB are functionally the same. This is a failure of collaboration. Open Source is not just about publishing code; it's about the ability to work together across organizational lines. - See a bug? Ask the maintainer. - Not an expert? Find one. - Patching the same issue for years? Get help. Let's get back to the core principles of our industry. Discuss your problems, even with people who work for your competitors. P.S. Help the community protect that ecosystem. Sign Vadim's Open Letter to Oracle here: https://lnkd.in/dx3geV6Z
6
-
Vedran B.
https://npgsqlrest.github.io/ • 19K followers
CRUD isn't enough. Agree, it usually isn't nearly enough for anything functional and usable. That's why almost all app generators that can build an entire app in a few clicks fail, and they fail miserably because they all generate code (endpoints, validation, even the UI) around CRUD operations. Real-world applications need more than one table; they need joins, transactions, and all that stuff.
34
12 Comments -
Arron M.
ZERO-1 LTD • 3K followers
Tech debt doesn’t show up on your P&L. But it does show up in delays, bugs, and mounting developer hours. If you're running a Adobe Commerce store, you've probably experienced it firsthand... - Custom features that break with upgrades - One-off code only one developer understands - Fixes that fix the fix from last quarter That’s tech debt. It builds up over time and quietly erodes your margins. After 15 years building on Magento, we’ve learned that the key to reducing tech debt isn’t just cleaner code. It’s a shift in mindset. At Zero-1 we’ve built a more scalable, multi-use approach to development. Think of it as a SaaS mentality...while still retaining complete control over your platform. In concrete terms, this means: - More reusable code - More standardized extensions - Less time reinventing the wheel The result is lower long-term costs and a store that’s easier to grow. If you're planning a new feature or re-platforming project and want to build with the future in mind, let's talk!
6
-
Oakley Hall
2K followers
Openclaw is great for tracking and scheduling home maintenance items. Take for example car maintenance: 1. Agent script runs and syncs mileage from Home Assistant 2. Calculates remaining miles for each scheduled maintenance item based on intervals stored in Sqllite DB 3. Checks for any Trello cards you moved to "🎉 Done" → marks maintenance complete at current mileage, calculates next due date 4. Creates new Trello cards in "To-Do" for any items that are due and don't already have an open card Workflow: 1. Get notified via Telegram when maintenance is due 2. Find the ticket in Trello "To-Do" list 3. Do the actual work (or schedule it) 4. Move the Trello card to "🎉 Done" when complete 5. Next day at 9am, script sees the completed card, records the mileage, and won't bug you again until the next interval Example: • Tire rotation ticket created (overdue at 32,230 mi) • You get it done, move card to Done • Next morning: script sees Done card, records "completed at 32,230 mi", next due at 47,230 mi • No new ticket until you hit ~47k miles Pretty cool, right?
6
-
Kennie Nybo Pontoppidan
Microsoft • 9K followers
We are soon shipping a lot of QoL improvements to the Business Central Word add-in for document reporting. All related to UX for the layout author. More updates are coming over the next weeks. You can try it today by installing the preview version. Note that Word does a lot of caching, so you might get an install error the first time you try to install the add-in. If so, remove any preview add-ins (for Business Central), wait a day or two, and then try again. #msdyn365bc #documentReporting #word
74
3 Comments -
Salvador Carranza
PossibLaw • 2K followers
Most vibe coders are optimizing the wrong layer. There’s a post going around showing how a “non-technical” prompt and a “senior engineer” prompt produce wildly different results for the same task. The takeaway people grabbed: write longer, more detailed prompts. That’s not the lesson. Here’s what usually happens. A deal team needs to review 6,000 documents in a virtual data room for a mid-market acquisition. Someone asks an AI to flag every contract with a change-of-control provision. They get a script that searches for the phrase, pulls matches, and dumps them into a spreadsheet. Half the results are boilerplate. Key risks in assignment clauses and consent requirements get missed entirely. Nobody knows what the AI skipped or why. An experienced builder doesn’t write a better search query. They ask different questions first. What document types are actually in this data room? Are we looking for explicit change-of-control language, or any provision that could block or complicate closing? Do amendments override the base agreement? Are side letters in the set? What’s the priority: speed to first-pass flags, or completeness for the disclosure schedule? What happens when a clause is ambiguous and needs deal-team judgment? That reframes the problem before a single line of code gets written. The gap between a weak AI output and strong output isn’t verbosity or technical vocabulary. It’s the quality of the constraints. Success criteria. Tradeoff decisions. Knowing what not to build. Vibe coding gets dramatically better when you stop describing the task and start defining the boundaries around it. I Try this: next time you prompt an AI to work through a diligence set, write three sentences before the request. What’s a real risk versus noise? What should get escalated instead of auto-flagged? What’s the consequence of a false negative? That alone will change the output more than any prompt template. Subscribe to PossibLaw. Substack. Podcast. Tools to become a builder. We run custom training for legal teams who are done watching from the sidelines. Let’s talk.
2
2 Comments -
Brian Sowards
Supersync.ai • 21K followers
If you feel left out of Claude Code cause you aren’t technical Download Claude Desktop It has Chat | Cowork | Code side-by-side Chat you already know how to do Cowork is a mini-OpenClaw without the hazards And Code is right there, ready to use. All you need to do is ask Chat how to get started with it! That’s how I went from being completely intimidated to running 6 code projects simultaneously in three weeks and looking like an 80s tv show hacker 🖥️
3
1 Comment -
Aimee Farabee
Empower Community Care • 1K followers
For any non-devs using Lovable, they just released one of the most helpful features I've seen... ability to mention code files in chat!! From their change log: https://lnkd.in/ekGjXfUi "Reference specific files directly in chat by typing @ or clicking the reference button in the code editor. This makes targeted edits and discussions about specific files faster and clearer." This has been a game-changer for me! Step 1: type @ Step 2: Lovable suggests files. Pick one or keep typing. Step 3: Select the file you wish to update Step 4: Code file updated 😄 Eazy breezy!
2
-
Dan R.
IDR Consultants LLC • 6K followers
The Bureau of Economic Analysis now has a custom connector. The BEA API doesn’t behave like most. You have to get a little weird with it. Read Interface, the latest edition of Developments, to learn how to bring in vital economic data via Power Platform. Article: https://lnkd.in/euKSGYM8 GitHub: https://lnkd.in/ed4VupNG
2
-
Kyle Sebestyen
Everon • 286 followers
Week 2 of Spring into AI challenged us to write an tool that AI can use. I decided to create a SQL Server DB Profiler skill that an agent can invoke. I wanted to move metrics closer, within my IDE. Usage: "DTUs comin in hot! Check last 3 hours. Show top 3 offenders." Output: A synopsis of top N offending queries over last N hours, invocation counts, cpu waits, and tuning recommendations. I chatted with GPT about what kind of metrics are possible to query SQL Server for. Then I asked it to produce a small suite of sql scripts and a powershell script to map input sentiment to input params in the sql scripts, and aggregate the output into a synopsis that relays the real current state of things, so I can quickly take action. Great for when those monitoring alarms go off.. I mean, of course, they never do, but just in case ;) src: https://lnkd.in/gnRDjsNd https://lnkd.in/gFPY2sAn
9
-
AKASH TUSHIR
CBRE • 971 followers
Four coding agents lined up for the Great Automation Grand Prix—winner gets unlimited server time and bragging rights. TurboBot yelled, “I’ll automate Jira updates!” and every software engineer in the office felt hope for the first time. ScriptNinja promised, “I’ll write unit tests, integration tests, and even explain why they failed.” BugBlaster tripped on a missing semicolon and accidentally fixed 47 production issues—pure luck, pure legend. Meanwhile, a tired software engineer watched from the sidelines, holding cold coffee and 23 unread Slack messages. As the agents raced ahead, they started automating builds, deployments, logs, alerts, documentation, and even those painful status updates that nobody reads. By sunset, the engineer finally closed their laptop on time. The agents didn’t replace the human—they removed the chaos around the human. For the first time in years, “work-life balance” wasn’t just a sprint goal… it was actually delivered. Moral of the story is : The Agentic world isn’t about automating humans. It’s about freeing humans to think, create, and live better lives. #AgenticAI #DeveloperLife #FutureOfWork #AutomationWithHeart #CodingHumor #AIForDevelopers #SoftwareEngineering #TechEvolution
9
1 Comment
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content