Uncoverlogicofapplication

The difference between engineering as art and engineering as science is that objectiveness of requirements/design specification, and logical flow of inference and deference.

As more people are born into our technology-centered world, coding, and use of technology will become a fundamental skill in much the same way the math works today. This is combined with the simplification of programming tools and proliferation of doing it yourself interfaces. 

The applications will become more user friendly, interrelated as we move to a world of systems-of-systems where constraints govern how and what we develop and people become the center of the business.

Illogic behind application programming is caused by ineffective management practices: It is a lack of structure, observation, and progress measurement that permits bad code to persist until ripping it out becomes nearly impossible. Some amount of bad code is inevitable, because programmers are human. Too often, organizations can't be bothered putting the effort into these details, and just want to race into execution. 

When the problem is a developer, the leadership/management has usually contributed to the problem. Symptoms are: lack of reliability leading people to withhold information and produce incredibly convoluted code that no-one enjoys. It’s important to educate engineers to think beyond coding, understand business context, the purpose of code, and customer satisfaction. etc.

Logic of applications is more interactive and customer-friendly: The platforms, tools, and environments that programmers use will become more powerful, easy-to-use and knowledge-base. Be more user-centric, the user will do the programming and the programmer will build the systems and infrastructure to enable this. 

To improve software management effectiveness, the involvement of software development teams is really important. IT-enabled business solutions meet the customers’ criteria and clarify their concerns such as, what the users need it to do, the way they want to do it quickly, and accurately enough. We will see the product owners become self-sufficient and able to execute their vision of the application nearly real time.

Logic of setting up software development principles/criteria is to improve software quality, reliability, reusability, customer-centricity, value/cost performance ratio, etc: Besides agile principles and philosophies, if there are good team principles and a focus on quality there should never be an issue stemming from the work of a developer or programmer. 

It’s important to set criteria for telling bad code from good, specification and test plans. You need to evaluate code in context as soon as possible; integrate early, on time, and use partial integration testing; check progress in small increments: use Earned Value Management or Cost Schedule Management. Set specification, vendor review, with the goal to improve application quality, reusability, and performance.

The difference between engineering as art and engineering as science is that objectiveness of requirements/design specification, and logical flow of inference and deference. Because the software has to be used in order to be valuable. Only customers can value the quality of the software. At the high maturity level, the scientific side of engineering is for automation, reliability, and continuity; to become more real time for problem-solving technically.

Posted in: Digital Agility,Project Management,Quality