• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle
  • It’s super hard to get involved as a UI person. If you’re a developer, you can just rock up to a project and fix bugs, and if you follow the coding style they’ll probably get accepted.

    If you want to successfully contribute as a UI person you have to convince a bunch of developers that you know what they should be doing better than they do. It basically never happens.







  • It’s very true on a Mac. Almost every time you click the green button, it jumps to full screen and then you can’t drag another window on top of it.

    It’s a pain in the arse because my workflow is to have a reading screen with documents and emails on, and a work screen with whatever I’m actually doing. But if outlook is full screen, you can’t drag any other windows on top of it.

    Don’t know why the first guy was saying this is a Windows thing though. I only run onto it on macs.













  • Yeah I thought you’d ask this. Basically they’ll never do this, just because their attitude is “fuck you I’m a bank”.

    Beyond this, there’s a big difference between source code and having a working system.

    For very long running systems their state depends very heavily on how they were maintained, little bits of informal design decisions that get components working together, and the order stuff was loaded in, and what other services were up and running when you booted up.

    None of this magic is captured by source code, and it can make even setting up a replacement server, even as part of the same infrastructure really hard.

    Of course banks are moving to more modern dev methods that encourages turnkey deployment, but the fact that they still rely on a bunch of COBOL code tells you there’s a lot of very old system running in “do not touch” mode