Well, the business community still thinks that the software of the world is made up by celibate geniuses pulling all-nighters. Managers dont have a clue unless they're programmers too.
Until the software world is converted to an ENGINEERING field, with project design ( my specialty ) as the FIRST thing done ( rather than the release date and suggested retail price ), and a rigirous in-house testing phase done with a re-programming phase LAST the software of the world will be buggy, just like everything else that's released onto the public without proper design and testing
Keyboard evolution seems to be similar to calculator evolution -cheaper ( yes, cheap...), multiple-function buttons, and jazzy looks......
but not to the extent of specialty markets!
programmers, graphic artists, gamers, businessmen, stock-market fiends,CAD specialists,
and the inevitable Linux keyboard...complete with a little penguin button
I am sure of a set of niche markets......
SPECIALTY keyboards!!
For programmers: extra keys, programmable for the
C/C++ crowd and the colons, pipes, and the above-128 ASCII codes....
For graphics people: an RGB "mouse touchpad", layer functions, filter functions........
And what is it about the stupid keyboard and mouse connectors?
Cheesy! Easy to knock loose, in the back of the machine,
they flex on the motherboard......
and the da** MS OS wont allow connection to be broken
so it wont work unless powered down, jiggled, then rebooted!
( reboot, sounds like MS ! I don't know about Linux, but I suspect the same sort of programming.... or is this a BIOS/Hardware problem?)
I'd also like a joystick with a mouse switch/connector so I can use the joystick as
a mouse ( programmable buttons ! throttles!
x-y positions! should be easy! )
And why isn't the CMOS/Bios settings available to the OS to change? I might like to disable a drive or port
while installing software, or to change the equipment attached to it.....
( hot swap for the personal PC isn't recommended, since the design engineers aren't allowed to spend time to actually design the things properly)
Standardized connectors, properly labelled for the speaker connection, PWRON switch, Reset switch, HD LED connectors, so I dont need a magnifying glass to make the connections to the motherboard!
Cases! hard to open, no room to get a hand in for connectors, not enough flow-through ventilation, poor mounting designs for the Hard drives......
Ideas and gripes, just like a programmer!
Engineers follow certain rules and procedures. Among them are the design constraints and requirements. ( What it is supposed to do and where it is supposed to work, limitations on loading, temperature, air pressure, wind loading, whatever is applicable ). Then there is the failure analysis ( NASA does this with excrutiating tediousness ) which is supposed to be the troubleshooting guide. This sort od designing would cost ( see the $ 60 Billion ststement) more, but how much would it save in terms of wasted time for rebooting, installing patches, re-installing, etc ? ALSO: the design environment is supposed to be defined. this is not possible with M$, since not only is the source not open, but the versioning problem is unmanageable ( see any set of comments on DLL-HELL ) IS it possible ? yes, if the programs dont rely on system DLL's. Yes, if the registry is bypassed and ini files are used. Yes, if the directories and 'microsoft-assisted installs' are bypassed.
YES!! Absolutely!
They hold 'in trust' information about us,
and the consequences are possibly extreme
( financially ).
If a crime is being comitted , like a break-in,
and a person sees it, and doesn't report it, then
they become an accomplice. Same thing here.
Well, as a general rule, I dont install MS software until the third service pack comes out.
This is due to the multitude of problems that come with MS new releases.
As for security, why haven't the web and OS programmers set up a VM for browsers and email
with no access to the underlying OS?
A separate VM for each logon, and the user just kills his own VM..........
Slashdot Mirror
Well, the business community still thinks that the
software of the world is made up by celibate
geniuses pulling all-nighters. Managers dont have a
clue unless they're programmers too.
Until the software world is converted to an
ENGINEERING field, with project design ( my
specialty ) as the FIRST thing done ( rather than
the release date and suggested retail price ),
and a rigirous in-house testing phase done with a
re-programming phase LAST
the software of the world will be buggy, just like
everything else that's released onto the public
without proper design and testing
Ignorance is only an excuse the first time. Once.
Keyboard evolution seems to be similar to calculator evolution -cheaper ( yes, cheap...), multiple-function buttons, and jazzy looks...... but not to the extent of specialty markets! programmers, graphic artists, gamers, businessmen, stock-market fiends,CAD specialists, and the inevitable Linux keyboard...complete with a little penguin button I am sure of a set of niche markets...... SPECIALTY keyboards!! For programmers: extra keys, programmable for the C/C++ crowd and the colons, pipes, and the above-128 ASCII codes.... For graphics people: an RGB "mouse touchpad", layer functions, filter functions........ And what is it about the stupid keyboard and mouse connectors? Cheesy! Easy to knock loose, in the back of the machine, they flex on the motherboard...... and the da** MS OS wont allow connection to be broken so it wont work unless powered down, jiggled, then rebooted! ( reboot, sounds like MS ! I don't know about Linux, but I suspect the same sort of programming.... or is this a BIOS/Hardware problem?) I'd also like a joystick with a mouse switch/connector so I can use the joystick as a mouse ( programmable buttons ! throttles! x-y positions! should be easy! ) And why isn't the CMOS/Bios settings available to the OS to change? I might like to disable a drive or port while installing software, or to change the equipment attached to it..... ( hot swap for the personal PC isn't recommended, since the design engineers aren't allowed to spend time to actually design the things properly) Standardized connectors, properly labelled for the speaker connection, PWRON switch, Reset switch, HD LED connectors, so I dont need a magnifying glass to make the connections to the motherboard! Cases! hard to open, no room to get a hand in for connectors, not enough flow-through ventilation, poor mounting designs for the Hard drives...... Ideas and gripes, just like a programmer!
Engineers follow certain rules and procedures. Among them are the design constraints and requirements. ( What it is supposed to do and where it is supposed to work, limitations on loading, temperature, air pressure, wind loading, whatever is applicable ). Then there is the failure analysis ( NASA does this with excrutiating tediousness ) which is supposed to be the troubleshooting guide. This sort od designing would cost ( see the $ 60 Billion ststement) more, but how much would it save in terms of wasted time for rebooting, installing patches, re-installing, etc ? ALSO: the design environment is supposed to be defined. this is not possible with M$, since not only is the source not open, but the versioning problem is unmanageable ( see any set of comments on DLL-HELL ) IS it possible ? yes, if the programs dont rely on system DLL's. Yes, if the registry is bypassed and ini files are used. Yes, if the directories and 'microsoft-assisted installs' are bypassed.
YES!! Absolutely! They hold 'in trust' information about us, and the consequences are possibly extreme ( financially ). If a crime is being comitted , like a break-in, and a person sees it, and doesn't report it, then they become an accomplice. Same thing here.
Well, as a general rule, I dont install MS software until the third service pack comes out. This is due to the multitude of problems that come with MS new releases. As for security, why haven't the web and OS programmers set up a VM for browsers and email with no access to the underlying OS? A separate VM for each logon, and the user just kills his own VM ..........