The thing about revolutionary inventions is not that they're made by geniuses of immense minds. It helps, but it isn't necessary. All you have to do to invent something of value is to solve a...
The thing about revolutionary inventions is not that they're made by geniuses of immense minds. It helps, but it isn't necessary. All you have to do to invent something of value is to solve a problem some people have.
The more people have the problem, the more intense that problem, and the better your tool solves it, the better you'll be thought of as an inventor, regardless of the field.
He didn't write git as you know it in a week, he wrote the simplest possible implementation in a week. The former would be an impossible task, but the latter is quite attainable with a few years...
He didn't write git as you know it in a week, he wrote the simplest possible implementation in a week. The former would be an impossible task, but the latter is quite attainable with a few years experience and a little bit of knowledge about version control. Keep in mind that he purposely chose to avoid some of the more challenging problems such as storing the diffs (git is snapshot based) and in doing so he made a better product. It just goes to show, sometimes trying to solve a problem in the dumbest way possible actually does a better job, so it's good to try!
Man, sometimes I'm feeling okay about my programming skills and then I've gotta go ahead and read that.
The thing about revolutionary inventions is not that they're made by geniuses of immense minds. It helps, but it isn't necessary. All you have to do to invent something of value is to solve a problem some people have.
The more people have the problem, the more intense that problem, and the better your tool solves it, the better you'll be thought of as an inventor, regardless of the field.
He didn't write git as you know it in a week, he wrote the simplest possible implementation in a week. The former would be an impossible task, but the latter is quite attainable with a few years experience and a little bit of knowledge about version control. Keep in mind that he purposely chose to avoid some of the more challenging problems such as storing the diffs (git is snapshot based) and in doing so he made a better product. It just goes to show, sometimes trying to solve a problem in the dumbest way possible actually does a better job, so it's good to try!