My father works in electronic maintenance, which is pretty much fixing anything other than light bulbs that break, at NBC4 in Washington D.C. He's worked there for about 20 years and is still near the bottom of the ladder, because they hire new people very rarely.
That's not really what you're interested, you want to do somehting that involves "mucking about with computers". Sorry, but most of the computer stuff lies in network graphics and the weather departments (the writers and related use computers to type stuff up obviously, but you're not interested in that, it seems). Most of the equipment uses "computers", but they're all highly specialized hardware systems the users never see. The places I mentioned before where you do see something that resembles your normal computer both demand specialists in their field. As for IT stuff for the normal machines, it's contracted out to outside firms. There just isn't much to muck around with.
You mentioned that you have expierience in non-linear editing. There are only about 5 editing suites in the building that use it, and they're for high-profile national-network and sports editing. Only their best editors use them. Sorry, there's just not much that the new people get to play with
It's the old thin client very thick mainframe model of the bad old days. We moved away from it for a variety of good reasons. Not the least of which is the fact that it costs a lot more to get the computing power of 20 cheap desktops in 1 mainframe type machine. It's the same reason Beowulf clusters, COWs, and the like were created.
Interestingly enough, the internet model aproaches the thin client model, but I stray from the topic
Spriggan the movie is based on a manga (japanese comic), which was originally translated and published domestically as "Striker" (just as it was in japan), the name was later changed to "Spriggan". The basic premise is that the main character is a failed experiment to create a "Berserker" ("friendly" ultra-powerful killing machines) and now works for the local Big Group Protecting the world retrieving technologically advanced artifacts that could destroy the world if they fall into the wrong hands. Not very deep, but that doesn't keep it from being entertaining.
The movie takes place in the middle of the series and I'm not sure why they chose that part, but the story is simple enough that with some filling in the audience can easily understand what's going.
Who's a monopolist?
on
.NET at JavaONE
·
· Score: 2, Insightful
Using its own standards and APIs. As McNealy put it, "The community aspects of Sun ONE will win over.NET. It's mankind versus the monopolists."
Naming your product "Sun ONE" is pretty blatent if you ask me, at least M$ give you a break with names. Sure it uses open, standard interfaces between components but that's only because they're the minority so it's to their advantage to be interpolation. I doubt it would stay that way once they've won (I think the pun is intended). Sun is just another big company trying to make money so you can't get too upset qwith them for trying to gain market share by recruiting anti-M$ people. Hiding your monoply-in-the-making within an anti-monoply ball is the logical strategy afterall.
Another thing that bothers me is that Sun has always, at least in the public works I've seen, dismissed their competetiors and childishly called them names. The strategy of pretending that the competition isn't competition at all is a tried-and-failed one. I would much rather see Sun encourging intelligent debate and taking note of the arguments on both sides to improve their platform.
The only way napster could get people to pay for a service provided freely by others is to make a vast improvement. Looking at what they have now, they offer no new features over Gnutella clients, except perhaps chatting and "paying the artists" which isn't enough to make most people pay for it. The only reason to use it is to clear your conscience. Just buying the cd (used, possibly) is cheaper for that.
Re:Perl isn't unreadable - some Perl programs are
on
Exegesis 4 Out
·
· Score: 2, Informative
Ruby uses #{} within a string to indicate that the expression, brackets, and '#' should be replaced with the value of the expression within the brackets. So 'put "Hello, #{foo}"' would print "Hello, world" (assuming foo=="world").
Description in name, not in easily twisted prefix
on
Exegesis 4 Out
·
· Score: 1
Good naming of variables, software design, and documentation should be what makes it clear what a variable is, not a symbol prefix that can be easily something other than what you think of first. A well named variable will allow you to make a good guess about how to use it. A variable called "userName" should be a string, "User" should be a class that represents users, and "users" should be an array of User objects.
You mention that you have to go to another file to find the decleration of the variable, no function should span multiple files and strongly typed variable like Java and C++ force you to place the variable type in the function header, decleration, etc. This tells you what the function is (informing/reminding you of paramater and return types as well) and if you haven't read it you really should to prevent altering the intended behavior.
Pre-6 perl does an excellent job of making it easy to write obfuscated scripts by stuffing so many interpretations into one symbol ($foo can be a scalar, refrence(which is a scalar but is not used the same way), or file handle)and having a list of inconsistencies so long that comprehensive documentation is insanely difficult. The language as it stands at perl 5 does little to help understanding of a script, and more to make the task difficult.
Slashdot Mirror
That's not really what you're interested, you want to do somehting that involves "mucking about with computers". Sorry, but most of the computer stuff lies in network graphics and the weather departments (the writers and related use computers to type stuff up obviously, but you're not interested in that, it seems). Most of the equipment uses "computers", but they're all highly specialized hardware systems the users never see. The places I mentioned before where you do see something that resembles your normal computer both demand specialists in their field. As for IT stuff for the normal machines, it's contracted out to outside firms. There just isn't much to muck around with.
You mentioned that you have expierience in non-linear editing. There are only about 5 editing suites in the building that use it, and they're for high-profile national-network and sports editing. Only their best editors use them. Sorry, there's just not much that the new people get to play with
Interestingly enough, the internet model aproaches the thin client model, but I stray from the topic
The movie takes place in the middle of the series and I'm not sure why they chose that part, but the story is simple enough that with some filling in the audience can easily understand what's going.
Naming your product "Sun ONE" is pretty blatent if you ask me, at least M$ give you a break with names. Sure it uses open, standard interfaces between components but that's only because they're the minority so it's to their advantage to be interpolation. I doubt it would stay that way once they've won (I think the pun is intended). Sun is just another big company trying to make money so you can't get too upset qwith them for trying to gain market share by recruiting anti-M$ people. Hiding your monoply-in-the-making within an anti-monoply ball is the logical strategy afterall.
Another thing that bothers me is that Sun has always, at least in the public works I've seen, dismissed their competetiors and childishly called them names. The strategy of pretending that the competition isn't competition at all is a tried-and-failed one. I would much rather see Sun encourging intelligent debate and taking note of the arguments on both sides to improve their platform.
The only way napster could get people to pay for a service provided freely by others is to make a vast improvement. Looking at what they have now, they offer no new features over Gnutella clients, except perhaps chatting and "paying the artists" which isn't enough to make most people pay for it. The only reason to use it is to clear your conscience. Just buying the cd (used, possibly) is cheaper for that.
Ruby uses #{} within a string to indicate that the expression, brackets, and '#' should be replaced with the value of the expression within the brackets. So 'put "Hello, #{foo}"' would print "Hello, world" (assuming foo=="world").
Good naming of variables, software design, and documentation should be what makes it clear what a variable is, not a symbol prefix that can be easily something other than what you think of first. A well named variable will allow you to make a good guess about how to use it. A variable called "userName" should be a string, "User" should be a class that represents users, and "users" should be an array of User objects.
You mention that you have to go to another file to find the decleration of the variable, no function should span multiple files and strongly typed variable like Java and C++ force you to place the variable type in the function header, decleration, etc. This tells you what the function is (informing/reminding you of paramater and return types as well) and if you haven't read it you really should to prevent altering the intended behavior.
Pre-6 perl does an excellent job of making it easy to write obfuscated scripts by stuffing so many interpretations into one symbol ($foo can be a scalar, refrence(which is a scalar but is not used the same way), or file handle)and having a list of inconsistencies so long that comprehensive documentation is insanely difficult. The language as it stands at perl 5 does little to help understanding of a script, and more to make the task difficult.