CS education is less than worthless

CS is full of retards who can't understand that arrays don't have to start at 0. This means these graduates have never seen Fortran, Cobol, Algol, Basic, PL/I, Pascal, Ada, Smalltalk, or Haskell.
https://www.reddit.com/r/ProgrammerHumor/comments/6jea7z/array_indexing_round_2/

Some of these grads are also confused by := as the assignment operator.

The only languages that matter are C based

Arbitrary indexing as in Ada is completely free at runtime and a great method to prevent off-by-one errors, what the fuck are these toilet scrubbers on about?

why are those people so butthurt about := assignment? it's better than = which is intuitively read as 'equals'

>>4
if it's better than = then why isn't it used anymore?

>>5
Because typing = doesn't require Shift, but : does.

>>5
because of C's popularity. and while I genuinely like C, it's far from perfect

What if Lisp used square brackets instead of parens?

>>8
clojure

>>5
Because students have been literally dumbed down by these universities. This is the next generation of software developers. If that doesn't scare you, the F-35 software is written in C and C++ because they thought the programmers were too dumb to learn Ada. They're too dumb to learn Ada, but they're supposed to write working C and C++.

>>10
next generation of code monkeys*

>>10

They're too dumb to learn Ada

No one programs in Ada

Ada(specifically GNAT) needs better compiler diagnotics.
It often just spits "Compilation error" or other cryptic one-liners.
I'm not going to use Ada just because its safe, the language has to be user-friendly. There is little of books, tutorials, code examples, communities/forums are stacked with old people arguing about standards.

>>13

communities/forums are stacked with old people arguing about standards.

so it's just like /prog/ wherever undefined behavior or GCC extensions in C are mentioned

>>13

There is little of books, tutorials, code examples, communities/forums are stacked with old people arguing about standards.

Barnes' Programming in Ada 2012 exists, what other books or tutorials do you need? You don't read ten thousand introductions to FIOC when you already have a good one. Yes, there is no Stack Overflow for Ada you can quickly copypaste from, thank G-d. The programming world needs less rot by cargocultists.

Example of proper documentation for complex software:

Tutorials: A step by step guide with heavily annotated code. These are meant to get the user acquainted with the library as quickly as possible. The objective is to build the confidence of the user in using the library through abundant examples and detailed instructions. Examples speak volumes and we have volumes of examples!
Abstracts: A high level summary of key topics. The objective is to give the user a high level view of the library, the key concepts, background and theories.
Reference: Detailed formal technical reference. We start with a quick reference -- an easy to use table that maps into the reference proper. The reference proper starts with C++ concepts followed by models of the concepts.

>>16

And then there is the The C++ Programming Language book, intended to confuse the user and make him lost in the labyrinth of broken concepts.

You don't need documentation if you know how to RTFS.

>>18
you don't need standards when you know how to RTFSC
you don't need source code when you know how to RTFMC

"Solving problems yourself builds character:
you don't need stack overflow, reddit and google." /thread

who needs /sorg/ when you've got /prog/

Professors are afraid to fail people.

>>22
This. I'm not sure if it's fully their fault though: Many universities receive funding based on how many students succeed in the program and a high number of failing students is usually blamed on the professor and not (as it should be) on the fact that too many students don't have any business being enrolled. Gotta keep the student loan scam going.

>>22-23
Except it's not.
CS is there now to churn out future code monkeys to meet the demand. Future code monkeys don't need Fortran, Cobol, Algol, Basic, or any of the other ones.

>>24
Fortran and COBOL are still relevant though.

>>25
Only for legacy systems.

>>26
Which are most of them.

>>26
Fortran is also used for HPC and scientific computing

>>28
not relevant

>>29
Okay, run along and play your video games now.

>>30
But I'm right, tho. Whether Fortran is or is not used--is irrelevant.
Future code monkeys have absolutely no need to learn it, and only people involved with legacy systems or "HPC" care.

>>31
Computer science isn't supposed to create code monkeys. Universities are supposed to be better than a Java/JavaScript coding ``bootcamp''.