- A 'developer' is paid to create code that works within the company's contrived runtime environment and passes a few stages of testing, while a 'software engineer' is also paid to ensure the code actually works reliably in this nebulous abstract construct called the "real world" - customer/client installations where there are innumerable environmental variables and things that can go wrong.
- A "developer" nods timidly and reluctantly to Murphy while passing in the corridor. But the software engineer says "Thanks for another great night. What would you like for breakfast?"
- A "developer" goes whining to her/his team leader when the tools or OS play up. A software engineer cracks out the machine-code debugger, logic analyser and oscilloscope, traces all the API calls, and spits out working patches for the bugs in the libraries, drivers and kernel.
If I had some plant that was failing at 3:15am and costing me a fortune, I know which I would prefer to have on site.
I'm thinking along the lines of the emacs "spook" function, amongst other things. You just need enough a large enough group of participants working together.
The system can be trained in weird ways. For instance, if enough people in enough places scratch their noses with their left hands, then break out in a mock fight, the system will learn to sound the alarm every time someone scratches their nose with their left hand.
Or, for something more socially useful - have people pull out a cellphone, talk for a few seconds, then pull out a mock gun and pretend to mug others. Then, the system will freak out every time some annoying jerk pulls out a cellphone in public. Along that same theme, train the system to send in the troops whenever someone adjusts their underwear in public, or picks their nose, or farts loudly...
Link to Original Source
* Its memory bloat teaches us to be mindful of our resources, both within the computer, and our use of our resources in everyday outer life.
* Its slowness helps teach us patience.
* Its slow startup teaches us that wonderful things don't happen instantly, and that we need to lose our attachment to time
Stay away from Chrome - it feeds the ego by promoting our addiction to instant gratification
Framing the discussion as "piracy reduction" is long obsolete. Might as well call it a "reduce gas diffusing in a vacuum" conference.
They need to restart with a premise of "finding ways for content creators to be rewarded for their works". Then we might start getting some workable and relevant ideas.
The idea is that when logged in to the sandbox account, there will be nothing to indicate that it's a sandbox login. You will even be able to create a nested sandbox within this sandbox, with no nesting restriction.
With this in place, an employer will never know whether his/her employee or candidate has given up the master password, or just a sandbox password — with the ability to nest the sandboxes, account holders will have plausible deniability and will regain some control over their privacy in the event of duress attacks."
Link to Original Source