About Bill

The obvious question is why should you listen to my advice since you don't know me? I started as a project engineer a year out of college for a smaller automation company in Dayton, Ohio. It was an awesome learning experience. I had several great engineering mentors that between them, looked at functionality, process, and cost and took the time to make sure I learned to look at small details and the big picture. Plus, the company had in-house mechanical and controls engineering, machining, welding, paint, panel build, and assembly, and I enjoyed being hands on, so I tried every step of the process along the way. Ok, I was an awful welder and I only ever painted a bike frame, but at least I gave it all a try. But on the engineering, machining, and assembly side, I immersed myself in learning from those I would consider to be experts in their fields. As I moved on to other positions and other companies, I tried to keep learning from everyone who was good at what they did and even accumulated "things not to do" from people that may not have been so good. I can't guarantee that everything I blog about will be the most perfect engineering solution, and maybe your company has different or better answers, but I won't put it on here unless I've either had direct success/failure with it or have witnessed success/failure from others firsthand. This is an experiential engineering type business. There are many things that  "everybody just knows," but you won't find them in any engineering book. My hope is that I can accelerate your exposure to these unwritten practices so that you are seen as valuable and skilled faster than if you have to find out on your own. Why? I guess it's because I'm an old guy now and it seems like the right thing to do. Enough about me.

See my LinkedIn profile for additional info.