• 52 Posts
  • 9.2K Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle


  • In case your attempt to start arguments is sparked from actual ignorance ….

    federal permitting and leasing for wind projects

    • many wind farms are not on owned property. In particular for offshore wind farms there is no land that can be owned. Many projects are in locations leased from the government
    • if turbines are above above a certain height, it affects airspace used for flying, you don’t own
    • even renewables can be bad for the environment. The trope about killing birds has some truth to it, and environmental review keeps it from happening
    • yes, renewables can affect your neighbors and they deserve some consideration
    • yes, it’s conceivable that a wind farm offshore or near a base or a border can have national security implications

    In a nation of laws, things like this are worth considering. However that is different than using them as cover for personal beliefs



  • The government paid like $1B for wind farm developers to abandon projects.

    Most of the time government slows things down, but the current administration actively fights against progress or shatter people want. wtf does he care about wind farms in New England enough to shut them down

    I mean the alternatives are not all wine and roses. We pay among the highest electricity prices in the country and a big part of that is depending on wind farms that are already like a decade behind. Previous governments slowed them down, letting everyone be heard, but they didn’t actively oppose








  • They probably can’t.

    Arguably I’m creating a vibe coded repo now.

    We have a fairly complex continuous integration environment but need to move to GitHub, because we like following fads and don’t realize that fad is over. But GitHub CI is really immature, difficult to use, and just can’t do anything beyond the basics. I’m sure it’s great for individual projects and startups but it just doesn’t scale for enterprise use. Everyone gets excited at using yaml to describe workflow, but then you’re kind of stuck with shell scripts for actual implementation and the easy stuff runs out after the first hour. I am very much not impressed.

    So I’m trying to create a shared workflow for like 5,000 repos and it’s miserable. After a couple weeks I have a couple thousand lines of generated shell script that’s already beyond my ability to maintain to maintain by hand. So I’m well past “I told you so”, and my only route forward is yet more generated shell script. It’s too late to try to contribute without ai




  • My manager, several jobs back. He put me on the layoff list so he could take my job (which he was completely unqualified for)

    Or maybe the VP above him. Agree to lay me off because I was fine with being first in or last out, but drew the line at being both first in and last to leave (in a startup where everyone was working insane hours so I seriously considered working overnight as the shorter workday)

    Or maybe the CFO because he let me spend money buying my options on the way out in case they succeeded (it was like $200), then immediately issued new options to zero out the ones we got

    You know, that was just a really toxic startup