You forgot the most important one:
CSCI 7999 - logging with cat.
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
You forgot the most important one:
CSCI 7999 - logging with cat.
Missing "how to politely but firmly tell management 'that's a dumb fucking idea'"
Where's
Using Solutions that Already Exist
No, seriously, you don't have to build everything from scratch by yourself. Other people write code too.
Yeah, other idiots.
It's a double-edged sword and understanding when to re-use and when to re-implement is an art that goes wrong more often than right.
We desperately need to teach people when a 3rd party dependency is necessary and not just optional to save writing a single function (cough left pad cough).
Also when the dependency is really good but other considerations override it being a viable option like security or code ownership.
How we all didn't collectively learn our lesson from left pad baffles me.
Yeah, the problem is the balance. In-house code sucks. Nobody outside the team tests your code. Self-developed code is not battle hardened. You can only use the skills available in your team and especially for specialist topics like databases, security or cryptography having in-house expertise is rare and expensive.
Using external dependencies sucks. You are dependant on externally developed code and on someone elses skills, quality controls and trustworthyness, and you usually don't have time or ability to really verify any of that. Even a good dependency can get stuck in some kind of development hell (like e.g. OkHTTPClient) and not deliver updates for years, and supply-chain attacks are constant threat.
In the end both options suck for different reasons and it really depends on the scenario where one or the other is useful. Leftpad is an extreme example, but most options are less obvious.
Well said. I find I have a hard time with trying to get devs who cut their teeth on Node to take a moment and think before just reaching for a dependency. A dependency might be the right move but taking a moment to consider is a bare minimum and most people don't do that.
I'm trying to keep my panic over how that behavior translates to AI code in check but it's a struggle given human behavior time and time again.
Got caught in that trap at my first coding job. Made a sort formula and a sr dev asked my I didn’t just use the array.sort.
My answer: I didn’t know it was there.
Ah, the ever-elusive, mysterious stage in my process - the one I can't ever seem to move much before the "planning" and at least "beginning to implement" stages, and sometimes stubbornly comes even later than that.
I always find it funny to see calls to “unlearn oop”. It’s a tool, useful in some contexts and not useful in others. At some point industry treated it like a silver bullet, and now people are reacting to it by checks notes treating the hot new paradigm as a silver bullet.
learn oop, learn fp, learn logic programming, learn whatever you want. Also, learn when not to use them.
It’s a tool, useful in some contexts and not useful in others.
In my opinion this is a thought terminating cliche in programming and the IT industry in general. It can be, and is, said in response to any sentiment about any thing.
Now, saying what sort of context you think something should or should not be used in, and what qualities of that thing make it desirable/undesirable in that context, could lead to fruitful discussion. But just "use the right tool for the right job" doesn't contribute anything.
I've been working as first a Python and then a Java dev for the last 15 years and I can count the amount of times when I've seen actual OOP on one hand.
I mean, we write "class" at the beginning of our modules and at the beginning of our structs, and we write "interface" at the beginning of our header files, but none of that is actually OOP.
If you use Spring Boot, you are essentially doing C (not even C++) in Java.
You have data-only classes without methods (at best there's a conversion method or something shallow like that) that work identical to C structs. You have service interfaces, which serve the same purpose as C header files. And then you have data-less collections of functions (service/controller classes), which work like .c files.
Nowhere in this whole process are you actually using OOP techniques.
There's a lot of humour in there, but this:
CSCI 3300: Classical Software Studies
Discuss and dissect historically significant products, including VisiCalc, AppleWorks, Robot Odyssey, Zork, and MacPaint. Emphases are on user interface and creativity fostered by hardware limitations.
I'd take that course in a heart beat. I've read some of Atkinson's ideas and thoughts, and the man was deeply sane.
It must be decades now that my LinkedIn background banner is a screen shot of Zork source code.
deeply sane
I hope somebody describes me like this one day.
I feel like I'm the only CS major to have taken a CS focused ethics class
Would be nice if all engineers had to take ethics
I'm a CS major who had to take ethics, but the REQUIRED textbook was written by the professor teaching the class. Managed to get through the semester with an A without buying it and called him out in the class survey.
I was required to take an ethics class, but it was a complete joke. Guy just wasted a bunch of time on very surface-level, Philosophy 101 stuff like talking about who Aristotle was. I'm not sure we even had homework actually. Real ethics were nowhere to be found.
History of software design would be an AMAZING course.
It'd be a good idea. Hopefully it'd see an end to those idiots claiming single exit means there can only be one return statement.
It'd be fun to talk shop with the fast code in slow languages folks. I do that for a living. I remember three ways, but I'm sure there's more:
Arguably "we can just put it in docker, and create an auto scaling microservice with a load balancer, behind a CDN for avg request latency" fits this group too. The hoops I have to jump through to get a good user experience on top of our shitty PHP backend are unreal
It's almost always slow is ways that the language choice doesn't matter even a little
"Key Search Words 101". Make it quicker and easier to find other programmers solutions on the web.
Hello programmers, electrical engineer here.
I work in MEP design, basically power design for commercial buildings and multi-tenant residential.
I am constantly saying I wish every fucking engineer, architect, interior designer, building manager, etc. had been forced to take a class on project management and accountability.
Curious if some of you run into a similar desire...

I've never seen a course on functional programming. That would be interesting.
It's what the Wizard Book (Structure and Interpretation of Computer Programs) was written for.
My uni had one. Sadly I couldn't fit it into my schedule because of overlaps and other requirements.
i took two courses on functional programming through coursera. it was based on scala.
I would actually love to take 3300! That sounds fun.
As for 4020, writing performant code in Python typically means calling into libraries that are written in C.
-1 for unlerning OOP
But
+1 for Zork
+1 for unlearning OOP
It's a cult
Like everything that's impressive at first sight, but misunderstood because you never go past that first impression.
Why? I find it quite useful.
That's because you haven't unlearned it yet