350 karma · joined March 30, 2009
When all its doing is breaking a neck and moving to the next one, it's hard to say that it was just hungry.
That may be his definition but from my experience, when I hear people talking about professionalism, they're usually either using it as a way to complain about someone else or to boost their own ego. I haven't known many people to think of professionalism as defined above. Seems like more often than not, its used as leverage to argue for exactly what he says it does not mean.
As far as I could tell, the author got an email from a friend looking for help and instead of helping him, he decided to humiliate him on the internet.
Time is going to pass anyway, so just do it now. "Too popular" doesn't mean there's no more value to create.
Do you think this is a good scenario for using print statements?
I often still find myself adding print statements and rebuilding due to the complex nature of debugging this particular (multi-process) system. For obvious reasons, rebuilding is very inefficient. Interested in any other suggestions or references you might have.
I always see the recommendation to spend a huge effort on business planning, etc., up front before you start. This can often lead to giving up on the idea, though. Yeah, you might say then that the person doesn't have the passion to be successful if that is the case but alternatively, I've found that with software, simply doing it and getting something working is what really generates the motivation.
Maybe business planning is good but it doesn't necessarily need to be the first thing you do and it's not worth it if the result is that you do nothing instead.
I'd argue to just do something first.