beardedetim

Yeah I'd assume this is to allow us to train on their TPUs with torch instead of needing to rent a GPU

Location: Tennessee, US

Remote: only

Willing to Relocate: Probably not but open to PNW/Europe

Technologies: Web (React/TS/etc), backend (node/python/go), infra (everything from ansible to Terraform). When I say full stack I mean I've shipped and owned pager across the stack

Resume: via email

Email: [email protected]

I'm looking to move from IC into EM/engineering leadership. Over a decade experience across both.

I think of this and the book the author wrote Computer Power and Human Reason every time I try to talk to product about the short comings of LLMs

It's a ~year old product that started on GH. So this is the first time this team has had to think through "okay, so this isn't as reliable as it was at $oldjob."

We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?"

No idea if/when we decide to pull that bandaid but I think once we can't merge a hot fix into main because of GH being down, it'll be a big org push to replace it.

What's everyone else using? Self hosted Gitlab? Gitea?

Tinfoil hat time but I think they definitely did _something_ at that time that "changed" the system. It's the Cambridge Analytica/Trump time and I believe that FB definitely "changed" at the same time.

This is what I don't understand about this policy. There's no way a senior has enough spare capacity to be the gate keeper on every PR made by AI below them. So now we are just making it so the senior people use more AI to keep up but now they're to blame for letting it happen.

It sounds like a piss poor deal for seniors unless senior engineer now means professional code reviewer.

Early in my career I tried very hard to "be concrete, cold, and direct" because that's what I thought a good communicator would do. It was seen as attacking to anyone below me and confusing to anyone above me. I was naive and I suffered for it.

I definitely agree with what you're saying here where these words actually do mean something, but it's completely opaque to those outside the "know". I also have found that there's not any better way to express information to those in the group than in this coded language, even if it makes completely no sense to me.

I wish younger me understood that the way I'm being perceived is the only important thing, not choosing the "best" words to technically describe a situation

This feels like such a valid solution and is how past $dayjobs released things: send to the free users, rollout to Paying Users once that's proven to not blow up.

I've become a huge fan of A.E. van Vogt and have been slowly collecting all of his pulp books.

This is the reason I left the "main" social media and what keeps me from engaging too much with Reddit/HN or any of the other new hotness like Mast, nostr, BlueSky, etc: it's just rage baiting or karma farming

This is a good callout/distinction you're making. How we view the goal of the experience determines our experience itself. The guitar analogy is really good because if your goal was to learn guitar, it's definitely not wasted but if your goal was to learn this one specific song as quickly as possible, I could see how my perspective would be different.

they have concepts of a product

I am getting

> "error": "Text to speech is not available. Please set Azure speech credentials in .env"

Cannot agree more to this sentiment. I call it "throw away code" and it's always seemed like the easiest to change in the future, and we all know everything is gonna change in the future.