• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle



  • Shift-left eliminated the QA role.

    Now we have AI generated shit code, with devs that don’t understand the low level details of both the language, and the specifics of the generated code.

    So we basically have content entry (ai inputs) and extremely shitty QA bundled into the “developer” role.

    As a 20 year veteran of the industry, people keep asking me if I think AI will make developers obsolete. I keep telling them “maybe some day, but today’s LLMs are not it. The AI bubble is going to burst, and a few legit use cases will make it through”



  • In general, digital privacy invasions have been very successful because of attrition.

    Most people don’t care, those that do hold out, but then every competitor does the same and you no longer have any real alternatives. Eventually, the hold outs need to replace [car in this case] and the sting of the objectiknable change has faded, and they just move on.

    Rinse and repeat.

    We lost the fight for meaningful net neutrality, basic digital privacy rights, broadband limits, etc.

    They’ll win this one too. Eventually. Your phones and IoT with microphones are already doing it.






  • That’s a pretty weird rant on EVs.

    The carpool lanes were very under utilized. Hybrids and later EVs were also slow to be adopted, and the state wanted this adoption accelerated due to air quality and just general environmental consciousness.

    So the state decided to add the carpool benefit, which solved two problems.

    Now that EVs are far more abundant, that policy is getting revisited. Which is fair, because the carpool lane can only support so many before it just gets clogged like the main road. And people don’t necessarily need the encouragement to get EVs anymore.

    Nothing is permanent.






  • I find the “clean history” argument so flawed.

    Sure, if you’re they type to micro commit, you can squash your branch and clean it up before merging. We don’t need a dozen “fixed tests” commits for context.

    But in practice, I have seen multiple teams with the policy of squash merging every branch with 0 exceptions. Even going so far as squash merging development branches to master, which then lumps 20 different changes into a single commit. Sure, you can always be a git archeologist, check out specific revisions, see the original commits, and dig down the history over and over, to get the original context of the specific change you’re looking into. But that’s way fucking more overhead than just looking at an unmanipulated history and seeing the parallel work going on, and get a clue on context at a glance at the network graph.