3 ms·

Have long stood by this belief and still do but modern IT calls it legacy and antiquated. Oh how we've lost The Plot.

hi-v-rocknroll 2y ago
The modern attitude is discard everything "old", not immediately understood, and abandon standardization and simplicity.
- borski 2y ago
  Eh, I don’t think that’s true. I think you’ve just had bad experiences, and that that can definitely be true in pockets. For example, I am exceptionally happy that we have standardized on OpenAPI documentation and/or the self-documenting nature of GraphQL (where used) rather than WSDLs and the other ancient nonsense. I’m also glad we’ve mostly progressed from SAML to OAuth2/OIDC/JWT. Sure, SAML still exists but it’s definitely on its way out, once the enterprises of yesteryear eventually switch. I don’t know if you’ve ever built a SAML application and/or IdP, but it’s awful. Sometimes “old” is just worse.
  - hi-v-rocknroll 2y ago
    You're cherry-picking technologies. I'm talking about people. Yes, I have. Krb5, LDAP, OAuth2, CAS, and SAML 1 & 2. XML sucks but sometimes you have to pee with bits you have rather than remake the entire world all at once with a utopian panacea.
    - borski 2y ago
      Oh, of course - if you have no other options you go with what you have. But if you have other options, I think too many people are also stuck in “I know what I know and I know it will work” and will happily kludge along while something else is sitting right next to them, better for the job. Neither extreme works.
- mangamadaiyan 2y ago
  I agree. I'd go further and say that the modern attitude is to discard everything "old", regardless of whether it is understood or not.
al_borland 2y ago
I can only hope this is cyclical, like most other things. Eventually organizations will reach a breaking point and realize if they want reliability, stability, and longevity, they need to slow down and do things the right way. At least I hope that’s the case. It doesn’t seem like the current pace can or should be maintained. It produces so much throw away junk.

The modern attitude is discard everything "old", not immediately understood, and abandon standardization and simplicity.

borski 2y ago
Eh, I don’t think that’s true. I think you’ve just had bad experiences, and that that can definitely be true in pockets. For example, I am exceptionally happy that we have standardized on OpenAPI documentation and/or the self-documenting nature of GraphQL (where used) rather than WSDLs and the other ancient nonsense. I’m also glad we’ve mostly progressed from SAML to OAuth2/OIDC/JWT. Sure, SAML still exists but it’s definitely on its way out, once the enterprises of yesteryear eventually switch. I don’t know if you’ve ever built a SAML application and/or IdP, but it’s awful. Sometimes “old” is just worse.
- hi-v-rocknroll 2y ago
  You're cherry-picking technologies. I'm talking about people. Yes, I have. Krb5, LDAP, OAuth2, CAS, and SAML 1 & 2. XML sucks but sometimes you have to pee with bits you have rather than remake the entire world all at once with a utopian panacea.
  - borski 2y ago
    Oh, of course - if you have no other options you go with what you have. But if you have other options, I think too many people are also stuck in “I know what I know and I know it will work” and will happily kludge along while something else is sitting right next to them, better for the job. Neither extreme works.
mangamadaiyan 2y ago
I agree. I'd go further and say that the modern attitude is to discard everything "old", regardless of whether it is understood or not.

al_borland 2y ago

I can only hope this is cyclical, like most other things. Eventually organizations will reach a breaking point and realize if they want reliability, stability, and longevity, they need to slow down and do things the right way. At least I hope that’s the case. It doesn’t seem like the current pace can or should be maintained. It produces so much throw away junk.