• 2 Posts
  • 13 Comments
Joined 5 months ago
cake
Cake day: May 28th, 2024

help-circle

  • it’s pretty good for things that I can eye scan and verify that’s what I would have typed anyway. But I’ve found it suggesting things I wouldn’t remotely permit to things that are “sort of” correct.

    Yeah. I haven’t bothered with it much but the best use I can see of it is just rubber ducking.

    Last time I used it was to asked how to change contrast in a numpy image. It said to multiply each channel by contrast. (I don’t even think this is right and it should be ((original value-128) * contrast) + 128) not original value * contrast as it suggested), but it did remind me I can just run operations on colour channels.

    Wait what’s my point again? Oh yeah, don’t trust anyone that can’t tell you what the output is supposed to do.





  • My point isn’t actually about the software.

    Agile is a limited form of workplace democracy that succeeded because the usual forms of disciplining workers couldn’t be enforced to stop it. It’s taken off in software because the outlay for software is so low that people can just quit their jobs and start a rival project with preferable working conditions. It’s stuck around because it’s significantly more effective than dictat.

    I have problems with agile too. A lot of the “ceremonies” seem more like cult rituals and bad practices are often assumed to be self justifying when they should be interrogated. (I once had a bust up in the office because I insisted in creating a future proof test framework instead of writing just what’s needed at the time. I was overruled and I’m still mad about it).

    So I guess my point isn’t even about the specific agile practices either.

    The point is that workers are able to self manage when they’re allowed to, and agile has accidentally proven this to be the case. Other work places should adopt some of these ideas. And these ideas should be pushed further, into business decisions and HR and management. And physical communities etc. all the way up to actual government.




  • What is impact engineering though? If it’s it’s just agile while being cognisant of technical debt over MVPs, I don’t know if it’s necessarily that different.

    It seems the study was designed to sell a book and I can’t find anything about what that book says. I should probably read it but the bait way it’s being sold makes me resistant to paying to find out.



  • It’s half way to self management.

    Software exists in a world that kind of exists outside of property. Cynics like to think that Agile got big because as some kind of fad because the kids love it, but the reality is that fully hierarchical models just cannot keep up with self organising teams.

    The old model - the model that most of the rest of the world of work still uses - simply cannot compete on a level playing field where the means of production (a cheap computer) are available to all. A landowner can stop you building your own house, but Microsoft can’t really stop you building your own software, so they still have to put in work to collect rent.

    Imagine what we could accomplish as a species if the goals and distribution of resources were also decided democratically.





  • I hate that “soviet MLs” is used as a label here, because the failure of the USSR is down to the undermining of the soviets.

    The economy being centralised and then destroyed is why post-USSR states are disfunctional, and it’s the same vulnerability the EU faces.

    Were the economies actually managed democratically, they might have been able to weather the storm instead of getting fucked over by the world bank and IMF.

    Instead of cooperating to sort out their affairs post-empire, countries are expected to play monopoly and somehow magically not have the same end game as monopoly.