Earlier quoted context omitted.
That was worth reading. capitalism's fixation on quarterly reports is ruining successful companies like DST.
That's not capitalism, it's our culture around capitalism. There is nothing inherent to capitalism that stresses short term growth vs. long term growth. For example much of the push for short term growth comes from the stock market, but the stock market (or public ownership at all) is in no way required for capitalism to work (and IMO it would probably be better without it).
Millennials and Mainframes: How to Bridge the Gap
121–130 of 163 posts
Re: Millennials and Mainframes: How to Bridge the Gap
#122>And it’s not all COBOL anymore. Today mainframe programmers use Python, Linux, node.js, Java, blockchain.
node.js on a mainframe? That doesn’t strike me as being something that can uninterrupted for years.
Re: Millennials and Mainframes: How to Bridge the Gap
#123Earlier quoted context omitted.
As a non mainframe programmer I found your anecdote about windows reliability contrary to the experience I have had over the past few decades so I am not sure how accurate the rest of your post is.
Here's my favorite: https://support.microsoft.com/en-us/help/2553549/all-the-tcp... article about it: https://blog.ctm-it.com/it-support/blogs/matt-cannon/2013/49... edit: If you want to be especially cynical, you can note that this wasn't discovered for a while because everyone running Windows reboots it regularly because of its notorious instability issues (the bug was found in 2013 and dates back to at least Vista…
Windows used to suck, but it's somewhat unfair to judge the platform of 2018 because Vista of 2006 was bad for you.
Re: Millennials and Mainframes: How to Bridge the Gap
#124Earlier quoted context omitted.
As a non mainframe programmer I found your anecdote about windows reliability contrary to the experience I have had over the past few decades so I am not sure how accurate the rest of your post is.
https://www.cnet.com/news/windows-may-crash-after-49-7-days/ Windows has improved since then, but it's still a very brave person that would have a single business-critical Windows machine without a few scheduled maintenance and reboot periods every year.
Re: Millennials and Mainframes: How to Bridge the Gap
#125Many people will say that there is a shortage of skills when it comes to mainframe environments, that might be true, however the need for such skills is diminishing significantly.
Re: Millennials and Mainframes: How to Bridge the Gap
#126Earlier quoted context omitted.
Here's my favorite: https://support.microsoft.com/en-us/help/2553549/all-the-tcp... article about it: https://blog.ctm-it.com/it-support/blogs/matt-cannon/2013/49... edit: If you want to be especially cynical, you can note that this wasn't discovered for a while because everyone running Windows reboots it regularly because of its notorious instability issues (the bug was found in 2013 and dates back to at least Vista…
That bug is over five years old. Are you implying there haven't been similar, or worse, bugs in other operating systems since? Windows used to suck, but it's somewhat unfair to judge the platform of 2018 because Vista of 2006 was bad for you.
Hopefully a mainframe expert can chime in as to whether the major mainframe OSes have included similar or worse bugs.
Re: Millennials and Mainframes: How to Bridge the Gap
#127Earlier quoted context omitted.
https://www.cnet.com/news/windows-may-crash-after-49-7-days/ Windows has improved since then, but it's still a very brave person that would have a single business-critical Windows machine without a few scheduled maintenance and reboot periods every year.
That bug is from 2002. Do you really think it's a solid reason to not host business-critical things on Windows in 2018?
It is, of course, only a proxy for the real reason, which is the engineering culture that led to the bug and/or reliability. If there's better evidence that Microsoft has drastically changed its engineering culture in favor of reliability and/or IBM has done the converse [1], it could easily trump this proxy evidence.
[1] for example, if they've included the OS developers in the layoffs they've been in the news for
Re: Millennials and Mainframes: How to Bridge the Gap
#128At any rate, it isn't clear why millennials should be expected to work on mainframes, i.e., maybe there's a good reason why they don't. Are the jobs good? Do they pay well? Are there recruiting efforts underway to get candidates in the door and explain to them why they should be excited about it, to help bridge this gap?
Engineering talent is rather supply-constrained, or so we hear. You can't just sit around writing op-eds about how the darn millennials should work on your stuff, just because your stuff happens to exist and needs engineers. What are you doing about it? The answer this article points to is conscription, which of course is silly in the context of industry.
Re: Millennials and Mainframes: How to Bridge the Gap
#129How do I start? Can I get access to one? Can I build up something I can learn on? What is the best path for doing this? How would I usefully gain enough experience to get into this?
I have linux, python, c, but unsurprisingly can’t afford 30 million (or whatever) on a mainframe.
I know about Hercules, but I’d only be able to run Linux. Is that right? Is that useful?
My feeling is that I’d need experience to get a job, but I can’t get experience without a job. Seems like the whole shortage is a lie. If there was a shortage I’d be able to find various organisations falling over themselves to help me into mainframes.
Re: Millennials and Mainframes: How to Bridge the Gap
#130Fine. I want to learn how to maintain/write software for a mainframe. How do I start? Can I get access to one? Can I build up something I can learn on? What is the best path for doing this? How would I usefully gain enough experience to get into this? I have linux, python, c, but unsurprisingly can’t afford 30 million (or whatever) on a mainframe. I know about Hercules, but I’d only be able to run Linux. Is that righ…