On top of ventilators, face masks and health care workers, you can now add COBOL programmers to the list of what several states urgently need as they battle the coronavirus pandemic.
Alicia Lee, writing for CNN:
On top of ventilators, face masks and health care workers, you can now add COBOL programmers to the list of what several states urgently need as they battle the coronavirus pandemic.
In New Jersey, Gov. Phil Murphy has put out a call for volunteers who know how to code the decades-old computer programming language called COBOL because many of the state's systems still run on older mainframes.
In Kansas, Gov. Laura Kelly said the state's Departments of Labor was in the process of modernizing from COBOL but then the virus interfered. “So they're operating on really old stuff," she said.
Sure, they were almost done taking 40 years to upgrade their technology. So close! What terrible luck for them.
It's been this way for a while. COBOL programmers are paid quite well because large dinosaur organizations (banks, schools, governments) still use systems that require it, but there aren't a lot of people left who already know how to do the work. At some point in the past, some vendor convinced these organizations that it was worth the long-term investment to buy these really expensive systems. It turns out that technology evolves pretty quickly (who knew?), so these systems were left in the dust. Now these organizations are trying to build modern systems on top of this creaky technology, and it's just terrible. This is why government websites are so bad. My state's unemployment website says it's unavailable after 10 PM every night. Can you imagine Facebook or Twitter being unavailable, ever? That crap rarely flies when private money is at stake. Rather than admit their mistake and swallow the cost of these bad products, the organizations try to make it work as long as possible, never mind the downsides.
"Literally, we have systems that are 40-plus-years-old," New Jersey Gov. Murphy said over the weekend. "There'll be lots of postmortems and one of them on our list will be how did we get here where we literally needed COBOL programmers?"
There won't be any postmortems. The situation was already well understood, as I laid it out above. It's purely a political problem. Of course the engineers working with these products have been asking for replacements for decades. Governments could have paid the money to do it, but that would have required raising taxes or finding the money from somewhere, so they didn't do it. The fault lies squarely at the feet of the legislature: every representative that came and went since those systems exhibited problems. It's as simple as that.
The reality is that it's not that hard to learn COBOL and get up to speed on working with it. That's true for any programming language. I learn new programming stuff almost every week, and I've learned many programming languages in my professional work. Just because a programming language is old, that doesn't mean that it's bad. Lisp is one of the oldest programming languages around (1958, one year older than COBOL) and it's still one of the best. The reality is probably that these governments aren't willing to pay fair market wages and give engineers time to learn and train properly. They want someone who can walk in the door and be productive today, but for a fraction of what they're worth.
You gotta love those 1950s capitalized names. COBOL!
Rob Pike explains the origins of Go's concurrency. It's the first mention of the language Alef by the Go Team I've come across, which I'm glad to see. Really interesting contrast between the Go and Erlang concurrency models, and how Go's might be more expressive.
On Monday, April 30, 2018, the California Supreme Court issued a landmark decision in the matter of Dynamex Operations West, Inc. v. Superior Court of Los Angeles.
Timothy Kim:
Under the ABC test, a worker will be deemed to have been “suffered or permitted to work,” and thus, an employee for wage order purposes, unless the putative employer proves:
(A) that the worker is free from the control and direction of the hiring entity in connection with the performance of the work, both under the contract for the performance of the work and in fact;
(B) that the worker performs work that is outside the usual course of the hiring entity’s business; and
(C) that the worker is customarily engaged in an independently established trade, occupation, or business of the same nature as the work performed.
Note that each of these requirements need to be met in order for the presumption that a worker is an employee to be rebutted, and for a court to recognize that a worker has been properly classified as an independent contractor.
Essential knowledge for any programmer in California. I think a lot of employers are going to run afoul of B.
The This Is What We Do music video by MC Hammer. I watched the TMNT movie so many times as a 90's kid. This song is ingrained in my memory. The movie callbacks in the comments are hilarious.
Jonathan Blow on whether gameplay innovation is truly necessary in new games:
Here's a thought for you: what if, like fossil fuels, innovation is a finite resource? A steady flow indefinitely into the future is unsustainable. When it drops to a trickle -- when we're down to diminishing returns -- what are we going to do? Just say, "well there's no more innovation to put in games, so they all suck now. Sorry, everyone!" I hope not.
So, why do we feel like games need innovation to be good?
Data-Oriented Design (Or Why You Might Be Shooting Yourself in The Foot With OOP) – Games from Within
Noel Llopis:
Data-oriented design is a different way to approach program design that addresses all these problems. Procedural programming focuses on procedure calls as its main element, and OOP deals primarily with objects. Notice that the main focus of both approaches is code: plain procedures (or functions) in one case, and grouped code associated with some internal state in the other. Data-oriented design shifts the perspective of programming from objects to the data itself: The type of the data, how it is laid out in memory, and how it will be read and processed in the game.
Chris Moody on what part of company culture is actually important:
I’ve been fascinated by different company cultures for as long as I can remember (maintaining culture is also a hot topic at our CEO Lunches each month) and I’m frequently asking entrepreneurs to describe the culture of their companies. Over time I’ve come to realize that when you break down culture descriptions you’ll often find a mix of two components: values and vibe. Although each component can have a significant impact on the overall feel of a company, the way you establish and manage the two should be different.
Hi, I’m Vladislav Zavialov. For the last couple of months, my job at Serokell has been to lead our efforts to improve our primary tool – the Glasgow Haskell Compiler (GHC). I’m focusing on making th…
I'm really interested in dependent types, and hope this comes to fruition!
titsay
izzy806
andulkaphoto
tangentwithtanner
vaporwave
kianamaiart
kaledo-art
turnnoffyourmind
discoholicmusic