When I entered the realm of the Internet some time in the early 2000s, I had my idea for my username, Sazz. I really thought that it was original and that no one else had done it. Around a year ago I decided to go out and see if other people really had used that name, and I've found out that it may have been used since before I was born, by lots of people. I really thought I had had a new idea, too.
On another note, I just searched 'fmp tedzy the bear' again, and found that it has a result from me and a result from some other site that actually had some recognizable Starcraft wording in it. I clicked on the link and found out that my IP range is banned from the site. Even if it's just because I'm on Blogger my priority in the search was higher than yours, fools.
On what seems like the most important note, from the world of ScienceOnline '09, I'm submitting my interview response to Bora Zivcovic at A Blog Around the Clock either tomorrow or today. I can't say enough that I'm eager to go next year, there was a lot of interesting information and speculation to go around at the last conference and an atmosphere I appreciated (many of the people at this conference have said proudly that they don't want to 'grow up', at least in a more traditional sense of the word).
And finally, my family (which has extended to include me, too) will have highly limited access to the Internet over the following month. This means I won't be writing anything for that duration of time (as if I was a consistent and frequent poster anyway). To all my loyal and numerous fans, I'll return to tracking your epic turnouts at the end of summer!
Friday, July 24, 2009
Monday, July 13, 2009
PP: AItCSUP: Chapter 2
In the second chapter of the book, the Pythoning begins. The idea of the book is to give ongoing information about computer programming throughout, but the programming itself begins here.
The chapter started off by explaining, on a broad level, the macro of how a computer works: on the most basic level is the hardware, which materially the machine is. Next, the operating system is that which directly interacts with the hardware; all that is above the OS needs to go through it, or operate using it, to do anything with the hardware. The OS and the various other entities above it that do things are all programs, but the book outlined how the OS is the only one that calls the shots (has direct access to the hardware).
Next, the chapter went into some math. The math here wasn't extremely complicated (BEDMAS, modulo, rounding, integers and floating point numbers), but the information was more about how Python dealt with the numbers than how a person would, presented on a sheet. For instance, Python before 3.0 (apparently the later versions of 2 are still used more) will round down (take the floor value) of integer division. On the other hand, it will divide floating point values as closely as it can (it will also always convert integer values to floating point values when the two are in the same expression; I'm guessing that integer values are only used when it's strictly certain that the rest or the real numbers aren't needed). After that, it went into using variables on top of the math, and then how Python treats variables (again, not quite as one is supposed to use them generally). A short interlude with basic error messages came (there was one before too), and then the book got into functions.
I was pretty interested with this part. It took all of the previous math information, with variables, and then added defining and using functions to it. At this point, one might not right much of a program yet, but they (I) could make a list of variables and functions at this point; I was OK with not knowing how to right an even mildly sophisticated program after the first chapter, but I was glad the learning curve wasn't very wrathful (maybe I want a straightforward learning experience... sue me). The chapter finished with a few paragraphs on style (there are myriad forms, and the books advice was to use some kind of procedure with a few broad tips; however, if people argue that there is one style out there to rule them all, then hound them for actual proof). Finally, there was a summary of the chapter (which I didn't read before writing this-- honestly!), and a section with exercises. The chapter's title was 'Hello, Python!', and in the way of Python's own developers, they made sure to include well known lines from cultures of varying popularity almost wherever there was a code demo with words. More on the book later, which is hopefully sooner; I was supposed to update this daily, but I doubt that's a pattern I'll settle into (maybe my dad meant that I was supposed to at least add to a post daily, which sounds manageable).
The chapter started off by explaining, on a broad level, the macro of how a computer works: on the most basic level is the hardware, which materially the machine is. Next, the operating system is that which directly interacts with the hardware; all that is above the OS needs to go through it, or operate using it, to do anything with the hardware. The OS and the various other entities above it that do things are all programs, but the book outlined how the OS is the only one that calls the shots (has direct access to the hardware).
Next, the chapter went into some math. The math here wasn't extremely complicated (BEDMAS, modulo, rounding, integers and floating point numbers), but the information was more about how Python dealt with the numbers than how a person would, presented on a sheet. For instance, Python before 3.0 (apparently the later versions of 2 are still used more) will round down (take the floor value) of integer division. On the other hand, it will divide floating point values as closely as it can (it will also always convert integer values to floating point values when the two are in the same expression; I'm guessing that integer values are only used when it's strictly certain that the rest or the real numbers aren't needed). After that, it went into using variables on top of the math, and then how Python treats variables (again, not quite as one is supposed to use them generally). A short interlude with basic error messages came (there was one before too), and then the book got into functions.
I was pretty interested with this part. It took all of the previous math information, with variables, and then added defining and using functions to it. At this point, one might not right much of a program yet, but they (I) could make a list of variables and functions at this point; I was OK with not knowing how to right an even mildly sophisticated program after the first chapter, but I was glad the learning curve wasn't very wrathful (maybe I want a straightforward learning experience... sue me). The chapter finished with a few paragraphs on style (there are myriad forms, and the books advice was to use some kind of procedure with a few broad tips; however, if people argue that there is one style out there to rule them all, then hound them for actual proof). Finally, there was a summary of the chapter (which I didn't read before writing this-- honestly!), and a section with exercises. The chapter's title was 'Hello, Python!', and in the way of Python's own developers, they made sure to include well known lines from cultures of varying popularity almost wherever there was a code demo with words. More on the book later, which is hopefully sooner; I was supposed to update this daily, but I doubt that's a pattern I'll settle into (maybe my dad meant that I was supposed to at least add to a post daily, which sounds manageable).
Subscribe to:
Posts (Atom)
