This is how he squeezes it into companies- "Your technical people are only saying it sucks because they're afraid it will make them obsolete!" A few additional choice quotes from the overview documentation: He uses this paranoia to drive wedge between the managers holding the purse strings and the technical people who have the knowledge to recognize VSE for the turd that it is. One of the strongest forces affecting the acceptance of new technology is the perception of one's job security.Is job security dependent upon complex code.?.Is job security dependent upon ensuring the other guy can't figure out what was done?.and fit only for those desiring artificial job security. I counted 17 uses of the phrase "job security" in the document. (And it works- the federal gov't is his biggest customer). He leverages this irrational fear to sell his tool. One of the key selling points that Bill Cave uses to try to sell VSE is the democratization of programming so that business people don't need to indenture themselves to programmers who use crazy, arcane tools for the sole purpose of job security. PERCENT BUSY = (TOTAL BUSY CALLS * 100)/TOTAL CALLS Riiiight.Īnother choice theme that comes up frequently: INCREMENT DAY COUNT BY 7 (or DAY COUNT = DAY COUNT + 7) They go on to claim that this somehow makes it more suitable for multi-proc environments because it more closely models the underlying hardware implementation.
Worst programming language list pdf#
Search that PDF for "Quagmire Of Scope" and you'll discover some true enlightenment. I'd include a quote but, like most fools, it takes these guys forever to say anything.
Worst programming language list software#
Why do things this way? We learn that from The Software Survivors that Variable Scope Rules Are Hard. When other functions use it, they're using the same data, not a local copy of data with the same layout. Imagine C's requirement that all variables/data must be declared at the beginning of the function, except now move that declaration into a separate file that other functions can use as well. The idea is that Data and Behavior must be completely segregated.
VSE is built around what they call "The Separation Principle".
Wading through all your answers made one thing clear. Some people have raised concerns that this question attracts trolls.
If a language supports only single character identifiers (see my own answer) this is bad in a non-debatable way. I'd like to collect this stories partly to avoid common pitfalls while designing a language (especially a DSL) and partly to avoid quirky languages in the future in general. The worst programming languages you ever worked with and I'd like to know exactly what annoyed you. While there is a lot of discussion about the best one, I'd like to hear your stories about We are programmers, and our primary tool is the programming language we use.
0 kommentar(er)
