blog · engineering
Writing on Engineering.
Engineering practices we use to ship production-grade software for AEC. Notes on architecture, error handling, T-shaped teams, and small-team project management.
June 16, 2026
Scan it, own it: a free LiDAR scanner with no tiers
Capture a room with LiDAR and export DXF, USDZ, a quantities PDF, photos and notes. On-device, free, ad-free. No account, no paid tier.
3d · engineering · threejs
June 3, 2026
Get the most value of your tokens with nearshore software development using Claude
An agentic pipeline cut delivery from 41 days to 12. The 55 production issues automated checks missed are the part senior engineers still own.
strategy · engineering
November 26, 2024
Mastering error handling in AEC tech: strategies for crisis management
Proven strategies to handle errors in AEC technology with confidence: troubleshoot issues, minimize downtime, and ensure project success.
engineering
August 21, 2024
The elegance of minimalist project management
How small senior engineering teams ship AEC software faster than the 'big team' approach. Lagarsoft's structure, trade-offs, and operating model.
engineering
May 8, 2024
Exploring T-Shaped Knowledge and LLMs in Software Engineering
Why T-shaped engineers, paired with LLMs, deliver better outcomes on AEC software projects. Cross-functional depth, hiring, and team dynamics.
engineering
what you’ll find here
Topics we keep coming back to.
Architecture and source of truth
How we decide what the database knows, what the application knows, and how those two stay in sync when the domain is real-estate operations, building information, or anything else where the cost of stale data is measured in hours of follow-up instead of milliseconds of latency.
Error handling at the application boundary
AEC software lives in a messy world: half-uploaded files, partial scans, third-party APIs that go quiet, browser environments running on tablets in the field. We write about the error-handling patterns that keep the application usable when the world is not cooperating, and that surface the right context to the engineer who has to fix what broke.
T-shaped teams and what LLMs change
A small senior team that goes deep on one stack and broad across the surrounding ones gets more done than a larger team of specialists, and the tradeoff has shifted further in that direction since LLMs joined the workflow. We write about how the team is shaped, how the work is allocated, and what we have learned about pairing engineers with AI tools.
Small-team project management
How a four-person engagement runs on a single source of truth and a planning cadence small enough that nobody has to read a status report to know where the project stands.