Crank it up on the emulator, and it looks astounding at hi res. Just like Quake II or any other 3D game. It's all in the video card. Much better than TV.
I haven't been there, but my wife is from there, and I've read up on the nation.
The people are conservative. They dress well, follow politics, and read a lot. And I'm talking before TV, so don't think of that excuse. They have a much higher literacy rate than other nations such as, oh, the U.S.
Maybe it's due to the general European cultured influence of France, who had colonized them. Or maybe it's the Asian mindset.
So now Vietnam follows the path of many other nations: independent nation, to European colony, to communist revolution, to market economy.
It's not there yet.
The government does watch its people. It's a communist state, like you probably imagine Russia was decades ago.
Probably they'll go through lots of corruption and mob-type stuff even after becoming more capitalist. Just like Russia is becoming, and the U.S. is now.
But don't think the people are stupid, or aren't aware of this. These things take time to change and don't happen overnight. But they will.
Check IMDB further, and you'll find that Steven Soderbergh also did a movie called Kafka. And, one of his early shorter films was apparently a rather disturbing Kafkaesque film (I haven't seen it).
First, let's discuss some principles behind commenting (or just documenting) code.
Is code well commented? Well, think of how long it takes to understand the code. Then, once you've understood the code, think of how long it should have taken you to understand the code, knowing what you now know. Why the discrepancy? Could it be addressed by better documentation? Probably.
So now you've identified poorly commented code. How can you comment code properly?
Let's assume you are coding with intent, and not by coincidence. You should have a plan, and know what you are doing, and not just be making it up as you go along. Think of it as shooting a movie with a script, and not improvising every scene. Well, the comments are your script. You should already have the (meaningful) comments before you begin. Write them first. If you don't have them, why? Are you sure you aren't just improvising?
Another principle is not repeating yourself. Say things once, and only once. Information should be in one place. So, if the comments repeat the code, that's a violation. Remove one: the comment, not the code. It's better to put the information in the code, and not in the comments. Save the comments for things that aren't as easily said in the code. That's why some movie scripts describe backstory and themes and influences that aren't explicit in the frames of the film.
Finally, why isn't this done? We all know we should comment our code for the next person, and when we are the next person, we curse our predecessor who didn't take the time to properly comment the code.
Why didn't he take the time? Better yet, why didn't his management force him to take the time? Let's face it, the reward structure is not set up for fostering well commented code. Management wants code that runs now, and doesn't care if some intern complains about lack of comments while maintaining it some months later.
So why should you comment well, even if management doesn't care? Think of it as a stamp of professionalism. You take pride in your work, so you go above and beyond what J Random Hacker would produce, because you know it's right. The code isn't done until it is commented and tested.
Anyways I just finished reading the book The Pragmatic Programmer and it has lots of practical advice. I've been coding professionally for six years and it still makes me want to reevaluate my work and see where I can improve it.
Maybe writing computer programs in C and compiling them on a computer is illegal. It allows you to circumvent those bits which control copy protection! Pesky programmers...
I just bought a GBA for my wife last week, and then one for myself a few days ago.
I'm a professional software developer, so of course I looked up development tools for the little beast. I found the GNU tools, and info that I'd need such a flash device to actually make a cartridge. And also info on how they are hard-ish to get because of the crackdown.
I'd consider making my own Tetris game if only to avoid paying $60cdn for shitty Tetris Worlds.
But no... this tool can be used to copy games, so I can't write my own.
I got a BComH (commerce, that is business, degree) which featured MIS courses such as systems analysis. This includes marketing, finance, accounting, economics, organizational behaviour, operations management, human resources, all those things.
I got a BScH in computing and information science. This includes programming, but it's more than that. Algorithms, data structures, computational complexity, formal languages, formal logic, graphics, numerics, compilers, operating systems, parallel computing, databases, all those things.
There are also software engineering degrees. They should cover more applied things like project planning, testing, estimating, requirements, etc. Just do a keyword search for "SWEBOK" to see what (should) constitute software engineering.
Of course, there are no "real" definitions. It depends on what the institution's program is like.
Personally, I think a dedicated student can really appreciate the CS degree, and fill out the rest of SE through a dedicated post-degree self-study program. There are enough good books out there (e.g. Rapid Development, Managing the Requirements Process, Software Project Management) that this is possible.
I've heard it said that CS grads don't appreciate the final details of real applied software engineering, and aren't taught it. But really, even though it isn't the focus of their education, the good ones pick it up. My experience working with CS and engineering-with-computing-option engineers (some designated) is that it is usually the latter (not the former) who are more hack and slash coders. They often didn't seem to appreciate the complexity of what they were building, maybe because it wasn't wood or steel. I hear that engineers are more responsible with their programs and all that, but really I don't see it.
I'm putting conduit in my house this weekend while the drywall is removed.
I'll be pulling wires by Christmas.
Definitely the way to go.
What's So Funny? I'm Doing This
on
Wiring A New House?
·
· Score: 2, Informative
I'm literally putting the conduit in this weekend. In the future, I can pull whatever cables I want.
In my living/dining room, which I'm currently rennovating, I'm adding four outlets with conduit to the basement. Each outlet has space for six connectors. Leviton plug-in style. I can run voice, ethernet, cable, speaker, etc.
I'm just putting a box plate onto the stud and drywall, no actual device box. The wall plate goes on the finished side. Behide is a vapour barrier box, with 1" conduit going out the bottom through the floor.
Slashdot Mirror
You should check it out.
Crank it up on the emulator, and it looks astounding at hi res. Just like Quake II or any other 3D game. It's all in the video card. Much better than TV.
Yes that was the best.
Didn't it have Destruction in the title though?
I haven't been there, but my wife is from there, and I've read up on the nation.
The people are conservative. They dress well, follow politics, and read a lot. And I'm talking before TV, so don't think of that excuse. They have a much higher literacy rate than other nations such as, oh, the U.S.
Maybe it's due to the general European cultured influence of France, who had colonized them. Or maybe it's the Asian mindset.
So now Vietnam follows the path of many other nations: independent nation, to European colony, to communist revolution, to market economy.
It's not there yet.
The government does watch its people. It's a communist state, like you probably imagine Russia was decades ago.
Probably they'll go through lots of corruption and mob-type stuff even after becoming more capitalist. Just like Russia is becoming, and the U.S. is now.
But don't think the people are stupid, or aren't aware of this. These things take time to change and don't happen overnight. But they will.
You can theorize about how tech-savvy helps his sales, but the reality is that his sales are lower.
Check out his movie Kafka.
Check IMDB further, and you'll find that Steven Soderbergh also did a movie called Kafka. And, one of his early shorter films was apparently a rather disturbing Kafkaesque film (I haven't seen it).
I live in Kingston. I'm here now.
I wonder if I met this guy, I've been to some blind functions (had a blind girlfriend some years ago).
With Cogeco in Ontario.
I got a cable modem, no cable. Then I split the cable into my television.
I really don't watch TV, though, and hardly watched it at all.
When I moved from my apartment to a house, I changed from cable model to ADSL. I didn't get cable, or anything.
I don't watch TV. It's a waste of time, and the sparse TV content that is good isn't worth the cost.
When I got ADSL, I tried to get it without a phone, since I have a cell phone, but they wouldn't let me.
First, let's discuss some principles behind commenting (or just documenting) code.
Is code well commented? Well, think of how long it takes to understand the code. Then, once you've understood the code, think of how long it should have taken you to understand the code, knowing what you now know. Why the discrepancy? Could it be addressed by better documentation? Probably.
So now you've identified poorly commented code. How can you comment code properly?
Let's assume you are coding with intent, and not by coincidence. You should have a plan, and know what you are doing, and not just be making it up as you go along. Think of it as shooting a movie with a script, and not improvising every scene. Well, the comments are your script. You should already have the (meaningful) comments before you begin. Write them first. If you don't have them, why? Are you sure you aren't just improvising?
Another principle is not repeating yourself. Say things once, and only once. Information should be in one place. So, if the comments repeat the code, that's a violation. Remove one: the comment, not the code. It's better to put the information in the code, and not in the comments. Save the comments for things that aren't as easily said in the code. That's why some movie scripts describe backstory and themes and influences that aren't explicit in the frames of the film.
Finally, why isn't this done? We all know we should comment our code for the next person, and when we are the next person, we curse our predecessor who didn't take the time to properly comment the code.
Why didn't he take the time? Better yet, why didn't his management force him to take the time? Let's face it, the reward structure is not set up for fostering well commented code. Management wants code that runs now, and doesn't care if some intern complains about lack of comments while maintaining it some months later.
So why should you comment well, even if management doesn't care? Think of it as a stamp of professionalism. You take pride in your work, so you go above and beyond what J Random Hacker would produce, because you know it's right. The code isn't done until it is commented and tested.
Anyways I just finished reading the book The Pragmatic Programmer and it has lots of practical advice. I've been coding professionally for six years and it still makes me want to reevaluate my work and see where I can improve it.
We have flex hours.
So we went to see the late matinee, then came back for a few hours of work.
The matinee is less packed and cheaper, and the office is quieter in the evening, so everybody wins.
Except that the reviewer (the person writing the review) doesn't get that payment. Reviews are voluntary. Write one yourself.
Maybe writing computer programs in C and compiling them on a computer is illegal. It allows you to circumvent those bits which control copy protection! Pesky programmers...
What makes code quality any higher with interpreted languages? I usually find the opposite, if anything.
I just bought a GBA for my wife last week, and then one for myself a few days ago.
I'm a professional software developer, so of course I looked up development tools for the little beast. I found the GNU tools, and info that I'd need such a flash device to actually make a cartridge. And also info on how they are hard-ish to get because of the crackdown.
I'd consider making my own Tetris game if only to avoid paying $60cdn for shitty Tetris Worlds.
But no... this tool can be used to copy games, so I can't write my own.
I would like to study the code for a real RTS like StarCraft or TA.
I got a BComH (commerce, that is business, degree) which featured MIS courses such as systems analysis. This includes marketing, finance, accounting, economics, organizational behaviour, operations management, human resources, all those things.
I got a BScH in computing and information science. This includes programming, but it's more than that. Algorithms, data structures, computational complexity, formal languages, formal logic, graphics, numerics, compilers, operating systems, parallel computing, databases, all those things.
There are also software engineering degrees. They should cover more applied things like project planning, testing, estimating, requirements, etc. Just do a keyword search for "SWEBOK" to see what (should) constitute software engineering.
Of course, there are no "real" definitions. It depends on what the institution's program is like.
Personally, I think a dedicated student can really appreciate the CS degree, and fill out the rest of SE through a dedicated post-degree self-study program. There are enough good books out there (e.g. Rapid Development, Managing the Requirements Process, Software Project Management) that this is possible.
I've heard it said that CS grads don't appreciate the final details of real applied software engineering, and aren't taught it. But really, even though it isn't the focus of their education, the good ones pick it up. My experience working with CS and engineering-with-computing-option engineers (some designated) is that it is usually the latter (not the former) who are more hack and slash coders. They often didn't seem to appreciate the complexity of what they were building, maybe because it wasn't wood or steel. I hear that engineers are more responsible with their programs and all that, but really I don't see it.
Seriously, even one of my books on game design has a chapter on Roberta Williams. Go research and learn.
Any idea how much more cubicles cost than building simple small offices? Hint: wood and drywall is cheap.
Why they continue to buy cubicles, especially when productivity is lower in them, is beyond me.
I don't want Cat5e or anything else that will be outdated *eventually*...
I want conduit.
I've been running the stuff in my house as I remodel rooms. This way I can pull anything wire-like in the future whereever I want it.
Conduit.
You can just change MOUNT_DIR=.. (the parent directory).
Well I suppose the US robot arms are so much better.
Truly, the way the Canadarm crawls around the outside hull of the station is amazing.
I'm putting conduit in my house this weekend while the drywall is removed.
I'll be pulling wires by Christmas.
Definitely the way to go.
I'm literally putting the conduit in this weekend. In the future, I can pull whatever cables I want.
In my living/dining room, which I'm currently rennovating, I'm adding four outlets with conduit to the basement. Each outlet has space for six connectors. Leviton plug-in style. I can run voice, ethernet, cable, speaker, etc.
I'm just putting a box plate onto the stud and drywall, no actual device box. The wall plate goes on the finished side. Behide is a vapour barrier box, with 1" conduit going out the bottom through the floor.
Plan for change.
I more or less agree with the review, but I found an inordinate amount of typos, particularly in the XML examples (where it matters).
If I can spot them on a more-or-less casual read, how many more did I miss? What about the others who might not catch them?
O'Reilly needs to step up their technical reviewing, it's been lacking lately.