Spyke

Replies

Comment on

my own personal Chatgpt

Reply in thread

This bothers me so much, my coworker constantly refers to Claude as "he" even when I remind him that's a bad idea for long term, to either call it "it" or Claude. But nope even in front of the CEO it's all "I was just working with him and gosh he makes everything so great blah blah blah, he frustrates me sometimes blah blah"

I think my coworker will be on the short path for ai psychosis

Comment on

catgirls save us

Reply in thread

I've gone for the corpo middle ground and my company picture is the Japanese business blahaj in a suit. I've been told, "I don't even look for your name I just look for the shark, it stands out more"

Comment on

*Permanently Deleted*

I use AI as a rubber duck, to compliment the rubber ducks on my desk when they don't give enough feedback. So it's use is mostly conceptual, I find that models that provide "thinking" output perhaps more useful than whatever its actual answer is because it asks questions about edge cases I might not have considered.

As for code generation, I hate it. It outputs garbage, forgets things, hallucinates, and whatever thing it writes I'll have to rewrite anyway to actually make it compile.

As I'm fairly isolated at work I think it makes a good pair programmer partner, so to speak. Offering suggestions that I can take into consideration and research heavily if I think it's a good one.

memes

Comment on

Hail Corporate!

Reply in thread

I don't know if they'd even be up for it but at this point I think the best option would be Framework getting into it as theyre already trusted by the community.

But even if we get the hardware down there's another issue - we need an open source, government approved, bank approved Wallet app. There's only Google or Apple wallet to store important documents on Mobile at the moment. Frustratingly, some governments are using only those two as a source for national verification which is obviously a problem.

Comment on

Thrust into an AI role

Reply in thread

We're honestly already running on a dev deficit, so for the foreseeable future I don't think they're in any danger. Interestingly, management seemed wary of vibe coding and letting the ai write large swaths of code used in production, which I'd say is a generally safe stance considering the obvious stability issues that have become frequent lately. As for the devs themselves, they're seemingly not interested in really playing with the ai to begin with, but I somewhat expected that as I have different issues with them like "please update your code to GitHub the main branch hasn't been updated in months" and "don't commit pem keys to git"

Comment on

Thrust into an AI role

Reply in thread

I suppose my views are predominantly that it's just kinda fine? I think it's naive to think that it has no value but also don't think it's going to be the end all be all of tech and once the hype train settles we'll probably have a medium similar to the dot com bubble bursting.

I'd say I'm somewhat familiar with llms in general; self hosting a few with llama-swap, testing harnesses, generally just testing its capabilities year after year. As for my teams we have our singular backend dev, singular mobile dev, and singular hardware engineer who hold up our platform and sold consumer devices and then the litany of customer facing staff.

Morbidly, I only got the job because their ai hype man contractor died and they decided "maybe we should look internally instead", but the general work he produced was a singular Claude vibed executive report.

Comment on

Quarkdown

Reply in thread

Looking through some of the docs I'm afraid I won't be able to move off of Typst to this either. Typst has a long standing bug that I would have liked to avoid (lists that are too long will overflow memory and the maintainers seem to not want to temporarily dump to disk) but if even rust has an issue with those 100k+ row lists, I'm not sure kotlin will handle it better.