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).
We don't need to bombard kids with technology, we need to bring them up with essential skill such as literacy, printing / handwriting, math, science, history and in general all the basic skills that allow them to learn and develop WITHOUT getting technology involved. I would go as far to say that students shouldn't even hand in word processed assignments, unless it's absolutely necessary.
I'm not saying we should have no technology involvement, I'm saying we should limit it. If you want to offer a computer basic course, awesome! If you want to accept typed / word processed assignments, awesome! Just don't mandate it. Kids need less technology and more quality, this entire plan from the get go was to offload the responsibility of teachers and subvert known, good, working practices for teaching.
The school board got bit by trying to fool around, well lesson learned, next time don't try to reinvent the wheel, that wasn't broken and didn't need updating.
My cousin is studying hoarding disorder and how to overcome it. She's been given money, A LOT of money to study this. None of the people in her study have any kind of chemical imbalance, which as I already stated would completely change the landscape. So far her research at a PhD level has determined that people with hoarding disorder attach false emotional states to objects, which means in other words, they can't rationalize emotion. That's not science, that's a lack of emotional control, they need to mature and stop playing cry baby.
My Sister studied depression, again in people with NO chemical imbalance. People felt sad because they didn't want to grow up and face the world for what it is! Again, not science. More proof people are cry babies.
I could keep going but it all the same story.
With the exception of chemical imbalance, every single person is directly responsible for there actions, case closed, now lets stop using the term science to describe excuse generation.
Any time a user has to enter the same information more then once or has to navigate complex boxes, tabs or windows, you've FAILED!!! Software development has become more about the developer and less about the user. It's become more about maintainability and less about functionality and ease of use.
For instance, currently I'm the sole developer of a major (NDA protected), application which carries out automated testing, logging and stressing of almost 70 products. Each of these products requires it's own set of special criteria, it's own set of special resources and it's own set of requirements, it has to be used by workers in 3 countries, including China and it has to log everything back to massively redundant databases. The expected experience of anyone using my software is basically 0, we don't need them to have to any idea about the products, any idea about the databases, any idea about anything, other then pressing two buttons, (Setup and Commit).
The users don't enter manual information, they don't even have to validate test results as that is taken care of in the program. At the end of testing they're given a number which auto posts via secure transfer to us and shipping information is automatically populated and carried through the system, at which point production gets a label and a box. This is how proper and well designed software works!
Now some smart ass is going to say that it can't work this way in the medical field because you require manual entry, well automate as much as you can and use automated systems to the check the rest. In Ontario at least, I'm not sure about other places, everything is fuelled through our health cards, one scan and the hospital knows all about you, everything they need is displayed. This is step one where automation can take over, why not pull that data and auto populate the system, log it back to a database and secure it! Second step would be to collect all the vital stats from all the machines you're tested on and log that against you. Once you have both sets of information, use automated scanning to generate likely issues you could have and etc...
If done right, the user, nurse or doctor should have very little work to carry out, maybe a check box here or there or a line descriptions, but basically everything else can be automated. If software developers aren't going to go the extra mile and make everything a smooth experience and because of that people suffer, that developer is at fault.
Step 2 would include choices such as hit the breaks if it would work. I just used summary steps to make it easy to understand.
Your plates store information about your car, hence you know from looking the number up, everything to know about the car via reference lookup. Wireless is easily fast enough to deal with the latency for it so no problem there, infact you could also get information about the driver, so really you do have a good deal of information at your car to decide what to do.
If the software fails for some reason, a good hardware design will step in to save it so again no problem
Lets just assume the object we're concerned about is in front of you!
Step 1: Turn on all cameras and sensors
Step 2: Cut all engine power
Step 3: Using the license plate of the car in front of you determine what would happen if you hit it.
Step 4: Compute what would happen if you hit the person
Step 5: What ever has less damage execute
Step 6: Dump massive logs to solid state storage
Step 7: Call police, send them the files automatically
Step 8: Run diagnostics to determine driver error or manufacturing issue
Step 9: Done.
Not that hard to do