8/4/2023 0 Comments Java script crash courseIf they knew how to multiply they could calculate 12 × 150 in seconds. That's pretty slow! It's also error-prone, since a mistake in the 3rd minute will be hard to spot and hard to correct after the fact. If they were able to add numbers at a rate of 30 numbers per minute, together 30 numbers per minute, it'd take them about 5 minutes to figure out that 12 × 150 is 1,800. They could multiply 12 and 146 together by adding 12 together 146 times. Imagine a person who only knew how to add and count, but didn't know how to multiply. A task that might take 2 or 3 sentences to describe to another person might take 100s or 1000s of lines to express in terms a computer can use.Ĭomputers make up for it by being able to perform billions of operations per second. They are "dumb" in the sense that they can only perform a limited number of operations. Computers Are Fast But DumbĬomputers are dumb but fast. If you develop this habit, you'll be able to tackle unfamiliar problems quickly and without stress. What does it appear to do? How can I be sure? How does its behavior change when I modify different parts of it? Why would someone think to write this code in the first place? Did you read a piece of code that does something unfamiliar to you? Figure out how to isolate that piece of code and play freely with it. This is understandable since the syntax is the most foreign and visible part of learning to code.īut most early frustration comes from believing you have a clear picture of what you're trying to do when, in fact, you don't. Novices spend too much time focusing on the syntax and not enough time focusing on the picture in their head. Expressing the words helps you understand the idea better. In other words, being a software engineer isn't about writing code any more than being a writer is about putting words on a page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |