We are now getting into the integration of software. So, software implementation is a discipline that ensures that the software system you’ll make integrates well into a complete system. So it’s to make sure you know how are you going to do your work, and finding out the best way to do it, and which tools you’ll need.
Programming methods are usually broken into two:
The structural in which you work with loops and other subroutines to make you code a little more legible.
The functional, which bases itself in mathematical functions.
So you can choose between those two in how you want to implement your system. Now, it’s also important to make sure that your code is somewhat easy to read, or that at least people can figure out easily what is going on in the code. This is why documentation is really important. There’s a few ways to make documentation, but the important thing is that you actually document your code. Designing a software is not a job of a single person, make sure that others understand what’s going on between the lines.
Now the tools:
- A text editor: You need a place to write your code. It can even be notepad if that’s you cup of tea, but you’ll need an editor.
- Compiler: Some languages only need an interpreter to run, but in some is necessary in order to translate the code into machine language or another lower level language.
- Debugger: You’ll need it for big piece of software. Using the good ol’ trusty print in console only works to a certain point. A debugger helps you find bugs and deal with them faster.
- A SCM tool is also really helpful when working with a group of .
- Testing tools: Test your software. It’s important. You don’t want a faulty software out there made by you.
- Documentation: Make sure that you know what’s going on. I remember that I once saw in StackOverflow a guy that said “When I started to write this code only god and I knew what was going on, now that I’ve finished it, only god knows.” I don’t think you want to be that guy, or I don’t know, don’t really know him.
