How will computer and computer programming be a good practice to learn? For example, you learn how the circuits work, then assembly language, and then high level languages?
I decided to do that when I was 15 years old, and kept it for the same - Well, forever.
The basic program on the book that came with my computer (The first TS-80 came with a great book targeted at the same age, it is not certain that I started a good start book. Since then) ..
Learned assembly and binary by hand coding to CPU instructions from a z-80 CPU databook. Apart from all the registers and how the CPU works out of it, apart from this, our DEC in the school PDP-11 has been messed up with the assembly (just love the fact that due to the difference in word-size due to the hex instead of the base 8 was used)
Knowing the assembly was very helpful with my first job. I did not know anything at the time, but while reaching the original variable from the assembly, the concept of pointers was raised, so there were not many surprises in fact. Use of syntax exceptions was only a difficult part (for example, it is different from some other thing, and I was very upset before)
Took some electronic classes and paid special attention to the gates and flip Still did not understand how to get a bunch of gates and flip-flops from the CPU, who started learning about the time.
Learn about time signals (an important part of bringing it together) Navy - One of their classrooms included troubleshooting of a box that was originally an explosion CPU. You can work on any transistor, and go all the way up to the CPU to plug in through the toggle switch and the CPU can perform them (100 bytes memory). They could break a transistor and you had to be able to find it. (Whenever you make some difficulties outside of training, you used to swap the card until it was done).
Edit: By the way, the best part of this class was about the size of a desk of 2/3 about Skimetics's 50-page book, which was portrayed by each single part of that thing. . Every inch was studied till I got the "Got" (from at least one logic level - forgetting the power supply material) ..
A job coding PC (Because till then I was not really comfortable sleeping ram, switching cards and hard drives, swapping power supplies, ...)
Financially, took jobs in the database and I could find someone Also about the area Whenever I took a job, then I had a big idea how much I would learn about it. Taking jobs trying to concentrate on learning business practices and tools, where I spent good time on customer sites
This was the first 15 years of my career, the last 10 has probably been more difficult to understand the design of a higher level (focusing on OOD), which refers to reading or using your code (Instead of just solving a problem with your code) and thinking about how to interact with others and make others more productive.
I think the big part was not afraid to jump yet. I never saw anything on the computer and said, "Boy, I can never do this". If anyone wants something, I have done the same.
To know about the history of how all these things have exploded (the school version and who invented it) is totally irrelevant to me. I raise bits and pieces here and there, but in most part I just keep this in mind how it works. I focus on design patterns and books that apply to my work, which I can not apply, I try to understand, so I know when I should apply, etc.
Hey, this sound is starting up, sorry like a lot of computer psycho resume.
Comments
Post a Comment