Whether you’re beginning your career or looking to become more proficient in embedded software and systems, there are plenty of useful resources to help you. With over 25 years of embedded programming experience here at DISTek, I thought I'd take a few minutes and share some practical tips to enhance your skills.
It’s been a crazy couple of weeks around the office. We’re moving what feels like a thousand miles a minute as we put the final touches on our presentation for CONEXPO-CON/AGG 2017. Yes, you read that right, the DISTek crew is headed to Las Vegas next week for THE international construction industry show. This year’s show is running March 7 – 11 at the Las Vegas Convention Center.
I recently graduated from Iowa State University and began my career at DISTek, and during that time there is one thing that I notice engineers hate doing: documentation. Despite being loathed, it's widely believed documentation is one of the most important things in software development. I always strive to see that code my teams and I have worked on will be well documented in some form or another. I, especially, run into problems with code that is developed as a library (a set of functions and data structures).
“I enjoy doing code reviews!” said no embedded software development engineer, ever.
Nobody in their right mind takes pleasure in combing through hundreds of lines of Consolas 9.5 gibberish they didn’t even add, modify, or remove. There are no rewards. No incentives. Only an engineer at the other end of the diff-viewer who thinks you’re just trying to get under his skin, thinks you’re a know-it-all, or assumes your stylistic preferences are a personal criticism.
Okay, that may be a bit aggressive, but nonetheless, can be very true.