Let them type in 20 pages of BASIC programs just to be able to shoot white pixels on a Black and White 127x48 display. (Ah I loved my TRS-80 model I)....
When I see the amount of horrendous Notes/Domino databases, Excel macros, SAP reports and weird Intranet web sites, I think it would be time to have some tools that allow people to write good programs (whatever that means...), not more to write bad programs.
Considered the fact that the only time in my life when I needed trigonometry was the day when I wanted to fix an IKEA lamp diagonally across the room.....oh wait.. last decade he said. No. nothing.
In fact, SAP has quite some experience with (well, kinda...) "open" development processes:
Their biggest product, good old R/3, is written in an interpreted language (ABAP/4) and delivered to the customer with the complete source code.
Now we all know users having "requirements" and we all know how many cheap and bad programmers are running around and we know the result if you combine those two: it's a mess. Imagine, the linux kernel would be written in python and it would also contain the code to place buttons on the left or right side of the desktop. And now try to maintain it.
Of course, he has an agenda. And they make their living by selling expensive products....
Well, the problem starts with being born or getting up in the morning. And a system running since 20 years normally doesn't start to stink by itself.
OTOH, what does "Risk management" in IT really mean, besides drawing nice PowerPoints and putting a chapter "Risk analysis" into change request forms, that are normally filled in with "No risk, no fun!" or "If I make a very big mistake, it will extinguish mankind"?
The first thing about simpler user interfaces is to change thinking from 'what features does this software have?' to 'what does the user want to do with it.' combined with 'who by the way will be the user of that software?'
Once you have that in mind, it gets much clearer. You don't need any designers or usability experts. Sometimes, common sense is all you need.
But what are we talking about?
We applied common sense and it worked for us, though not 24/7?
I still wonder, why so many projects use methodologies without knowing why and for what reason. This article is the other side of it: we still don't know why, so we use just common sense - call it "agile" - and we have at least a reason to write an article. (Or is this already a new methodology?)
Slashdot Mirror
The ST-225 20MB hard drives had this issue already back in 1988. Why should anything change during that time?
and Electric Pencil.....
Incredible. AFAIR, Berlin underground has this since 1995 - and not only in stations but throughout the whole network.
...as I've said before: Google+ is the OS/2 of social networking.
Let them type in 20 pages of BASIC programs just to be able to shoot white pixels on a Black and White 127x48 display. (Ah I loved my TRS-80 model I)....
SCNR....
...because WordStar key bindings became hardwired inside my spinal cord during childhood....
...ahh those CP/M days....
When I see the amount of horrendous Notes/Domino databases, Excel macros, SAP reports and weird Intranet web sites, I think it would be time to have some tools that allow people to write good programs (whatever that means...), not more to write bad programs.
Considered the fact that the only time in my life when I needed trigonometry was the day when I wanted to fix an IKEA lamp diagonally across the room.....oh wait.. last decade he said. No. nothing.
I used my cell phone in the Berlin subway already in 1996. What are they going to invent next in US? Waste water treatment?
In fact, SAP has quite some experience with (well, kinda...) "open" development processes:
Their biggest product, good old R/3, is written in an interpreted language (ABAP/4) and delivered to the customer with the complete source code.
Now we all know users having "requirements" and we all know how many cheap and bad programmers are running around and we know the result if you combine those two: it's a mess. Imagine, the linux kernel would be written in python and it would also contain the code to place buttons on the left or right side of the desktop. And now try to maintain it.
Of course, he has an agenda. And they make their living by selling expensive products....
Just read on page 24 of:
g ht.pdf
http://home.bridge.de/rukiessl/gravitation_and_li
OTOH, what does "Risk management" in IT really mean, besides drawing nice PowerPoints and putting a chapter "Risk analysis" into change request forms, that are normally filled in with "No risk, no fun!" or "If I make a very big mistake, it will extinguish mankind"?
The first thing about simpler user interfaces is to change thinking from 'what features does this software have?' to 'what does the user want to do with it.' combined with 'who by the way will be the user of that software?' Once you have that in mind, it gets much clearer. You don't need any designers or usability experts. Sometimes, common sense is all you need.
Sometimes "IT Management 101" comes in handy when it is rewritten nicely....but doesn't harm if repeated regularly....(or it may even help?)
But what are we talking about? We applied common sense and it worked for us, though not 24/7? I still wonder, why so many projects use methodologies without knowing why and for what reason. This article is the other side of it: we still don't know why, so we use just common sense - call it "agile" - and we have at least a reason to write an article. (Or is this already a new methodology?)