• 0 Posts
  • 173 Comments
Joined 9 months ago
cake
Cake day: January 3rd, 2024

help-circle

  • Real world experience can help, but what we have now is also too stupid to recognize when it’s succeeding or failing. It just greedily gobbles up inputs and feedback indiscriminately.

    There’s currently no way to know if the necessary advancement, to advance independently of humans, is 2 years or 2000 years away.

    Even so, nature tells us that advancement probably isn’t coming at all. It’s not needed, so long as there are billions of humans available to partner with.


  • MajorHavoc@programming.devtoAsklemmy@lemmy.mlIs Google Maps getting worse?
    link
    fedilink
    arrow-up
    84
    arrow-down
    2
    ·
    edit-2
    5 days ago

    Makes sense. Google has been replacing skilled engineers with tail-eating AI regurgitation engines, which are getting progressively worse as they eat their own shit.

    But I’ve been told those regurgitation engines are about to get really smart and replace all skilled labor.

    So maybe it’ll be fine.

    Or maybe, as we’ve already started to see, more and more useful stuff will only be available via the Internet wayback machine, until they kill it.





  • Bare minimum place to start: See if you can get the team to agree that these documents should exist in every project root folder:

    • README.md - What is this even for? Audience: Managers.
    • CONTRIBUTING.md - What steps are needed to build this? What steps are needed to be able to run the tests? Audience: Developers.
    • CHANGELOG.txt - Describes the contents of every tagged release. Audience: end users.

    Stretch goal: pick a spot (readme is fine) and make a list of sources (data in) and sinks (data out). Include contact information for whoever can reset the credentials or fix the firewall.



  • I figured out how to remove most of the safeguards from some AI models.

    Nice.

    How do you feel about this?

    It’s another kind of power. I try to use mine responsibly, but also to give myself a break when I don’t meet my own standards.

    Some good advice I got once was that it’s impossible to “un-say” something, so it pays to think twice before speaking.

    If your gut is telling you to pause, listen to it. Wait to move forward until you feel better about it.

    As someone else pointed out, responsible disclosure is an option.

    You also have the option to just quietly enjoy a better copy of the AI than others have.

    If you decide to publish your discoveries, be aware that others will judge you for how you go about it. For me that means the two options are responsibly, or anonymously.










  • Well said.

    Here I am trying to wind people up and you’re responding with thoughtful nuanced consideration.

    You make some great points.

    I’ll add - for folks reading along - I do think a class is still almost always an anti-pattern, even with all the OOP class function and factory pattern stuff removed.

    I also feel (as you referenced):

    • Functions being forced to reside inside objects is just stupid.
    • Factory patterns are horrible, because they mix config into program code, maximizing uncertainty when debugging

    And also:

    • Inheritance is almost always a worse idea than an interface.
    • classes tend to have additional fancy tooling to make it easier to carry state data around - which is usually a bad idea

    State data is a necessary evil in most programs.

    I’ve found that most advanced class object implementations treat program state data more like a pet than a threat.

    Sorry for the long response - I know you don’t need it - you know what kind of tool you’re looking for.

    I figure they extra detail above might provide food for thought for folks reading along who are surprised there’s even contrasting opinions on classes.

    (And I feel a little bad for not really posting anything very useful earlier in the thread.)