IHeartBadCode
Actually 127 years ago. Svante Arrhenius published a paper indicating that creating so much CO2 could potentially alter the Earth’s surface temperature to such a degree that it may affect life.
That was in 1896 about 130 years after the start of the industrial revolution. So by that point we had a pretty significant amount of CO2 in the air already.
Human beings have been dumping CO2 into the atmosphere hard for the last quarter of a millennia. I usually bring this up because people need to understand, even if we stop today 100%, we’ve got at least five centuries of a problem on our hands. Because it’s going to take at least twice as long to clean things up as it did making the mess.
And that should help people understand how difficult a problem we have because we need a solution that can work for us for 500 years at least. I mean we’re doing nothing right now which is just making the problem worse, but solutions aren’t ever going to be a one and done thing. Just swapping over to solar or just driving EVs aren’t going to cut it. It’s a good start but we must reinvent all of human society on this planet for the next half millennia to actually solve the problem. That is the actual task that lies before humanity. There has never been a more complex challenge put before mankind ever in the history of all existence for Homo Sapiens.
Just FYI for semantics. Generics is a term usually for small molecular weight compounds, usually under 900 daltons. Biosimilars is the term for higher molecular weight.
Doing generics is a lot simpler than biosimilars, in both you must wait for the patient to run out. But biosimilars are less likely to be made using an alternative process than the original trade secret process. This is due in part to the higher molecular weight which means a more complex compound.
Correction. Excel DOES NOT HAVE PYTHON. Your python is sent to Microsoft's cloud instance of Python and the result there is sent back to your Excel sheet. No actual python is being executed on your machine.
India? More like WINdia!
If it's #2 he's absolutely going nowhere near a window on the fifth floor of any building.
IBM hawks new conversion tools all the time. None of them are amazing sliver bullets, all of them require humans to comb over the resulting output. And every single one I’ve ever used chokes on any weird case.
From the RPG fixed form to free form, DDS to DDL conversion, and so on all of them are usually more trouble to use than to not use.
IBM does this kind of stuff all the time. And for some folks it’ll work some of the times. But at this point, I just skip any WS tool they put out and have a snippet on RDi and RDz that does all the required plugging away to call web services from the COBOL module.
This sounds no different than the static analysis tools we’ve had for COBOL for some time now.
The problem isn’t a conversion of what may or may not be complex code, it’s taking the time to prove out a new solution.
I can take any old service program on one of our IBM i machines and convert it out to Java no problem. The issue arises if some other subsystem that relies on that gets stalled out because the activation group is transient and spin up of the JVM is the stalling part.
Now suddenly, I need named activation and that means I need to take lifetimes into account. Static values are now suddenly living between requests when procedures don’t initial them. And all of that is a great way to start leaking data all over the place. And when you suddenly start putting other people’s phone numbers on 15 year contracts that have serious legal ramifications, legal doesn’t tend to like that.
It isn’t just enough to convert COBOL 1:1 to Java. You have to have an understanding of what the program is trying to get done. And just looking at the code isn’t going to make that obvious. Another example, this module locks a data area down because we need this other module to hit an error condition. The restart condition for the module reloads it into a different mode that’s appropriate for the process which sends a message to the guest module to unlock the data area.
Yes, I shit you not. There is a program out there doing critical work where the expected execution path is to on purpose cause an error so that some part of code in the recovery gets ran. How many of you think an AI is going to pick up that context?
The tools back then were limited and so programmers did all kinds of hacky things to get particular things done. We’ve got tools now to fix that, just that so much has already been layered on top of the way things work right now. Pair with the whole, we cannot buy a second machine to build a new system and any new program must work 99.999% right out of the gate.
COBOL is just a language, it’s not the biggest problem. The biggest problem is the expectation. These systems run absolutely critical functions that just simply cannot fail. Trying to foray into Java or whatever language means we have to build a system that doesn’t have 45 years worth of testing that runs perfectly. It’s just not a realistic expectation.
Is basically their WEBSERVICE function but automatically because it's python and hardwired to their service.
Yeah this is hardly the announcement Microsoft thinks it is.
Nothing can enter your bloodstream if you just let it bleed.
Exactly. Just like how fish cannot swim upstream no matter how slow or fast the flow is.
That's not how being a scapegoat works. I know this may come as a shock to many, but the person who gets all the blame DOES NOT usually volunteer for that position.
Literally Uber and Lyft are both in the find out phase. And what they’ve found is that those PDF417 barcodes aren’t as foolproof as they thought and AI selfies are easy to make.