Hacker Newsnew | past | comments | ask | show | jobs | submit | ricklancee's commentslogin

That seems like a really good idea, might try it next time


> Engineers are pressed to get it done anyway possible and as fast a possible. The ones that push back get fired or moved to another project.

This. Also incompetent engineering teams could be a major factor.


I don't see the point of this other than the "cool i spend 50% more time in [insert language here] than [insert language here]" factor.

Also: http://martinfowler.com/bliki/CannotMeasureProductivity.html


For me, it's a tool to track my time i'm spending on which projects.


How do you track time that you spend on the project that is not done inside the editor; for example research?


Exactly my thoughts. Many projects are more about the research, and less about the time purely spent coding. Many times, my research time > coding time, so it would be cool if WakaTime made a Chrome plugin that could track that time.


I use rescuetime to track browser page titles. I use wakatime for tracking too.


I use emacs and one org mode file per project so it tracks kind of well as long as my research produces notes.

As a proper Emacs user I also do my e-mailing there and my e-mail is in a git repository. Whenever I feel like I haven't got much done in a day I can usually verify that I it was because I spend like half a day writing e-mails instead of coding.

One of the more surprising stats I have found out about myself is that I regulary spend about 5% project time writing git commit messages.

I actually find the most value of wakatime that I can keep track of that I don't work too much on the "wrong" projects. Wakatime has helped me hold off things I should not focus on that much.

Wakatime has at least somewhat reduced my imposter syndrome tendencies because I can use it to disprove the feeling that I'm not getting things done because it tells me that I got things done even if it was not the things I originally had plan to get done.


so web focused is not technical or professional?


How exactly did you test the usability?

The first thing i noticed was the checkbox label "Prevent duplicate votes?" was not clickable.


Good catch! We're fixing it so checkbox label is also clickable and will be pushing out the change shortly.


Done. We've made the checkbox label clickable.


When i can't sleep I usually watch or read something in bed on my tablet until i can't keep my eyes open anymore



The author probaly never worked with a deadline before, where there is no time to build everything custom.


Shouldn't the undefined check be like this?

    if (typeof fruit === "undefined") {
       fruit = "strawberry";
    }
Unless your doing something like:

    (function(undefined) {

    })();


`typeof` is useful when the binding may or may not exist at all, this is almost exclusively an issue with global variables which may not be there (toplevel APIs or libraries missing).

If the binding exists at all, you can just check for its value. And parameters always create a binding pretty much by definition.

So no, there is no reason to use `typeof` to check whether a parameter is `undefined`.

If you fear that somebody rebound the global `undefined` for some insane reason, you can use `void 0` instead.


In ES5+, the global `undefined` is immutable, so it should be pretty safe unless someone declared a local `undefined` var in an outer scope.


I use "var undef;" at the top of a function and never set it to a value. Comparison with === is the same as with undefined. And it's nice for minification.


Nice to know someone else is waking up really early. I started setting my alarm 5 minutes back each day toward my goal of waking up at 4am. I started at 7am now I am at 4:40am and I'm really liking it so far; I get stuff done this way.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: