was able to get it running on windows, so I am happy with it. Needs more in-depth guide so I know what it provides and the reasoning behind ur "sane defaults"
59 karma · joined December 30, 2010
I too was interested in Node.js but I don't like the idea of using JavaScript - I simply prefer python for coding. I looked into it, found the counterpart of node.js in python and am happy with it.
Too much of a hassle to find medias in my social feeds, until made fun with SocialKey:
You can consider it a shortcoming on my part or reality for most programmers, but I don't tend to memorize names of concepts, I just know how to use them. i.e. I may be using inheritance or polymorphism in my code, but my brain does not every time thinks about what these terms mean and am I applying them as they are defined. I have been programming for years and OOP has become second nature to me; I know how to apply OOP, but have long forgotten most of the terms.
In my view, when interviewing, the questions should be practical problem so it tests user's ability to program a solution, not about being able to churn out the definition. Example: If you want to test someone's OOP expertise, give the person a list of classes and ask them to create a UML or how they would structure their classes. Example 2: Give them a problem like, create 2 classes: Animal and Dog. All animals have a name and a dog can bark. Test to see if the programmer would extend Animal class from Dog class, or maybe he decides to make an Abstract class out of Animal class.
The only downside of these questions is that you would need to have interviews who are competent in the OOP concepts themselves. Continuing to ask dictionary questions is a cop-out solution to not having technical interviewers and it is easier for someone to check if interviewee is able to mention some of the keywords that are in the definition you found on wikipedia.
Unfortunately, you will continue to reject most developer job applications and miss out on lot of great candidates.
On serious note:
Problem: Help me manage what I need to do and motivate me to do it.
Issue with every possible solution: there can't be 1-shoe-fits-all.
There are various solutions proposed: 1. Have a "done" list - people get motivated by seeing what they get done and feel good about themseleves when they are reocrding what they have done, and feel bad when staring things they need to do .
2. Pair-wise to-do list. Randomly pair a user to a different user and they both use various means to motivate each other and provide means to help each other. This is social interaction and people feel some responsibility to get things done when they have someone to answer to, while others dont want to expose their private life.
3. Bombard the user with notifications on what needs to get done or give user with positive enforcement every hour, in order to motivate the user.
There are 2 issues to be addressed: Motivation and organization. If the data is not easily organizable, user dont feel like vesting. If user does not have anything motivating to do those actions, rather than procrastinating, your system is plain doomed.
I have similar experience with movies - Dark Knight - I watched it 4 times and each time I find it more fascinating because I saw new details in the movie.
For next batch, I applied as lone founder with no-idea, if you did not get in, seems like I might have similar fate.
2 Eclipse for development
3 Notepad++ For quick changes to codes, write SQL queries and standard tool for storing temporary text.
1. How would you add a new element to an array? PHP: array[] = 2 Python: array += [2]
2. How to combine 2 arrays? PHP: ?? array_merge(...) ?? Python: array += array <- it is as simple as appending to a string.
Lot more fun examples: http://python.net/~goodger/projects/pycon/2007/idiomatic/han...
side-note: How about a rename to something with django in it? i.e Better Django CMS?
Personally, Mezzanine does not rolls right off my tongue and my brain is just refusing to memorize it.
1. If I am right, it validates my understanding of the concept.
2. If I am wrong, it bring misinformation to surface and gives me a reason to go over previously discussed material. If I never had experience where I was wrong, it puts me in the cycle of "I know everything, so I don't need to study."
3. It keeps me awake in class because asking and answering questions requires paying attention in class.
If I have such free time, there is always something else work-related for me to do, since I am not tasked with only coding. - Go over the code I have just written.
- It is time to commit, so look at diffs and commit.
- Check the server's performance.
- Go over list of pivotal stories and see what I be doing next.
- Take a break, go for a walk around in the building, check out the beautiful view.
- Go over calendar and see if there is anything I need to not-forget.
- Read something related to programming, a book at work or an article.
- Have a talk with fellow co-workers about something that has been on your mind.
Python idioms : http://python.net/~goodger/projects/pycon/2007/idiomatic/han...
I have done something similar but based on Vista : vidshome.com