BEC Systems  ยท  Cliff Brake

I help small teams build connected products

Hi, I'm Cliff Brake. I help ambitious small teams build smart/connected/edge products. Product development is changing. Shipping on time is a challenge. We borrow more and build less. Each is important, but the borrowing part can create unexpected challenges if not managed correctly. I offer practical ways to improve how you build and borrow technology, so development goes faster and faster instead of bogging down in technical debt.

A connected product spanning three tiers: Zephyr firmware that senses and controls, an embedded Linux edge gateway running Edge AI, and AI-enabled cloud distributed systems, with data flowing in both directions between every tier. A brace spans all three tiers under the question: how to build and maintain all this?
What you're aiming for

The goals every product team shares

Simple ingredients for a successful product.

  • Ship on time
  • Efficient reuse of technology
  • Quality
  • Control
  • Leverage AI
  • Security
  • Adapt to changing needs
  • Scale the team and product
Where it bogs down

Why doesn't it always come together?

Teams have talented people and good technology, yet still struggle to ship on time and meet the goals above. Here are a few patterns I keep seeing on teams that feel stuck.

Wrong technology

Using the wrong technology

Small teams have different problems than large teams. Just because Google uses it does not mean it is right for you.

No process

Neglecting the process

Building and maintaining complex systems requires process. The good news is it does not need to be hard or time-consuming. A little goes a long way.

Reinventing

Redoing work others have done

To be efficient, we have to leverage the work others have done, not only the technology but the process behind it.

Slow cycles

Slow development cycles

Innovation requires fast iterations, which means shrinking the time between having an idea and putting it in front of real users.

AI without structure

Letting AI outrun your process

AI amplifies whatever system it is dropped into. With clear structure it multiplies a small team. Without one, it produces code faster than anyone can review, understand, or maintain.

No tracking

Inability to track things

To move fast, we have to efficiently track and identify versions, parts, units, and locations across the whole product.

The development framework

Three principles that produce speed, agility, and quality

Platform thinking decides what you stand on. Release first keeps it moving. Developer experience sets how fast you can move within it. The technology changes. These principles don't, and everything I build reinforces them.

The development framework: platform thinking, release first, and developer experience at the three points of a triangle, producing speed, agility, and quality.
The technology framework

A platform assembled from open source and other technology

A connected product stands on a platform โ€” critical pieces, most of which we did not create but must assemble and use. Below is my own platform: the open-source pieces I build, the foundation they stand on, and the tools that tie it together. The specifics of your platform will differ. What matters is that you define it: what you are using, why you chose it, and how it all fits together.

The technology framework: a connected edge device and cloud sitting on a platform built from BEC open-source technology and an open-source foundation, with a rail of development tools alongside.

Free resources

The thinking, writing, discussions, and projects behind everything here.

Interested in shipping faster?

Whether it's a product you're trying to get out the door, a build that slows you down, or a foundation you want to get right from the start, there's a way in below. Start a conversation, or book a free 30-minute technology/workflow audit and I'll follow up with a written report.