• 0 posts
  • 13 comments
Joined 3 years ago
Cake day: June 15th, 2023
  • Specifically, the 13th amendment, which abolished* slavery:

    Neither slavery nor involuntary servitude, except as a punishment for crime whereof the party shall have been duly convicted, shall exist within the United States, or any place subject to their jurisdiction.

    So, yes, prison slavery is expressly legal.

  • The key thing for elections is that all counts ought to be auditable and verifiable. It doesn’t matter whether the count is done by humans or electronically. Enough information from each individual vote must be preserved so that counts can be verified, during the legal window for races to be confirmed.

    I am old enough that when I first started voting, we used lever machines. You pushed a lever for your choice in each race, then you pushed a big lever, which “recorded” your choice and resets all levers for the next person. But, it recorded your choice on manual dials that showed the vote total. Sometimes, the dial has issues rolling over from “9” to “10”, or “9999” to “10000”. If your vote got swallowed by the mechanical dial, it’s gone! There was no remedy. At the end of the election, the poll workers reported the counts off the dials. If they needed a recount, they looked at the dials and said “Yup, that’s the count”.

    Today, I vote on a paper ballot, which gets fed into a machine. I can see right away if my vote is accepted – if it is not, I can get a new ballot and try again. All those paper ballots are retained so if there is a recount, they can either be run again or physically inspected by hand. It is much better tha it used to be.

  • So, now, when I see senior developers (which I am not) vibe code green field projects, I am just astounded as to how they manage the architecture + understanding + optimization + maintenance context.

    My experience is, they’re not. Like the article says they are just focused on MOAR and not on the quality of the output. It may take years for the unmaintainable code to cause problems, and they may have already been laid off by the time that happens, anyway .

    I don’t write much code anymore, but when I did, there was a fair amount of embedded code, where fixing a bug is more costly than just pushing out a build to a production server. I actively sought out automation back then, but the purpose of the automation was to help cover edge cases and better test the embedded code for flaws that traced through multiple layers of code.

    Whenever I start a new software project, it usually starts with a short period of experimentation when I try out several things. Then, I coalesce on an architecture in my head (and eventually document it), and once I do that I can add more structure to the code.

    Given the state of the AI tools today, I can see myself using them to accelerate all the little fiddly parts of this (especially if I can give it a coding standard and have it stick to it). But I wouldn’t trust it more than that. I would always keep the archictecture separate, because I don’t trust the AI tools to change it on me for no good reason.