[ShadowAce]

Thanks to The Spirit Of Allegiance for finding this article!

[ShadowAce]

Tech Ping

[Jemian]

I have been wrestling with drupal, css, php, and twig all day today. I don’t consider myself a programmer. Someone else invented these languages.

[Cvengr]

A programmer’s response to his error:

Ooops, ..... why it’s another ‘feature’.

[mad_as_he$$]

There are 10 kinds of people........

[duckman]

Blast from the past from an old programmer. Back in the day people were amazed that I could read a punched card that did not have any verbiage above.

[SES1066]

Just remember, all of this is the basis for all of the “Internet of Things” (IoT) aka automation aka Alexa and the rest. If a human being does something stupid like running a stop sign, it is a single act and society has procedures to handle the consequences. If a self-driving automation system does the same action, the ramifications are a very “Brave New World” indeed! Even if you place ultimate responsibility with the driver using the flying pilot rules as an exemplar, there are going to be a myriad of exceptions to be programmed.

Thank God I am a retired & recovering software engineer!

[Chode]

"And so we see again and again as developers create new frameworks to patch the problems of the old frameworks, introducing new problems along the way. If a framework adds server-side rendering, it bogs down the server. But if everything is left to the clients, they start slowing down. Each new feature is a tradeoff between time, code, and bandwidth."

[AnotherUnixGeek]

Here’s another lie: managed code somehow magically removes the need to worry about or even check for memory leaks. Managed code just means the memory leaks become more difficult to debug.

[ImJustAnotherOkie]

No programmer wrote these. So what the hell does this author know, Not Much.

[I want the USA back]

How did you know my pronoun is “His Majesty”?

[Fresh Wind]

The only programming I ever actually enjoyed was assembly language.

[BubbaBasher]

Computers do not make mistakes. Programmers and data entry folks make the mistakes.

[McGruff]

An If is an If, a For is a For.

[zeugma]

These are only two examples of how file systems don’t honor the compact between user (the person supplying the electricity) and the machine (desperate needer of electricity).

Desperate needer of elictricity. Yup. Mine has even trained me to supply it clean power through an UPS. I just wish the UPS were more reliable. I had one recently that I had to replace, because even the slightest bobble of power would cause it to drop like a stone. Even when said bobble wasn't enough to even reset the clock on my microwave.

[CodeToad]

The biggest lie, I think, is time. They will write something quick in an hour then spend three weeks making it work, but when asked how long it took they claim an hour.

[stylin19a]

all of our clever code boils down to one bit of doped-up silicon choosing to go left or right down the fork in the code and there is no middle path.

until you start chasin an altered goto.

[_Jim]

TI DX10 on a TI990/12 were the best.

DNOS on a DX10 offered almost bulletproof, although slower, execution. This was MULTI-USER not just multitask stuff!

[asinclair]

Interesting that this came from InfoWorld. Back in the day, the magazine never talked about programming. That was left to Byte, Dr Dobbs, and Popular Electronics, among others. Computer "languages" are interesting. And in my career, I have had to move from language to language. So:

• COBOL, so I could help my father with his homework
• BASIC, when a PDP-8 showed up at junior high
• FORTRAN II, because that's what my high school taught.
• PL/I, the "next new thing" (1969)
• 360 Assembler, so I could document a bug I found in the PL/I compiler
• FORTRAN IV
• C, the "next new thing" (1972)
• MIX, because The Art of Computer Programming
• ALGOL, class book assignment -- never used it
• PL/I again, so I could teach a class in the language as part of CS 306, Operating systems.
• GLIPNER, because ILLIAC IV
• LINC microassembler, because there was one in the basement at school
• PASCAL, so I could run my own compiler and run time on a minicomputer
• PL/M, because Intel
• BASIC again, because IBM PC
• PASCAL again, because Perq graphic workstation
• PDP-11 assembler, because there was one down the hall
• 808x assembler, because I could, and various C packages didn't cut it
• PERL, because Unix system administration
• SH and BASH, because Unix system administration
• LEX and YACC, because inventing my own language made particular problems MUCH easier to solve and maintain
• PHP, because commercial Web site
• TCL and EXPECT, because inter-computer automation
• Python, because $DAYJOB loved buzzwords.

And I don't expect that to be the end of the list. Most of these things I have dropped by the wayside.

I have JAVA books, but never took the time to learn the language because I didn't have a need for it. Read the ADA Language Standard, but never had a machine with a compiler to play with.

I keep hearing about other "new" languages that have enhancements for security; someday I'll have a reason to try them. I don't know their names yet.

Quite the parade, isn't it?

[bruin66]

Universal truths:

Constants aren’t.
Variables won’t.

[Larry Lucido]

You can prevent SQL injection by sanitizing your database inputs.