• 2 Posts
  • 73 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • I mean, that could be extreme, or really not that bad.

    Refactors have a way of generating a lot of changes. Half our job is code review, kind of have to get over it and go read some code.

    If someone put the effort in to write it, it’s your responsibility to put the effort in to read it and review it.

    If the style is difficult to read and non-standard for your repository or not. Conventional then your repository and your engineering team should be following set standards to ensure consistency.

    If you’re doing this then most PRS shouldn’t be that difficult to review.

    I say this, spending a decent part of my week reviewing something like 40+ PRs.











  • I’m familiar with them.

    These are projects sitting years, maybe even a decade, away from maturity. IF web standards and capabilities don’t change at all over the next 5-10 years.

    Hopefully that puts this into perspective. These are really cool projects, but without a massive influx of engineering effort and organization, they will likely be perpetually, hopelessly, behind the standard rate of change required of browsers. Nevermind meeting the current standards of performance, security, observability, ecosystem, user and developer experience.

    It’s always good to check in on these projects yearly, see how it’s going, see if they are accelerating or slowing down. Eventually one of them will take off, and potentially leech resources from other similar projects.


    Though, the nature of FOSS is that 1000 people will work on 200 different projects all trying to do the same thing, instead of combining and organizing efforts to go after the same unified goal.

    This isn’t really a statement of fault but rather a statement of reality. Without dedicated full-time organization, this is usually how scattered resources solve problems. Which is a core problem here in that dedicated organization to rapidly grow the engineering effort for a particular project usually requires funding and full-time employees. To both market it to engineers as an interesting project, mature documentation and DevX, mature the onboarding experience for devs, and to handle the organizational aspects of distributing said work.




  • Yeah, but they hold none of the actual real emotional needs complexities or nuances of real human connections.

    Which means these people become further and further disillusioned from the reality of human interaction. Making them social dangers over time.

    Just like how humans that lack critical thinking are dangers in a society where everyone is expected to make sound decisions. Humans who lack the ability to socially navigate or connect with other humans are dangerous in the society where humans are expected to socially stable.

    Obviously these people are not in good places in life. But AI is not going to make that better. It’s going to make it worse.