Java is extremely widespread in corporate companies - hence the suit and tie. Perl is fair to liken to spelunking deep into a dark cave with only your wits to save you.
PHP seems to be a reference to the fact that it’s extremely common on servers… but it also might be a lazy phpbad joke - it’s pretty weak either way (if you wanted to play into the server characteristic give it a dozen arms serving the entire restaurant in the background).
As a Perl dev, I dunno if that’s how I’d characterize the language, but I’ll take it over yet another “Perl is unreadable line noise lol and what’s the deal with airline food” reference.
Yeah, to be honest you can write good code in any language and it’ll usually look pretty similar… all the perl stereotypes come from having to maintain shell scripts from someone kludging their way through learning to code… it’s the same reason why phpbad, amateurs could get into webdev with php so there’s an impression that all php is the php written by amateurs.
Also, bear in mind that over time these languages have converged through feature additions “LISP has functional programming - why can’t PHP have first class functions… oh traits look neat, let’s add that… you know those statically typed languages sure seem nice…”
Do other languages separate definition from implementation? 🤔 Is there another way to distribute libraries with a binary component and a public component?
Anyway, you don’t need to separate them in your source code to have a legible component on your distributable. C is the only language that insists you must have part of the source code before you can use the very public perfectly clear interface that is written all over shared libraries.
Also, you can distribute proprietary libraries by source perfectly well. And it’s the standard except on very few cases where a corporation can coerce most of the world on accepting any shit.
Everyone who works on making software is a developer, even people who don’t program at all. people who make art for software work in software development. A “coder” only writes code. It’s more of a task than a job. A software engineer does technical design and probably also codes.
Actually my title is “Senior Network Architect”. I hate it. I feel like it detracts from real architects, who have licensure and actual training from an actual school.
I hate it as an architect, and I hated it as an “engineer”, for the same reason.
Yes, there’s a lot of complexity and planning, especially at larger scales. But it’s mostly self-taught, some webinars, and a lot of on-the-job (read: trial-by-fire) training.
When it comes to telling computers what to do, I have no idea what to call it. I write Python scripts and Ansible modules, I guess. That doesn’t make me any of those titles though. Some times I poor-mans deamonize my scripts (while true loop) and pack them in a container.
Using some of the same tools doesn’t make me any more of the same title.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.