I recently found the correct word for something that has for years been an obvious tool for me: a code comprehension tool. A code comprehension tool, as you might guess helps you comprehend your code. All the smart work is still up to you, but your tool offers an overlay of extra information, much like the iPhone’s augmented reality or a cockpit’s head-up display (Why hardware designers should switch to Eclipse). Additionally, you get super navigation powers like Jumpers.
A recent article about Tool Mavens vs Language Mavens made me realize that the term code comprehension tool is a good description for a part of what Sigasi offers to VHDL designers.
So, every engineer should ask himself: am I still working through this code like a caveman? Or am I going to use the right tools for the job? (Screencast VHDL Code Comprehension)
comments powered by Disqus