3 ms·
It's good to eventually have a comprehensive plan, but the other part which is especially important to be able to motivate your learning is to have fun. The tr
by ilaksh 9y ago
It's good to eventually have a comprehensive plan, but the other part which is especially important to be able to motivate your learning is to have fun. The trick to that is to make things easy but not too easy as to be uninteresting.
When you are just beginning to learn programming, really simple tutorials are going to be hard enough. When I was like 8 we had a Tandy Color Computer 2 that came with an amazing friendly manual explaining in detail each key to press and walking you through entering simple BASIC programs. Then it suggested making little tweaks here and there to change the way it worked.
If you wanted, you could actually download the Getting Started With Extended Color BASIC book from Internet Archive and actually follow it by emulating a coco2 on MAME. https://www.google.com/url?sa=t&source=web&rct=j&url=http://www.colorcomputerarchive.com/coco/Documents/Manuals/Hardware/Getting%2520Started%2520With%2520Extended%2520Color%2520Basic%2520(Tandy).pdf&ved=2ahUKEwi3_7n59pHYAhUY9WMKHUgeAvMQFjAAegQIBxAB&usg=AOvVaw1eeoIcqr-UD4HUMfGUwKSw https://www.google.com/url?sa=t&source=web&rct=j&url=http://... It really is a great book.
Anything easy like that I think is a good choice to start. There are plenty of more modern alternatives. The point is though that you have to walk before you can run and you will need to build your skills up over a number of years.
Definitely a good idea to down the line refer to actual CS and software engineering curriculum and study books. But you really don't want to rely on individual prescriptions of what to learn or content sources. You need to learn actively in a self directed way. So google is an amazing resource.
But I would say 3-8 years, depending on what your standard is and the particular person, for normal non geniuses to have a solid set of knowledge and skills for software engineering if they work on it continuously. Which is not to say you couldn't be useful in a job before then though necessarily.
The most important skills may come through practice and learning the hard way though. For example developing actual important requirements that make business sense and are feasible and selling them to the clients is critical and really tricky.
To me most software engineering falls into two broad categories: design and feedback loops. By feedback loop I mean a continuous process where there is an input and output mediated by some error detection and error correction. Feedback loops in SE have multiple layers and types. It starts with the loop between yourself and the stakeholders in the process of analyzing and negotiating the requirements. This process continues through the initial development and maintenance of the software.
Other examples of feedback loops: between you and the compiler doing static checking of your programs syntax, unit testing, integration testing, etc. Another one: improving your object-oriented/functional/reactive/modular/whatever design as it evolves through new features and testing etc. That is the design process itself is a feedback loop where you come up with an idea for a design, try it out, see where it went wrong or could be improved, and adjust it.
Feedback loops and design overlap and interact of course. You want your design to facilitate the smooth operation of your loops. For example, if you need certain types of unit or integration tests, you will need to organize your code with that in mind to some degree.