DYNAMISConsulting & Controls, LLCA notebook by Paul Kruchko
Engineering, architecture, and the things worth arguing about.
Paul Kruchko
Controls & embedded software engineer
Principal & Owner, Dynamis
About this blog
A system may need to work long after its original components, tools, and engineering team have changed. I'm interested in the decisions that make that possible, and the shortcuts that make it painful.
This is a place to think out loud about hardware and software architecture, obsolescence, and open standards. Defense and automotive engineering provide plenty to talk about. So do the everyday choices behind software design and development.
Expect technical arguments, questions worth working through, and the occasional rant. The thread running through it all is how to build systems that people can understand, change, and keep working.
Paul's Thoughts ·
I want my business to make a profit. I want it to pay people well, buy good equipment, survive a difficult stretch, and have enough room to do work properly. There is no virtue in building a business that can remain solvent only b…
Read this essayPaul on Programming ·
A controller that compiles, runs, and passes its unit tests can still be the wrong controller. It can implement the wrong behavior beautifully. It can meet a requirement that was never valid. It can make a perfectly reasonable lo…
Read this essayPaul's Thoughts ·
The best time to discuss changing suppliers is while everyone still likes each other. At that point, the development team is available. The business relationship is healthy. People remember why the interfaces work the way they do…
Read this essayPaul's Thoughts ·
There is a peculiar kind of pride in an engineering organization that has built everything itself. Its own framework. Its own communications protocol. Its own development tools. Sometimes its own operating system. The implied argu…
Read this essay