Our car stood outside (here in Belgium, Westhoek) this night, and was this morning covered with a thin layer of dust. The wind is currently from the north. When you wipe it with your finger, you can distinguish the glittering of glass. The ash is certainly coming down here.
But seeing that the North Korean invasion was done with massive help of China, it is more that North Korea learned the art of propaganda from the Chinese.
Didn't the Chinese call Tibet a dictatorial theocracy before they invaded^H^H^H^H^H^H^Hliberated it ?
Well, they have had 3000 years to perfect the art of lying^H^H^H^H^Hpropaganda^H^H^H^H^H^H^H^H^H^Hdiplomacy.
If a program works as intended and it requires no updates, users are happy with it, it's secure, and it is useful, then what difference does it make if it was made entirely using GOTOs
The mistake that you make here is that programs require no updates. Every program requires updates, because requirements change and new use cases are introduced. A program with GOTO's is much less readable from the beginning, and thus it becomes more difficult to maintain it.
Probably, but a good learning experience. I urge you to pick up a copy of Structure and Interpretation of Computer Programs.. They use exactly the same method to explain how Lisp (Scheme) implements list structures.
No, object oriented programming was invented in 1967 in Norway. The language was Simula 67. What Xerox came up with was the application of OO to graphical programming.
And there lies the problem : current IT departments are filled with hobbyists who can assemble computers and networks, and administrate certain software, but who do not know anything about how computers work (electronics), cannot program, and are clueless about business processes and work floor production (be it factory or white collar work), but who got more power over all these systems than the mainframe people used to.
The most striking example I have ever seen of this was in an aluminium mill. We produced rolled aluminium, and from we had all kinds of machines to process aluminium rolls and to create sub-assemblies.
One day an ambulance needed to come. On one of the processing machines where a roll of aluminium was processed through another roll, the night shift had invented a nifty little game : running on the rotating aluminium roll. The result was that one of them slipped and lost his leg in the roll where the aluminium sheet was processed.
I just find the way OO.o Writer and Draw work much better than the combo Word + Visio. I liked the old Visio, before MS took it over. I think that Draw works much the same way. The only thing that is missing is a way to export OO.o documents with embedded drawings to a Word document. In that case the drawings themselves are missing (the frames are there though).
When I worked between 1998 and 2000 for a bank, this was already so. This was a small bank (1000 employees), of which probably 150 where developers (both internally and externally). I think there where maybe 5 or six people responsible for IT, and these did the minicomputers (WANG VS back then) and the PC's. They also had operations outsourced to IBM and Honeywell mainframes.
I think the first thing that any IT department needs to do first, is install a publically available request tool and nicely explain to their users how to use it, and decide on a policy to process the requests.
My personal experience tells me that it should not be a cumbersome tool. When one thinks of something, he should just be able to enter his idea without much hassle.
That is why I in first instance think about installing trac for such things. It is easy to set up and use, and provides valuable experience in how a bug/request tracking system should work. The built in Wiki makes it possible to document procedures and other things that IT wants to disseminate.
Slashdot Mirror
Does that make Wisconsin the Holland of the USA ?
Might be missing the windmills and the tulips.
This winter we already had a mini ice age before the volcano erupted.
Our car stood outside (here in Belgium, Westhoek) this night, and was this morning covered with a thin layer of dust. The wind is currently from the north. When you wipe it with your finger, you can distinguish the glittering of glass. The ash is certainly coming down here.
They where probably all reactions from people who program for a living.
Yeah, moderated funny...
But seeing that the North Korean invasion was done with massive help of China, it is more that North Korea learned the art of propaganda from the Chinese.
Didn't the Chinese call Tibet a dictatorial theocracy before they invaded^H^H^H^H^H^H^Hliberated it ?
Well, they have had 3000 years to perfect the art of lying^H^H^H^H^Hpropaganda^H^H^H^H^H^H^H^H^H^Hdiplomacy.
I think this weapon is more intended for usage against naval targets.
I do think he really founded Computer Science, the other guys you mentioned founded Computer Engineering.
If a program works as intended and it requires no updates, users are happy with it, it's secure, and it is useful, then what difference does it make if it was made entirely using GOTOs
The mistake that you make here is that programs require no updates. Every program requires updates, because requirements change and new use cases are introduced. A program with GOTO's is much less readable from the beginning, and thus it becomes more difficult to maintain it.
Probably, but a good learning experience. I urge you to pick up a copy of Structure and Interpretation of Computer Programs.. They use exactly the same method to explain how Lisp (Scheme) implements list structures.
I read this document from him several times, and I always had the impression that it was really tongue in cheek.
A well deserved 'Whoooooshh' for all of you who took it that serious.
Dammit, no mod points.
Exactly the same conclusion I came to.
Java : not primitive enough to have GOTO, but not advanced enough to support functional programming.
You won't mind me ruminate through your belongings then ?
You know the logo of Drupal, a drop ? 'Druppel' is dutch for drop or droplet, add some artistic freedom and you get 'Drupal'.
No, object oriented programming was invented in 1967 in Norway. The language was Simula 67. What Xerox came up with was the application of OO to graphical programming.
And there lies the problem : current IT departments are filled with hobbyists who can assemble computers and networks, and administrate certain software, but who do not know anything about how computers work (electronics), cannot program, and are clueless about business processes and work floor production (be it factory or white collar work), but who got more power over all these systems than the mainframe people used to.
The most striking example I have ever seen of this was in an aluminium mill. We produced rolled aluminium, and from we had all kinds of machines to process aluminium rolls and to create sub-assemblies.
One day an ambulance needed to come. On one of the processing machines where a roll of aluminium was processed through another roll, the night shift had invented a nifty little game : running on the rotating aluminium roll. The result was that one of them slipped and lost his leg in the roll where the aluminium sheet was processed.
You know, you do not even have to die from them.
The December issue of Scientific American gave an overview of 5 debilitating diseases, not lethal, which affect 1 billion people worldwide.
I just find the way OO.o Writer and Draw work much better than the combo Word + Visio. I liked the old Visio, before MS took it over. I think that Draw works much the same way. The only thing that is missing is a way to export OO.o documents with embedded drawings to a Word document. In that case the drawings themselves are missing (the frames are there though).
Or these people that went studying physics at the university, but refuse to believe that rockets can leave the earth.
I am busy reading The evolution of Species, and to be fair, Darwin himself seemed to recognise that the boundaries between species are very vague.
When I worked between 1998 and 2000 for a bank, this was already so. This was a small bank (1000 employees), of which probably 150 where developers (both internally and externally). I think there where maybe 5 or six people responsible for IT, and these did the minicomputers (WANG VS back then) and the PC's. They also had operations outsourced to IBM and Honeywell mainframes.
I think the first thing that any IT department needs to do first, is install a publically available request tool and nicely explain to their users how to use it, and decide on a policy to process the requests.
My personal experience tells me that it should not be a cumbersome tool. When one thinks of something, he should just be able to enter his idea without much hassle.
That is why I in first instance think about installing trac for such things. It is easy to set up and use, and provides valuable experience in how a bug/request tracking system should work. The built in Wiki makes it possible to document procedures and other things that IT wants to disseminate.
Works equally well for "I dont care how well it works, if its NOT made by Microsoft I dont want it"
By virtue of inertia, fear and lack of knowledge of its current userbase ?