It’s about software engineering. why are we talking about drills? Hmmm. I mean. what information system users really need is that they don’t have to bother handling transactions manually. work efficiency. and are able to monitor the organization’s operations in an actual. sharp. and reliable way. a la Liputan 6.
Meanwhile people who are just learning to program
Still struggling with low-level things like. of course. coding . So. what phone number lead we often brag about is: “You have to use Java!”; “CakePHP is really cool…”. “Here. AJAX becomes simpler if you use Prototype”; “I have mastered Java. PHP. VB. C#. MySQL. Postgre. Cake. CodeIgnitter. etc… (really???)”; “Just use MySQL which is open source “;
But. for information system users. the reality often encountered in the field is: “I really think!” . They want a ready-made application that meets their needs. not a cool piece of program code. but does not form an application that can be used as a whole. They are too busy with their daily work. Of course. they do not understand the advantages of Java (for Java users. but not for Paul Graham ). do not care about the simplicity of AJAX with Prototype . and do not care whether we have mastered PHP . Java. CakePHP . MySQL . and so on. Moreover. most of them are just ordinary computer users. this means they can only use the computer applications they use every day .
Coding is Not the Same as Software Engineering
Coding is only one part of the overaware engineering process. Other parts include analysis. specification development. design. documentation. testing. training. data migration. installation. maintenance. and so on. The job isn’t done once the program is finished. In fact. providing software support and maintenance services can be a major source of income for software developers.
The Measure of Quality and “Eventfulness” of a Program is Its Suitability to User Needs What people really
Software is considered good and high-quality if it meets the needs of its users. not because it was created using a sophisticated programming language or library
. The size of a software’s “event” is also determined by the user. not by the programmer’s judgment . Therefore. specifications must be clear from the start. analysis must be thorough. listen to and prioritize user input. prioritize the testing phase because it takes the most time. and always involve the end – user .
Avoid Reinventing The Wheel. Use Existing Pieces Wherever Possible What people really
Don’t build everything from sc ame facilities are already available in affiliate disclosure for the my-data-team existing libraries . tools . frameworks . and other components. whether provided by default or made by third parties.
Besides speeding up the design and implementation process. existing components have also been extensively tested. thus minimizing bugs . This also allows end users to immediately try the software created.
Use existing components What people really
Use tools that make things easier. not those united states business directory that make things more difficult. There are many tools. both in number and type. The principle: know the purpose of the tools and use the tools that you really need.
This article is solely my opinion. based on my thoughts. knowledge. and experience. which are. of course. still very limited. Therefore. if readers have differing opinions and experiences. I would be happy to share them in the comments or by linking back to this article.