This is Why You Spent All that Time Learning to Program
prog21.dadgum.com
prog21.dadgum.com
It's not computer programming that's special. It's computers themselves -- they have greatly lowered the barrier to entry for many creative professions. (For which we must thank programmers, of course!)
You can create anything. Anything. Want to write a database? Go ahead. Hack on a GPU, nothing is stopping you. Make a recommendation engine? Why not? A game? Trivial (to get started at least).
Once you know how to program (not just one language, some high level stuff and some systems stuff) and know the surrounding tools and communities around the languages sometimes you'll feel like all you want to work on is stuff that pushes your knowledge, even if you could easily make a Exec type of app that would make you more money than programming something that is new to you, like an operating system.
It is a strange situation.
The equivalent of making fundamental changes to a TV station in IT is to use your CS degree to make Facebook allow customised homepages in the style of MySpace. The fact that you can make a Facebook/MySpace clone at home in a few night compares to buying a video camera and recording your version of the news in your kitchen.
Now, I agree with the conclusion: Computer programming is the great equalizer: for the low cost of a computer, a few books and an Internet connection, anyone can build the next Facebook. There are literally no further barriers.
A skilled developer can single-handedly shake up the paradigm and drive things in a new direction. The real challenge for the organization that grows up around that game-changing idea is to avoid behaving like the one it replaces.
So, I guess, building a good app is even harder then creating good TV-channel in some way (if you have enough money for the second, of course :)).
But that makes the whole thing much more interesting. You know we have a song called "Men in front of the monitors". I won't translate it, here's Google Translate variant:
"Those eyes could stare into the distance and look for land on the horizon. They could tear from the cold mountain tops or from the dry dust storm in the desert. Those eyes would go blind from the white snows of the polar dim light or navigation devices. They could, without blinking, pierce the night and see the stars ... But those eyes looking at the screen The man's eyes at the monitor
These hands could compress the steering wheel. These palms can be abraded on the ropes and sails and ropes the front. The fingers could be cut by the rocks and ice. They could turn black from the fires and winds, they can become hard and dry, but relate to women's leather soft and strong, taken by the waist or shoulders as take forever .. But they quickly ran her fingers over the keys .. men are in the monitor
These individuals could be weather-beaten all the winds, they could become peaky and whip wrinkles: fine wrinkles around the eyes, deep forehead. These cheeks can become hollow and unshaven, the lips can become dry and cracked from thirst in the blood, but to be able to kiss her so, so touched his lips to your favorite ... And those lips are stained from coffee, tea and cigarettes these persons in the pale blue light of the screens ... Men have monitors
Those eyes are tired of sleepless ... These fingers are running over the keys ... But it seems that the fingers grip the steering wheel, paddle, or compress or squeeze the shoulders of wonderful ... Men have monitors"
Well, the whole point is that nowadays all discoveries are made near the monitors as they were made in faraway seas and countries. (although song is not exactly about it - it's just my thoughts about it)
Isn't that the whole point (let the customer decide)? It's your project and you can design it any way you want as long as it works. You can try something new but it doesn't mean you'll be popular.
Yes you can always try something new, but IMHO you're wasting time if there's no real purpose - other than taking a totally new approach by breaking common rules - in the long run.
You're arguing something that no one has mentioned.
It's a conclusion to this statement.
I knew I was in deep when in college I started bringing my c++ book to drama rehearsals. . .
And I'm fine with that conclusion
I just spent a few weeks studying OOP and the best practices of implementing the MVC pattern and I'm not one iota closer to a working prototype. I can easily knock out a quick prototype of my idea but I'm imprisoned by exactly what the author talks about. I'm trying to do things as others always have instead of just doing it. No one is looking over my shoulder waiting to give me a grade so why not just fucking knock it out and fix things later.
I like this guy. His other posts are all real gems too and fit into this pattern.