Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
- A Zoomable User Interface. The project Piccolo http://www.piccolo2d.org/ is really nice.
- A Powerwall http://www.cs.uaf.edu/2007/powerwall/ (A Beowulf cluster with high end video cards)
Both tools combined allow you to easily visualize large data sets and adjust the resolution of your data.
People who use proprietary solutions are not ass clowns. People who believe that proprietary solutions are the only solution are ass clowns.
"That statement is not without merit. I can find an IT staff member who is familiar with Active Directory in about 30 minutes. Finding one who is familiar with your customised LDAP-based authentication scheme is going to take longer, and probably going to cost me more. For a small business who cannot afford to pay premiums for highly specialised knowledge that they don't really need, or experience lengthy hiring delays, this might be important. The only error that statement makes is implying that industry standards are exclusively the domain of windows, which is not always the case."
Lets differentiate between the two types of ITers. The nerds and the no talented ass clowns.
I am a nerd. I am in it cause I love technology and I love the concept of open source.
The no talented ass clown is a person that will write a statement like this, "Open Source Solutions Although many open source solutions are available that will provide similar system functionality to a Windows environment at a lower cost; for mission critical hardware and software itâ(TM)s important to follow industry standards and use products which can be easily supported if a staffing change were to occur."
And I've found that system administrators who have not developed significant programming experience also have difficulty with basic system administration concepts. The most basic of these is that any system is a particular instance of a certain class. System administration amounts to maintaining a code base written in an ultra high level object language. That's if you're competent.
I believe the inverse of this is true. While in graduate school I worked as Sys Admin and Web Developer. After a year and a half of mostly being a sys admin I moved to a different job that emphasized development. If you do not understand how mounted file systems, web servers, firewalls and network centric databases work you are going to be SOL when it comes to finding a novel solution in software development (unless you like re-inventing the wheel or write enterprisey type software). Being a sys admin you get to play with all the high level tools for doing systems integration. As a software developer you build solutions to individual problems.