- spjtBut it is being continually refueled. The output of an LLM, at least in the process of generating code, is a combined product of human creativity and the LLMl. I have told it what to do, fixed what it got wrong, and verified the solution was correct through testing.
- Yeah if they thought unions were bad, they really won't like dealing with another company larger than them.
- Interesting that I read elsewhere that most Venezuelan oil goes to China due to the sanctions. Would be nice to see them put a carrier group down there to guard their shipments...
- Because it has oil on it, you can sell oil for money.
- No shit. My question is the real question, how can I make money straw-buying GPU's and smuggling them to China?
- Is the new Gemini really that good? The "AI Overview" stuff on the google search page is so incredibly bad that I have never even given it a look. If so, the AI Overview is horribly bad negative advertising because it's so useless and frequently completely wrong.
- I always made sure to include "Time spent on time tracking" when I had to do it.
- > Let's Encrypt was _huge_ in making it's absurd to not have TLS
I still find it too much of pain in the ass to deal with to justify for my personal stuff. Easier to just click through the warning every time.
- Why not do it in English? I have a "program" that exists entirely as the history of an AI chatbot session. To "run the program" I load the history and a file into the message context and say "Now do this file." It kind of reminds me of a Smalltalk VM in a weird way.
- I've always seen estimates as trying to guess the highest number the PO will accept, the time or effort involved in actually completing the task is irrelevant. I have never had a PO or anyone else complain that a task was completed more quickly than expected. However I do have to be careful to not tell them it is complete too early, lest they start expecting shorter cycles.
At least in my company we've stopped calling them "estimates". They are deadlines, which everyone has always treated "estimates" as anyway.
Unfortunately in the real world deadlines are necessary. The customer is not just mad that they didn't get the shiny new thing, especially in the case of B2B stuff, the customer is implementing plans and projects based on the availability of X feature on Y date. Back to the initial point, these deadlines often come down to how quickly the customer is going to be able to implement their end of the solution, if they aren't going to be ready to use the feature for six months there's no reason for us to bust our asses trying to get it out in a week.
- In my experience, having to track my hours absolutely destroys my performance. Thinking about how I need to pay attention to how long I spend on everything is a constant distraction in the back of my head while I try to do anything useful, and then I spend the rest of the day procrastinating having to fill out the paperwork. I know I'm not the only one because the entire dev staff was ready to mutiny the last time I was at a company that tried to get devs to start tracking their hours.
- It sucks if you're looking for entry level work, of course. However, I'm a TL/manager with mostly entry-level reports and I have told them for a while the other side of this mentioned here - by the time they get to senior level they are going to be able to name their price in the shortage.
- In my experience the style bikeshedding comes about when PRs are not properly scoped. At least I have learned to just say TLDR.
- I'm staff and that is probably the main thing I use AI for. It's maybe a bit ironic that AI is a lot better at sounding like an empathetic human being than I am, but I'm still better at writing code.
- This happened to me a long time ago... well not me but my kid. She made a youtube video and got flagged for not being old enough.
- Good luck cracking down when local inference gets cheap.
- I don't think it wants to. Ask any on-call engineer or support tech how they felt when, after having their phone blow up at 1am because everything is falling apart, they found out that this was an AWS-wide outage.
- The thing about AGI is that if it's even possible, it's not coming before the money runs out of the current AI hype cycle. At least we'll all be able to pick up a rack of secondhand H100's for a tenner and a pack of smokes to run uncensored diffusion models on in a couple years. The real devastation will be in the porn industry.
- I love vibe coding because it does the things I hate really well, like meeting test coverage requirements and writing doc comments.
- The difference with fusion is that we have a very good understanding of how fusion works, and exactly what we need to figure out how to do, to make it a viable energy source. It's basically just an engineering problem, albeit a very difficult one due to the extreme conditions. AGI is more like developing warp drive. With AGI, we really have no idea how the brain works or any clue of what problems need to be solved. It's basically just like the underpants gnomes.
Phase 1: Buying more GPU to increase the number of parameters in a LLM Phase 2: ??? Phase 3: AGI
AGI may come anywhere between next week, 1000 years in the future, or never. Anyone who claims to have any idea is full of shit, because we don't even know what problems we need to solve to get there. If we develop a good model of how human cognition works at a biological level, there is at least a direction, but that isn't going to be coming out of some AI hype factory with a datacenter full of H100's making videos of anthropomorphic cats working as pastry chefs.