Chris Dellinger

Great article from Anthropic last week on how they use Claude Code in-house: https://lnkd.in/gvYg-tMD. I think the key takeaway for me is that none of the highlighted use cases are software developers using it to build products. This is all about getting oriented with unfamiliar codebases, debugging, workflow and prototyping for non-developers etc. If you have not felt welcomed by the tool being called Claude "Code", might still be worth giving it a shot if you want a powerful LLM agent that can access your files, browse the web, and leverage tons of free public MCP integrations including things like Jira, Figma etc. Think of it less as a developer, and more as a generic local AI agent. Here's an example from when it helped me organize/rename some iCloud photos and give feedback on my interior design and some product suggestions. (It's definitely right more plants would be great, if only it could help me water them)

8

Big News! We’re thrilled to announce that INEMSOFT has won a major multi-year RFP to modernize airline dispatch operations for a leading North American carrier. Our flagship SEQUENCE® Console System and SEQUENCE® Workspace will transform the airline’s Operations Command Center into a next-generation hub for safety, efficiency, and collaboration. Key highlights: ✅ Unified radio, telephony, and conferencing built on SIP/WebRTC ✅ Advanced collaboration tools for faster decision-making This win underscores our commitment to innovation, reliability, and mission-critical communications. We’re excited to partner with our customer to elevate their operations to new heights! https://lnkd.in/et8Ewbpn

33

6 Comments

Maintaining software is like maintaining fences. The fence on the left is 10 years old, the fence on the right is less than one year. Both are made of cedar, but the one on the left is regularly power-washed and resealed every 9-15 months. Don't neglect your software maintenance. Although the debt may be hidden, it is nevertheless there, waiting to reveal itself at a most inopportune time. Fold maintenance into your sprints so it doesn't have to be a chore.

75

7 Comments

Operational efficiency isn’t just about cutting costs it’s about visibility and control. Today, Allbridge launches Skyway with Allbridge Intelligence, giving organizations a smarter way to manage operations, improve TCO, and unlock stronger ROI through a single, unified dashboard. Looking forward to seeing the impact this has across the industry.

18

1 Comment

Not necessarily a cyber role - but if Henry is handling it - I'd take a look. And it's Remote.

3

1 Comment

The best ops insight I’ve heard in a while came from a quick exchange: “It’s not any single step that’s the problem, it’s the gaps in between. Inputs exist, approvals happen, but context gets lost as work moves from team to team.” That’s the real bottleneck: CONTEXT DILUTION. When the “why” doesn’t travel, teams spend their week clarifying instead of executing. That’s when you get the symptoms everyone recognizes: - back-and-forth - stalled queues - “I thought you meant…” - and dashboards that look fine while the operation feels stuck. The fix usually isn’t heavier process. It’s a simple guidance layer: 🔻A lightweight handoff brief that moves with the work 🔻A small alignment ritual that keeps definitions from drifting Operational trust is what lets work stay coherent, even when you’re not there to explain it. Read more in the Qnectra Systems Brief - January edition https://lnkd.in/evxRkEA8

2

Over the last few months, I’ve been working with teams across Alaska Airlines to define what “enterprise-grade AI” really means in practice. Not just models and prototypes… there’s secure infrastructure, data access boundaries, governance, and a repeatable path from experimentation to production. We’re now putting that vision into practice by standing up structured AI workspaces that enable teams to experiment safely, move faster, and stay aligned with long-term compliance expectations. The goal is simple: unlock innovation without cutting corners on data protection, operational rigor, or stewardship. What’s been most energizing is seeing the internal momentum. Across disciplines, people are exploring use cases, from automation to decision intelligence to knowledge copilots, and doing it with a shared foundation that supports scale, trust, and responsible adoption. I’m grateful to be part of this work. When engineering culture embraces new technology thoughtfully, with curiosity and discipline, it creates room for bold ideas to become durable solutions. Onward.

13

There is a lingering bias in our industry that contractors are just passing through. That because they aren't on the permanent payroll, they don't care about the product, the team, or the mission. They are often labeled as mercenaries. I think this view completely misunderstands what drives a great engineer. If you look at the reality of how a contractor works, the dynamic is actually the opposite of indifference. A contractor doesn't have that safety net. Their "job security" is the quality of their code. Their "tenure" is entirely dependent on the value they delivered this week. That lack of a safety net doesn't create detachment. It creates intense focus. The contractors I know aren't checking out; they are dialled in. They know that their reputation is the only asset they own, so they protect it with high performance work. Perhaps we start judging candidates by the impact of their work.

8

1 Comment