large training effort to use them and the effort to move your documentation into them
There was a discussion on Slashdot a couple of months about a more sophisticated file system.
In my opinion we should extend file systems instead of replace them because users and support staff are used to them and their stuff is already there.
If file systems easily allowed meta data to be attached to files and folders, then semi-structured queries etc. could be done on them. "Views" could be made of combinations of folder trees, similar to RDBMS views. Rough example:
define view foo as /serverX/zip/grog/stuff/*.pdf /serverX/zip/grog/stuff/snerg/*.* /serverY/derf/*.* -subfolders end view; select file_name, create_date, author, office from foo where create_date <= '12/31/2009' order by file_name;
While there is an existing standard on file meta-data, it appears inconsistent across vendors/OS/versions, poor support by file API's, and poorly tested.
I'm thinking of adding a secondary system on top of the file system to store meta-data rather than depend on vendors' meta-data. I have a rough-draft for an open-source product. (It won't be very fast, but if it catches on, optimizers could be added.)
It could also serve light-duty CRUD, such as specialized tracking systems.
A more general IT course would be better as a requirement. It could cover the relationship between clients and servers/clouds, what an OS is and isn't, normalization and data relationships (one-to-many, many-to-many, etc.), pro's and con's of different kinds of data keys/id's, encryption techniques, etc.
They will likely need to know a bit about such in the work-place even if they are not a coder. Coding is only one aspect of IT.
It's better 100% of students are slightly less naive about general IT which at least 90% will use at work, compared to 100% prepared for a career in coding that only 3% will end up in. It's not a logical use of school resources and time to put a coding class over an IT class.
I agree. There's usually very little incentive for engineers to cheat like that.
For one, their paychecks won't very that much between cheating and non-cheating. They'll likely get a paycheck whether the car is profitable/successful or not. People rarely cheat this big unless there is a clear and large benefit to them.
Being fired due to a downturn in sales is always a worry, but in this case there is a roughly comparable risk of being fired by management for cheating.
Engineers risk being caught by both managers AND the public (external people). If top managers cheat, they only have to worry about being caught by the public.
Thus, the engineers have to weigh the incremental possible raise if sales are successful versus the risk of being fired if caught by management. I don't see a clear net benefit here.
Upper management and CEO pay/incentives are usually much more leveraged on the rise or fall of sales and profits.
Unless something really odd is going on, it's not the rank and file engineers who made the final call. It would take more than one engineer to pull it off, and a group of engineers will know that the "incentive math" is not in their favor.
Generally the group of engineers needed to pull it off haven't chosen each other, they are just happenstance co-workers such that it's not comparable to a say self-selected crime gang.
Let the market...the consumer...not the government...decide how much pollution is too much
As the early history of industrialization shows, unregulated companies have no problems poisoning people for short-term profits. Aggressive business people tend to only think about 5 years out. If they believe the chances of getting caught is relatively low for the next 5 years, they'll often gamble to get here-and-now power and wealth. They are thinking with the "2nd head".
By the time 3-eyed babies appear, the perps or their trail may be long gone.
That might be true, but then the real problem is lack of a legitimate laugh track, not the mere existence of one. (Or, getting a bigger sound library.)
Slashdot Mirror
It's better if you read it to this tune:
https://www.youtube.com/watch?...
If you count spam, that's already true. Bots mutate and reshuffle the words to get past spam filters.
1. Go to Mars
2. Come back
3. ???
4. Profit!
They learned from USA
Maybe it's a scam to sell less bacon. 3 strips will be 3 tiny dental-floss-sized strips now. Marketers realized that "strip" was never defined.
Something is really off about the "new economy".
Twitter is still considered a "rising star", and one of the biggest and most used tech brands.
YET it only employees about 4k people AND is laying off.
Craiglist is also one of the most-used services, yet only employs about 60 people.
How do you propose punishing them?
There was a discussion on Slashdot a couple of months about a more sophisticated file system.
In my opinion we should extend file systems instead of replace them because users and support staff are used to them and their stuff is already there.
If file systems easily allowed meta data to be attached to files and folders, then semi-structured queries etc. could be done on them. "Views" could be made of combinations of folder trees, similar to RDBMS views. Rough example:
While there is an existing standard on file meta-data, it appears inconsistent across vendors/OS/versions, poor support by file API's, and poorly tested.
I'm thinking of adding a secondary system on top of the file system to store meta-data rather than depend on vendors' meta-data. I have a rough-draft for an open-source product. (It won't be very fast, but if it catches on, optimizers could be added.)
It could also serve light-duty CRUD, such as specialized tracking systems.
A more general IT course would be better as a requirement. It could cover the relationship between clients and servers/clouds, what an OS is and isn't, normalization and data relationships (one-to-many, many-to-many, etc.), pro's and con's of different kinds of data keys/id's, encryption techniques, etc.
They will likely need to know a bit about such in the work-place even if they are not a coder. Coding is only one aspect of IT.
It's better 100% of students are slightly less naive about general IT which at least 90% will use at work, compared to 100% prepared for a career in coding that only 3% will end up in. It's not a logical use of school resources and time to put a coding class over an IT class.
https://www.youtube.com/watch?...
Congress?
I agree. There's usually very little incentive for engineers to cheat like that.
For one, their paychecks won't very that much between cheating and non-cheating. They'll likely get a paycheck whether the car is profitable/successful or not. People rarely cheat this big unless there is a clear and large benefit to them.
Being fired due to a downturn in sales is always a worry, but in this case there is a roughly comparable risk of being fired by management for cheating.
Engineers risk being caught by both managers AND the public (external people). If top managers cheat, they only have to worry about being caught by the public.
Thus, the engineers have to weigh the incremental possible raise if sales are successful versus the risk of being fired if caught by management. I don't see a clear net benefit here.
Upper management and CEO pay/incentives are usually much more leveraged on the rise or fall of sales and profits.
Unless something really odd is going on, it's not the rank and file engineers who made the final call. It would take more than one engineer to pull it off, and a group of engineers will know that the "incentive math" is not in their favor.
Generally the group of engineers needed to pull it off haven't chosen each other, they are just happenstance co-workers such that it's not comparable to a say self-selected crime gang.
1. Don't use Perl
Just install Windows 8.0 and then Windows 3.0.
and only 13 know it.
The word should probably be "consciousness."
You have never slipped up?
Reminds me of the old April 1 Slashdot prank.
Classic.
So? That makes life easier.
Just for the shear hell of it, I'd like to see your impression of a gay cow.
You marketers
As the early history of industrialization shows, unregulated companies have no problems poisoning people for short-term profits. Aggressive business people tend to only think about 5 years out. If they believe the chances of getting caught is relatively low for the next 5 years, they'll often gamble to get here-and-now power and wealth. They are thinking with the "2nd head".
By the time 3-eyed babies appear, the perps or their trail may be long gone.
Space critters: "Humanize it from orbit just to make sure."
This is beginning to sound like a Linux dev discussion.
A.K.A. "Trump Mode"
Losers!
That might be true, but then the real problem is lack of a legitimate laugh track, not the mere existence of one. (Or, getting a bigger sound library.)