One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
It's even a good idea if you do know how to implement it.
Not everything that you can program is worth doing.
It's best to gauge whether the thing that you are writing is interesting someone else before you spend all that time coding.
So how do you know whether that could become interesting?
Tom Preston Werner who founded GitHub has a simple answer:
I'm glad I'm heading towards that direction. From this post I can figure it's somewhat like making a movie - you first write your script. The final cut will be a lot different from the original script, but the script is 1. the first thing executive producers will see to decide if the movie is worth the money or not; 2. directions for the whole crew know where to go. Thanks for sharing!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's even a good idea if you do know how to implement it.
Not everything that you can program is worth doing.
It's best to gauge whether the thing that you are writing is interesting someone else before you spend all that time coding.
So how do you know whether that could become interesting?
Tom Preston Werner who founded GitHub has a simple answer:
write its README first
tom.preston-werner.com/2010/08/23/...
I'm glad I'm heading towards that direction. From this post I can figure it's somewhat like making a movie - you first write your script. The final cut will be a lot different from the original script, but the script is 1. the first thing executive producers will see to decide if the movie is worth the money or not; 2. directions for the whole crew know where to go. Thanks for sharing!