Yk, you can make fun of old programming languages but the average job offer with one of them is.
Needs to know fortran/cobol
Pay: 8000€/month + benefits and unlimited sick days
Compared to the average web dev job offer:
Needs to know react, redux, angular, PHP (for managing legacy codebases) with 5+ years of experience, needs to be affluent in at least 3 languages and must have a master’s degree in computer science.
The one thing that consistently gets caught in code reviews in my shop is a failure to update a copyright date. I have been tempted to submit clearly crap code just to see if anyone actually is paying attention.
We add the current year to the copyright dates, the current updates are protected from the time of authorship. So if the copyright says, 2012, 2014, 2022; I would add a 2024. The commit records can be used to determine what was changed each instance, but the update provides notice of when changes were made.
Discerning what is protectable creative expression versus functional and therfore unprotected is an issue for the courts.
I’m not any type of lawyer, especially not a copyright lawyer, though I’ve been informed that the point of having the copyright date is to mark when the work (book, website, photo, etc) was produced and when last edited. Both aspects are important, since the original date is when the copyright clock starts counting, and having it further in the past is useful to prove infringement that occurs later.
Likewise, each update to the work imbues a new copyright on just the updated parts, which starts its own clock, and is again useful to prosecute infringement.
As a result, updating the copyright date is not an exercise of writing today’s year. But rather, it’s adding years to a list, compressing as needed, but never removing any years. For example, if a work was created in 2012 and updated in 2013, 2015, 2016, 2017, and 2022, the copyright date could look like:
To be clear, I’m not terribly concerned with whether large, institutional copyright holders are able to effectively litigate their IP holdings. Rather, this is advice for small producers of works, like freelancers or folks hosting their own blog. In the age of AI, copyright abuse against small players is now rampant, and a copyright date that is always the current year is ammunition for an AI company’s lawyer to argue that they didn’t plagiarize your work, because your work has a date that came after when they trained their models.
Not that the copyright date is wholly dispositive, but it makes clear from the get-go when a work came unto copyright protection.
There’s some good info out there from the good people that know how things should work that created the reuse tool - reuse.software - and basically the conclusion is that nobody should be updating the years on the copyright line just because it’s a new year. The only useful info and what should be done is put the year when the file is created and that’s it.
Somebody should make an api shim that proxies openapi compatible requests to this. And since Microsoft is forcing copilot on windows 10 they’re on the shit list too. Load balance all the AI workloads onto both of them through API adapters.
programmerhumor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.