In our latest blog post, we cover some introductory details on how to write code that uses CodaEA to close the loop that Software Engineering has long ignored.
It is absolutely crucial to provide a mechanism to allow your software community (users, operators, support staff, and developers) to understand the errors your software emits, easily obtain solutions, and easily research those errors. We predict that if you don't do it, you will be outpaced by your competitors who do - and within the next few years.
Remember the big disruptions - Apple disrupting the music industry, the cell phone industry, the mobile device industry? Remember the automotive paid features that were introduced, but became standard and nobody would buy a vehicle without them (power locks, power windows, antilock brakes, cruise control, and so on)? ICEM is one of those disruptions - software will soon have to have it, or it will not be able to compete.
Who wants to use software A if software B does the same thing, and provides help fixing its problems?
Top comments (0)