Raimi's Evil Dead were just a unique phenomena, they are products of the time and the talent involved that you just can't intentionally recapture.

Yeah unfortunately I suspect it will continue to improve over time :/

Holy shit.

My understanding of current gait analysis tech is that it isn't commercially ready without special equipment (like floor sensors). Do you have links to more recent info?

Yeah I've got no idea. Seems like you can sue people for anything in the US but it probably isn't clear cut.

It's basically criminal negligence at this point. Imagine what a competent game studio could do with a billion dollar budget.

There's a point in the not-too-distant future where I'm just wearing my covid mask whenever I leave the house. I already wear it in Bunnings. And it won't be long before camera glasses are so prevalent that my assumption is I'm always being filmed in public.

If you've only used it inside an IDE I recommend trying Claude Code Desktop. I use it from the command line and find it a much better workflow than the IDE integrations I've used.

Claude is actually very good at analysing and documenting a codebase. Get it to do a high level analysis and document, and then more granular versions of that for sub sections, down to the level of detail where you think you need. Tell it to document just the functionality and business rules, rather than the code itself.

You can verify the details by hand and with your friend to be confident you've got the business rules correct. Then use Claude in a similar way to create technical design documentation from the business rules docs, starting at a high level design and then creating more detailed subsections. You can give it specific technical direction through this process, with the kinds of architecture and patterns you want to use.

If you haven't worked with Claude much, its important to know how to work with it for good results. Always break up your sessions with it. Just having a single conversation that you keep working on for days or weeks will give increasingly poor results as the amount of information it has to keep track of blows out. Have targetted discussions that generate an output (usually documentation) and then start a new conversation that uses the output from the previous discussion, but focuses on a more granular aspect of it. As you generate documents, have claude update its "claude.md" file, which is a project file with any info you want to include in every conversation. Having an index to your documents so it knows which document to look for for a specific subject will save you a lot of time and tokens.

This is whow I would reverse vibe code a vibe codebase. It sounds like you haven't used Claude much, it is actually very capable when managed correctly by a skilled programmer. I'm happy to answer any questions you have.

Cue the downvotes.

The difference between auto-generating hundreds to thousands of words, versus having to manually read and type all of those words out yourself is very obviously a lot more than "nothing".

And that's not even taking into account the fact that we don't know what their method of watermarking is. From how they're talking it sounds like it will be algorithmically embedded in the text itself somehow, through specific choices of words or something similar. If that's the case, typing it out word for word will retain the watermark.

Yeah we'll see how that plays out for SAS but they've at least got a decent window until Harper's rookie contract ends. There'll be tough decisions to make at that point with their big 3.

Yeah I would love to see Fox playing well through to the trade deadline to boost his value, and then get off that contract and spend it on a high level power forward. But SAS has always valued continuity very highly, and considering last season's performance I think will probably keep Fox for the rest of next season.