IvoGeorgiev

40 - starting with a 4x4 grid, that makes 16+9+4+1 = 30, and adding 8+2 for the inner ones Can someone explain where is the 41th, if there is one?

I'm also 17, and I plan to focus on these things (not sorted by priority): * learning functional programming: starting out with haskell and scheme * learning to be a good salesman, to be able to sell my own skills to potential clients; you must be aware that you're 17. Some people would not take you seriously, some will be impressed by your age - anyhow, you must be aware that people's opinion will always be twisted by your age, either in a negative or positive direction. * maybe this depends on the way high school functions in your country, but in mine, most of my schoolmates cannot get good grades without studying/paying attention, but I can. So while I am at school, I have nothing to do, so I decided to read a lot of CS theory books. * creating social contacts - finding a lot of people, both like and unlike you, that you love spending time with; this is obviously important for your personal life, but can also one day be better for your professional life * try to learn graphic design - this is one of my personal goals - and I'm doing it because some programmers that I know believe that graphic design and programming are kind of mutually exclusive

And just to mention: NEVER create a website for your school :D

One year ago, I wrote an implementation of a concept I had. This implementation is a system daemon, which manages a lot of I/O work. The prototype was in bash, the actual system daemon was in C.

I am extremely proud of my recent decision to rewrite it in JavaScript and use Node.js. In the C implementation, I used standard FS functions (e.g. unlink, fwrite, fread) and of course, they are synchronous. In order to optimize the I/O, the entire daemon needed to be rewritten to use threads for the basic worker units, which were at least 5-6, each doing a very simple job. The alternative was to use async FS library in C, but I had to name every single callback.

So I scratched the C code and rewrote the daemon in Node.js. It is much faster because it manages to utilize the system resource much more efficiently, and the code is 3-4 times smaller.

The point is. If you have to do a lot of computation, DO NOT switch to Node or DO switch to Haskell. If you simply have to manage I/O operations, writing in Node might actually decrease complexity.

It's really simple, no long answer or discussion is required - think of what prevents you to excel at both. Nothing.

I cannot even believe that there are people who agree with this moron. First of all, he's chasing an ideal that's not even THAT valid: not all of the crappy-written software is knowledge, not all source code is worth reading. Plus, proprietary software improves industry. Industry feeds people.

Not to mention, in today's world, it is impossible to live without depending on corporations. The only way to live without someone knowing a lot about you is to live in a cave, miles away from civilization.

The way he is using computers: he is just putting restrictions on himself, thinking he actually removes them.

The only thing I agree with here is his opinion about Lisp.

Depends on the time of year. I seem to be more productive late at night (00:00 - 05:00) during summer and 22:00-02:00 during the winter.