ragatskynet

I wouldn't - the news of the Google Reader shutdown made great opportunity for many nice RSS/news readers to be born; so I would just switch, there are plenty of good alternatives now.

I actually use Feedly now - its perfect for me.

Not sure if that is what you are asking, but I am tracking my personal things in an Excel table - you can complicate things to the level you want.

I agree with you. I suggested these sites to a friend of mine and after then he really got into javascript and ruby. After learning the fundamentals, books are more understandable and more usable lets say.

Hahhha... some days ago I checked one of my old PHP codes (I was not aware it was written by me) - I was swearing much.. then I saw my name in a comment on the top and then.. I sweared more :-)

My style is transforming from year to year to a better one (I hope), so sometimes I cannot recognize my old ones.

I use feedly now too, I could set it up to look almost like reader did. I use it on my android phone as well.

I use a simple text document in my Google Drive, it is pretty plain - when I have a new idea I write it into the doc and at the same time I go through all of the others and see If I have more exact ideas related to them. Also I check back occasionally to see if I am still interested in all of them (let's call it refactoring,heh).

There are some which I share, some that I do not. :-)

Mostly repetitive 4/4 stuff like house or techno, sometimes downtempo/ambient/dubtechno (at night). Preferably without vocals; I am not a big fan of these types of genres (when I am not working I would never listen to these) but I found them very good for coding - they eliminate unwanted noises though they do not need your focus because of the repetitiveness.

I wanted to type this exactly.

"Scrum is not always Scrum." - Big point, haha - I see hundreds of people using "Scrum" and not Scrum.

Looking at other people's code (and I mean more experienced programmers of course) always helped me to learn best-practices, patterns, etc. Also if you does not understand something (why is it there? why is it written that way?) it is very good to ask the guy who wrote it down about his purpose - maybe both of you can learn from these situations.

Also this kind of "learning" is very useful in the future - you can understand other people's code faster or recognize problems by looking at the code.

I think your idea is worth doing and I would encourage you to keep working on it; I am sure I will recommend it to my friends too.

Watchmen is a favourite of mine also - it has a very exceptional role cast with very unique personalities. I would give an advice to whom have not seen it yet: watch the directors cut.

Hmmm. Maybe I would try to gather some money for creating a music instrument shop/service. I like music and technology (behind music) as well - that would be fun!

I also suggest looking for volunteers, I think many people would gladly help you.

This works for me too. For the cases when it does not work, and you have the option, leave it and go rest/sleep/run/etc.

I was playing the bass too and sometimes I also experience pain in my wrists or my hands. Not only when I am coding. Writing is the worst my hands always hurt from writing.

A doctor should help or if it does not, go see another. Of course he will not give you an advice about which keyboard you should buy, but he might tell you that you should have a break and stop coding for a while. Or maybe do some exercises, not sure. :-)

For the record - hd25 is really-really nice but consider AKGs too - I am using AKG k518 from a while now, and it is almost or just as good as the HD25 but have a far lower price.

Projects, projects, projects. In my opinion people need to have successes to get going. "Hello Worlds" and theoretical stuff is useful of course (well, not just useful, you need that!), but I saw many people learning to code without actually solving problems. People, who knew how to do things but never had a real success other than some smaller homeworks. These people could never meet with problems they need to face when developing real applications (version managements, logging, or even getting answers from the Internet).

I would suggest the same as the others wrote before - teach some theory, create a few simple stuff with them, and let them learn :-)

I agree with the others but; design should be important in enterprise applications as well. I have seen many enterprise applications which were designed so badly people can't really use them very well. Of course I am not talking about fancy design things, but their usability sometimes... argh. Though they need to cut down money on something, so they focus on the functions instead.

But - if you want to get attraction (like said below) you need to focus on design. You won't look at a Mercedes if it was ugly.

Good advices down there but the one worked for me: rest a week. Or two. I had the same feeling last year and I was really worried - maybe I am on a wrong path? Then I traveled to my friends in London for a week. After some days without Internet (I only had my PSP with me, but barely used it) I was eager to write some code.

I use an LG GT540. It is pretty slow and buggy with the ram i am using, though... no. I hate it. Really.

You have the option the choose between tasks - when I was freelancing I always tried to pick tasks which required a bit learning but I was sure I can handle it and create a good product. Also It is great if you have a partner who is a bit more experienced than you.

I might add that for learning, Windows is pretty good (now... it was not used to be this way, haha) - though the problem you mentioned consists and it is better to switch to Linux after a while (when you need those gems).

I would say these too. And one more thing - picking good names require an experience itself, too - if you write more code, your names will get better and better. Don't overthink it - if you make a little mistake for picking a not-really-suitable name for something you still have option to refactor your code.

And before I forget - having the opportunity to see more experienced people's code (well, the Internet is perfect for this) can nicely develop this skill.

I would suggest inventing a new world - it is often a great fun for me to discover new worlds and the stories behind it. I think you don't need to reinvent the wheel, just take the best parts of the fantasy worlds you like and from those develop a new-ish thing. Maybe you can start creating a new franchise - who knows?

It is down here too. (Hungary)

For newcomers I always suggest learning Python 2 first mostly because it is easier to find libraries and/or resources for Python 2. Also, I found it very easy to learn Python 3's differences after knowing the previous version.