Comment by bambax

Comment by bambax 4 days ago

5 replies

View on Hacker News

Same experience here, but I'm not sure it's just MS fault; companies have a way of installing a bunch of stupid software on top of one another, that you can't get rid of without admin rights, that continuously do things that slow the system down.

(And, you can have a tabbed file browser on Win7. I still have a Win7 box at home that works perfectly well and that does have tabs in file explorer. I think it was an addon I installed a while ago; don't remember exactly, but it works perfectly.)

bunderbunder 4 days ago

It seems industry-wide these days.

What I’ve seen as an older-than-average developer is that the Agile movement has made it increasingly difficult to make time for paying attention to some of the more subtle aspects of user experience such as performance. Because I can’t predict how much work it will be accurately enough to assign story points to the task, and that means that this kind of work frequently results in a black spot on our team performance metrics.

CD makes it even harder because this kind of work really does need some time to bake. Fast iterations don’t leave much time to verify that performance-oriented changes have the intended effect and no adverse side effects prior to release.

Reply View 2 replies
  • 2muchcoffeeman 4 days ago

    That’s not agile’s fault. That’s the orgs fault.

    We used to have a few days set aside regularly to fix things that would never get prioritised.

    Reply View 1 reply
    • bunderbunder 3 days ago

      I think this is another of those spots where the difference between agile with a little an and Agile with a big À comes to the forefront.

      Little a agile is about pushing back against dysfunctional business dynamics for the sake of humanistic goals like employees’ mental health and doing right by customers.

      Big À Agile co-opts that, and is more about squeezing as much money out of everyone as possible while wearing the trappings of agile values to make it seem more palatable.

      Reply View 0 replies
jjordan 4 days ago

Microsoft is progressively making everything an instance of Chrome. They've seemingly altogether given up the notion of native platform rendering. The win32 api for native ui elements hasn't been touched in two decades. There have been a few failed attempts to move on from it like Siverlight, WinForms, UWP, LightSwitch, etc, but they never bothered to revisit their native UI library. So now everything is a Chrome instance.

Reply View 1 reply