Suddenly, being an IT professional doesn't seem that bad...
186 karma · joined February 18, 2008
Suddenly, being an IT professional doesn't seem that bad...
- Emerson
That is, using div vs. table or vice versa, just because you're "supposed to" strikes me as being contrary to the true hacker mindset.
Democracy says that this place is peopled with hackers and if the hacker citizens upvote a story then it is, ipso facto, of interest to hackers.
Mobocracy says that demi-hackers trickle in and start upvoting stories and posting comments that attract quasi-hackers. The quasi-hackers then attract non-hackers and you eventually no longer have a narrow community. The stories that appeal to the lowest common denominator then rise to the top, due to sheer statistics.
(Move along. Nothing to see here. All of you redders and diggers can go back home now.)
Also, those have to be cheapest cube walls I've ever seen. The desks are the only things holding them upright.
Good luck getting people to be picky.
It's a one-stop antique store, swap-meet, and Crazy Louie's surplus store. I'd much prefer for the sellers to lower their prices to attract the customers, rather than vice-versa.
If that's what they'll eventually evolve into, good on them.
With each level of indirection, you get one more level of sophistication, but at the cost of one more level of complexity. OO has tons of indirection (+cough+ polymorphism +cough+).
Back in the old C++ days, before decent IDE's, I remember tracking through multiple code files in several different directories, just to figure out if an add operator had been overloaded - and if so, how. Man, was that a complex pain!
Lately, with Java, I've found myself in the same situation, but with XML config files. Some Java developers just love XML config files and often use them to direct reflective code execution (dynamic language envy). Needless to say, my IDE's are failing me again.
Erlang comes to mind as a good event-based language. Strangely, it is rarely (if ever) used for UI.
"the Singleton "pattern" encourages you to forget everything you know about OO design, since OO is hard, and procedural is easy."
Why, oh why, are we encouraging people to use OO 100% of the time, when it's admittedly harder than the alternatives? (I'm looking at you, Java.) Methinks the bandwagon continues to play on, even after two decades...
Theft, by definition, transfers value from the original possessor use to the thief - a zero sum transaction where the thief gains at the owner's loss. Copyright infringement does not do so. It only deprives the original possessor of potential future value. (You could even argue within some legal jurisdictions that there is copyright infringement only when the pirate derives commercial gain from the copy.)
Post-production houses and graphical design companies often demand that all job applicants already have Photoshop experience. Yet for someone who doesn't already have a job, they can't afford Photoshop in order to get experience. The unspoken industry solution is that everyone has a pirated copy of Photoshop for personal use.
Also mentioned is that the big 3D modeling/rendering packages that everyone uses for production work (3D Studio, Maya, and LightWave) also happen to be the most pirated 3D software. Coincidence? Is the dog wagging the tail, or is the tail wagging the dog?
Honestly, I have just as much of a laissez-faire libertarian philosophy as the next hacker, but there are plenty of other forums that are better suited to spreading the word. (cough reddit, cough digg)
When the code executes on a remote server, however, you have a completely different kettle of fish.