“Changer son fusil d’épaule”

Sometimes, when all else fails, you have to change your tack.

The Perl programming language is largely based on the idea that “there’s more than one way to do it”. This same idea can be applied to real-time embedded programming — especially when the method of choice just doesn’t seem to want to work. Coming to that conclusion sometimes takes a bit of time — especially when you’ve been focusing on getting your first approach to work — and may require input from a colleague. That can actually work even if the colleague in question doesn’t know what you’re talking about.

This morning, I had an idea for a problem I’ve been working to resolve. I wouldn’t exactly call it an epiphany but it seemed to be the only solution still available — namely to break the rules and try something that should fail, but might actually work. When explaining the idea during a progress report, a completely different approach appeared on the whiteboard, in the drawing I was making.

That new approach, which took about an hour to implement, including the time to recompile CE, proved to be a very fruitful idea: it allowed me to answer the question I was trying to answer all along, and had a much lower chance at failing.

Once again hindsight is 20/20, but it sure would’ve been nice to think of this before…

About rlc

Software Analyst in embedded systems and C++, C and VHDL developer, I specialize in security, communications protocols and time synchronization, and am interested in concurrency, generic meta-programming and functional programming and their practical applications. I take a pragmatic approach to project management, focusing on the management of risk and scope. I have over two decades of experience as a software professional and a background in science.
This entry was posted in Software Development, Software Engineering and tagged . Bookmark the permalink.

One Response to “Changer son fusil d’épaule”

  1. And sometimes you should just take a cup of coffee in the morning 🙂

Comments are closed.