Conversation

Notices

1. Embed this notice
   Ava Affine (ava@social.sunnypup.io)'s status on Wednesday, 23-Aug-2023 05:30:40 JST Ava Affine

   • Thomas 🔭🕹️

   @thomasfuchs
   You wax poetic about how much better things were in your day...

   My brother in Christ, you're the CTO.

   • Embed this notice
     Hedders (hedders@mas.to)'s status on Wednesday, 31-May-2023 23:45:03 JST Hedders

     • Thomas 🔭🕹️

     @thomasfuchs of course, when they actually do need to change something they find that, even if they have the source code, everyone who understands it is either retired, dead, or gone into consulting at 10k per day…

   • Embed this notice
     Purple_Sky (purple_sky@mastodon.social)'s status on Wednesday, 31-May-2023 23:53:29 JST Purple_Sky

     • Thomas 🔭🕹️

     @thomasfuchs

     Underline that last line. Some just like to follow those shiny hot stuff blindly.

   • Embed this notice
     Eric the Cerise (nattiegoogie@mstdn.io)'s status on Wednesday, 31-May-2023 23:55:41 JST Eric the Cerise

     • Thomas 🔭🕹️

     @thomasfuchs

     Exactly this logic is why it has taken me 2+ years to decide that, yes, it looks like #Rust is actually worth the time and effort to learn.

     At this point, I'm pretty sure it is one of those languages that'll still be around 50 years from now.

     PS: Still waiting patiently-ish for JavaScript to please just die already.

   • Embed this notice
     Kye Fox :veripanda1: (kye@tech.lgbt)'s status on Thursday, 01-Jun-2023 00:02:52 JST Kye Fox :veripanda1:

     • Thomas 🔭🕹️

     @thomasfuchs If they'd spent the last 10 years mastering COBOL instead of stumbling along with React, they'd be set for life.

   • Embed this notice
     StreetFur (streetfur@pawb.fun)'s status on Thursday, 01-Jun-2023 02:31:56 JST StreetFur

     • Thomas 🔭🕹️

     @thomasfuchs as someone who graduated in the late 00s and straight into mainframe work. It's interesting to explain, yeah it's super stable and has crazy transaction volumes it can sustain (the history of IMS is a bit bonkers). Buuuuuut it's a weird working market of older developers refusing to knowledge share and younger devs being locked out of the space by mockery and lack of teamwork and on the job training.

     It's going to get real weird when those older devs start expiring.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     StreetFur (streetfur@pawb.fun)'s status on Thursday, 01-Jun-2023 02:31:56 JST StreetFur

     in reply to

     • Thomas 🔭🕹️

     @thomasfuchs listening to a room at IDUG clap and cheer at a story of a new dev not getting any training, following a manual to the letter causing a bigger problem by bad documentation...then the story turned to a name and shame which made those jackals laugh showed me that the industry there has systemic problems about knowledge hording and it's going to sting hard very soon.

   • Embed this notice
     Brad Koehn (bkoehn@hachyderm.io)'s status on Thursday, 01-Jun-2023 03:53:24 JST Brad Koehn

     • Thomas 🔭🕹️

     @thomasfuchs While there is value in stability, that’s not why banks still run on the mainframe. It’s just cost/benefit analysis: it’s cheaper to live with all the technical debt than it is to figure it all out and rebuild it. COBOL didn’t win because of any intrinsic value, it’s just where investment stopped.

   • Embed this notice
     Schroedinger (steveclough@metalhead.club)'s status on Thursday, 01-Jun-2023 06:29:54 JST Schroedinger

     • Thomas 🔭🕹️

     @thomasfuchs Cobol is a brilliant language, and it is not easy to hack. It does what it says. I said in an interview recently that it was one of my favourite languages.

     Because it is simple. It deals with mapped memory.

     If it still works, it is fine.

   • Embed this notice
     Chip Butty (otfrom@functional.cafe)'s status on Thursday, 01-Jun-2023 06:43:37 JST Chip Butty

     • Thomas 🔭🕹️

     @thomasfuchs yeah, that strategy doesn't always work that well. https://www.bbc.co.uk/news/business-64036529.amp

     I've also worked on legacy systems that no one understands any more and there is no spec other than the live system. I think relying too much on something that people don't want to work in any more is a false economy. The TSB system before the migration was failing as well and they couldn't get anyone to fix it

   • Embed this notice
     federico (federico3@mastodon.social)'s status on Thursday, 01-Jun-2023 10:10:58 JST federico

     • Thomas 🔭🕹️

     @thomasfuchs
     brace for the obnoxious RIIR comments coming...

   • Embed this notice
     Matthew Knowlton (toastloop@hachyderm.io)'s status on Thursday, 01-Jun-2023 13:06:53 JST Matthew Knowlton

     • Thomas 🔭🕹️

     @thomasfuchs Running 60 year old code benefits the businesses because they don't have to pay developer time to update their software to conform with modern development standards. When the code breaks, the bank will pay out to ensure the code is repaired in place instead of gradually updating components to ensure the code base does not go stale and conforms with modern development standards that junior developers can work with. Just because it's old doesn't mean it glitters.

   • Embed this notice
     Kit Rhett Aultman (roadriverrail@signs.codes)'s status on Friday, 02-Jun-2023 00:25:08 JST Kit Rhett Aultman

     • Thomas 🔭🕹️

     @thomasfuchs Also, that behavior was pored over, specified, written to standard, tested by standard, and the misunderstandings were *themselves* re-specified. People say "waterfall" like it's a bad thing.

   • Embed this notice
     Scott Galloway (scottgal@hachyderm.io)'s status on Monday, 05-Jun-2023 07:59:35 JST Scott Galloway

     • Thomas 🔭🕹️

     @thomasfuchs Having worked on many of these systems when I was consultant it's often 'the team who wrote it left and we have no clue how it works'. So no team / manger wants to touch old systems & the risk of building replacements without understanding the original is way too high for the super-risk averse banks. ind you it employs a bunch of VB6, COBOL and LISP devs who otherwise would be skilled out of the market so not all bad ;)

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Tuesday, 22-Aug-2023 09:32:34 JST feld

     • Thomas 🔭🕹️
     Modern managers aren't helping either
   • Embed this notice
     Erin (moonshoterin@mstdn.social)'s status on Tuesday, 22-Aug-2023 21:45:11 JST Erin

     • Thomas 🔭🕹️

     @thomasfuchs truth.

     A neighbor of mine wrote & maintained a payroll system written in #fortran for 110,000+ employees until she retired after 50 years there.

     Her last programming task was writing, migrating and documenting the replacement system she wrote when she was hired in C++

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Don Whiteside (donw@mastodon.coffee)'s status on Tuesday, 22-Aug-2023 21:46:14 JST Don Whiteside

     • Don Melton
     • Thomas 🔭🕹️

     @thomasfuchs @donmelton I had a terse email exchange with the people behind a certain popular crm/blogging system a number of years ago. I wrote to complain that they didn't prominently link the release notes for each new release and it was a number of steps to find them. That made it a hassle to go look and see if the release covered issues I would have and thus made it worth installing and testing. They responded that "most of our users just want to run the most current thing.”🙄

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Crazy_Cat_Lady_Abroad (crazy_cat_lady_abroad@mastodon.online)'s status on Tuesday, 22-Aug-2023 21:48:43 JST Crazy_Cat_Lady_Abroad

     • Thomas 🔭🕹️

     @thomasfuchs When I worked in retail in my youth and every year we had the bright shiny new stuff, it taught me to greet every new feature with, "Yes, but what does it do?" It's amazing how often the answer is nothing.

     Graphics and sound aren't really important with bank records, AFAICT.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Ava Affine (ava@social.sunnypup.io)'s status on Wednesday, 23-Aug-2023 05:53:55 JST Ava Affine

     in reply to

     • Thomas 🔭🕹️

     @thomasfuchs if you are going to post boomer nonsense you can give us all a perfectly good reason why you aren't building new software in FORTRAN.