Principal Engineer for Accumulate

  • 2 Posts
  • 131 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle





  • You: “Nobody who uses AI treats it like a tool, they treat it like an employee they can claim credit for.” Me: “I treat it as a tool.” You: “Wow, you won’t shut up about AI.”

    Wow, you are just the best at reasoned arguments!

    Kindly, fuck right off. (I’m blocking you, so any response you make won’t be for me.)



  • So because everyone you know who uses “AI” treats it that way, that necessarily means literally everyone who uses “AI” must treat it that way? Wow, such flawless logic.

    Some of us see LLMs for what they actually are - tools. Tools that can be useful, but are also dumb as fuck. Claude is fantastic for writing boring, boilerplate shit like unit tests and reasonably good at finding bugs in my code. But I am never going to take credit for its work. If for no other reason than “I wrote this” means “any mistakes in this are mine” and I am not going to take the blame for the dumb shit Claude does.







  • 😆😂🤣 Are you kidding? Have you tried using nouveau? It works, sure, but you can’t play games that are even vaguely modern and if something uses up a bit too much RAM the entire display system starts jittering/lagging or becomes unresponsive. Source: I ran nouveau with a GTX 2080 for years. I was only able to fully ditch Windows once I fully ditched Nvidia (by switching to an AMD GPU and scrubbing every last vestige of Nvidia’s bullshit off my PC).


  • Speak for yourself. I’m a huge Linux fan but I find it rather easy to not annoy people. Mostly because IDGAF what OS anyone who isn’t me is using. And the only time I’d ever recommend Linux is if someone technical was asking for advice. If they’re non-technical, I will tell them to not use Linux (no fucking way am I going to be their tech support). If they’re technical, they can decide on their own (unless they ask me directly).






  • And it’s management’s job to multiply the senior’s estimate by 5 and +/-50% for good measure. And even then, that’s a rough estimate at best.

    Maybe using points for some planning actually works; I’ve never worked at a place that could use it for actual estimates. My estimates are entirely based on gut feel, my feeling of the complexity involved and my feeling of how much the team can get done. Over the last two years (since metastasizing into a CTO) my overall estimates have pretty much always been in the right ballpark. Which is to say, when the CEO says “We’re going to do X, Y, and Z this quarter,” I say “We’ll be able to reach about 50% completion if we work on all of those at the same time,” I’m usually more or less right.

    I’ve never worked with a dev who could make significantly better estimates than me (excluding the early years of my career when my estimates were absolutely awful). Most of the devs I’ve worked with just wouldn’t give estimates; if pushed they’d be as vague as they possibly could. The only boss I’ve had who would give definite estimates was always off by an order of magnitude (as in he thought it would be 10x easier than it was, even though he had decades of experience writing code and managing teams).