The parallels between home remodeling and transaction-level modeling are scary.

Designing for a worst-case scenario may guarantee a device will work, but it’s also the least-efficient approach.

What’s obvious to some engineers is obviously wrong to others, and that’s a problem.

The goal is to understand tradeoffs with the least amount of time and effort, balancing function and performance.

Just because something’s been done a certain way in the past doesn’t mean it should continue.

Picking the right rental car depends on where you’re driving and what you need to stuff into the vehicle. It’s all about context.

Understanding the origin of re-used technology or software can save a lot of time and problems.

Now the real fun begins. It’s easier to get started, but it’s also harder to manage expectations.

Where the system-level approach is useful in programmable logic and where it doesn’t work.

For some people it’s an absurd amount to pay. For others, it’s just a great lunch.