• 0 Posts
  • 49 Comments
Joined 3 years ago
cake
Cake day: October 15th, 2023

help-circle




  • If I’m not going far, not driving or not planning on spending much then yes, wallet stays at home.

    Otherwise, if I’m driving then I’m taking my driving license with me (you never know), if I’m making a purchase over the contactless limit then I need to take my actual card with me anyway, or if I’m away for a longer period then I might need cards that I don’t have linked to my phone (like my corporate card - like fuck am I putting that in my phone).

    And for all that, I’d rather have a wallet instead of just a loose amalgamation of plastic in my pockets.















  • I have witnessed companies make this exact mistake before - they have a legacy system written in $LanguageA that they either cannot find developers to maintain, believe is badly written, or does not support some new feature they want to implement (or some combination of the three) - and decide to solve this by taking the existing codebase and porting/transpiling it to $LanguageB (which is more modern, performant, is easy to hire developers for, etc) - without actually rewriting or rearchitecting anything.

    What they are actually doing is substituting one kind of tech debt for another. The existing code that was poorly written and/or not well understood is now just bad code written in a different language. Fixing bugs or implementing new features now takes just as long, if not longer to account for the idiosyncrasies of how the code was ported.

    And now this is being done by AI with even less oversight than usual? Recipe for a maintenance disaster.