castral

Is that not how reporting works...? Information was released by the company, someone writes an article about it, editorializes slightly, gives a perspective, publishes it on a related news website, we read it and discuss. The process has to begin somewhere.

I did something similar in the README.md of my foss repo. Unfortunately this doesn't seem to cover all of the possible granular scenarios of what is or isn't AI-assisted. For example, all of the documentation in my repo was 100% auto generated. All of the source files were at most "hint" level. The test sources were a mix of "hint" and "auto".

One singular level is too broad a stroke to paint to anyone who might care, I think.

The loss of AppCode from Jetbrains was a huge blow to my motivation to continue working with Swift. Xcode just can't compare.

I've also been waiting over three weeks to speak with customer support after being gifted an annual subscription just as my payment card expired. The failed payment (after the $200 gift) downgraded my account to the free tier and I lost my annual subscription. I had to pay another $20 to get back into the pro tier plan, but now for some reason I only have $197 in credits and I'm on the monthly subscription instead of the annual. Anthropic basically just made 3+ months of credits disappear for their own billing mistake.

The kicker? When you get downgraded to the Free tier, they don't offer any support beyond the AI bot. You have to go through some hoops to get it to open a support ticket to maybe talk to a human in 4-5 weeks. Unbelievable.

It feels wrong but I can't quite put my finger on the reason why... It will make version control more hectic, for sure. It also seems to be conflating identification with configuration which seems non-ideal. What about versioning and upgrading? How do I find a "well-known" entry point with a file name of flags? Every read now becomes an expensive find and grep lesson... Yeah, I don't like it.

Some of these are nightmare fuel. I love them.

Ah, well... TIL to not take anything geohot writes seriously in the future.

I agree with this take. What does this bring to the table that can't be done with pretty much any preexisting toolset? Hell, even bash and chroot jail...

I think I saw Gaius Baltar implement this on Battlestar Galactica. It went well. /s Honestly seems more like a protocol for encoding a popularity contest, which is already what social media signalling does. How do you defend against self-reinforcing botnets and bad actors "cancelling" other people? I can dilute your human signal by creating massive amounts of LLM-generated noise.

I don't understand how this is supposed to solve anything, and I've seen it suggested as a solution multiple times. If you restrict comments to older accounts, all it's going to do is make the bot creators speculatively open and proactively age accounts for future use.

It's an interesting visualization for sure, but I don't really know what I can take away from it. Is it useful for something?

This is a pretty sexist take considering the original article was not talking about the male loneliness epidemic, but elderly, and indeed the first example used was even of an elderly woman awaiting delivery. The commentary here is really something else.

You can literally do what your generated example does using a type guard. You can also use method overloaded signatures if you dont want to expose your API consumers to union types.

Is it strange that this isn't the first time I've been on this site? It's got pretty great info, and I used to work a lot with vacuum tubes...

Maybe it is the framing of the step as a "reversion" or "roll-back" rather than "spike" or "prototype" that is causing that sense. Personally, I would never throw away the code I spent time and effort writing just to stick to a systematized refactoring method like this "Mikado." I don't think the advice is unsound, and I have done exactly this many times in my own career, but instead of throwing it away I would shelve it, put it in a branch, write a document about what has been/needs to be done, and write a corresponding tech debt or feature/fix ticket for it with the new and realistic estimate.

Yeah but this is how Apple has always done infrastructure/services. Their internal software teams are a mess. They constantly reinvent the wheel poorly, and then they charge a premium for exclusive access. Is anyone surprised by this?

I wish there was more support for AMD GPUs on Intel macs. I saw some people on github getting llama.cpp working with it, would it be addable in the future if they make the backend support it?

I think OP and I have very divergent opinions on what makes a file API "best". This may have been the best 30 years ago. The world has moved on.

To be fair, the first novel Hyperion is quite literally a survey of major world religions, not just Christianity. It does settle onto Christian symbolism in the second book onward, but the first two novels alone are still worth reading for their ideas. No affinity required, it's just the default Western canon at work.

Wait until you find out what the word 'ciao' meant in the original Italian/Latin: 'ORIGIN: Italian dial. alt. of schiavo (I am your) slave from medieval Latin sclavus slave.'

This really isn't the confusing part about Autolayout. The confusing part is the millions of unclear ways to accomplish a given layout. Or figuring out how to make a scroll view content height dynamic. Or move/create anything dynamically, really.

You have to bring in third party libraries to make it easier to work with the API programmatically and then pray to the constraint solver gods that your changing a height constraint constant and adding 4 new constraints into the view hierarchy doesn't throw the most useless error ever seen.

It's just unpleasant.