I was thinking the same thing (also zero drive and rf experience lol) but it would seem like an easy way to actually make an escape diversion because the fiber line would typically be pointing to the origin of the attack.
That might actually be a good bot project; just slowly going through Google maps and trying to update missing information from OSM like road type, lane width, etc.
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
Ahh sounds like you had a sort of ad block problem! Turn on an ad block, client doesn't see any ads and then starts thinking "well maybe there just aren't ads and you're not doing anything" so you add a counter to show how many ads are blocked c:
Your gut feeling is the exact same I had when I was reading the report, abysmal. Then I realized it was hosted on the internet without any auth to access the report and that feeling just got worse.
From the very get go I tried to curb their expectations and be wary of spend because of the heavy token subsidation at the moment that's expected to increase especially with the IPOs later this year. At the moment I think I'm going to treat this as a way to introduce systems I thought we needed and have the ability to increase spending to do so, including spending on AI if I think it would be worth while.
I'm starting to get the idea that the LLM is just a small part of this and what's really important is instead the bunch of architecture and guardrails around it to form how the humans and ai will act with any given system.
Those are all very helpful points, especially the last one; I've always tried to include standardization in the company but was never in the position to enforce it before
I hadn't considered making an MCP server for our stuff, it feels obvious in retrospect, thanks! As for the self hosting I'd definitely love to but convincing a small company to shell out the kind of money to run something strong enough locally is something I don't think is going to be likely, even if it'd cost less in the long run.
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"
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.
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"
I feel strongly that "next" Thursday should be not the next instance of a Thursday but rather the first instance of a Thursday past the contained set of the current week (so the next row on a calendar). I.e. if it's Tuesday, "next Thursday" isn't the Thursday two days from now but the Thursday 9 days from now.
I've also started using it recently and I'm not sure if the way I'm doing it is particularly "right".
I don't have a lot of knowledge of practical coding practices because in school we literally had a new project every two weeks so I never learned things like you need unit tests or proper architectural design. It was mostly making sure whatever project there was that week ran and didn't crash.
So now I'm working as a sysadmin doing the random junk a sysadmin gets pushed on them. What I've been doing is telling it my project plan, Claude will write up something that looks better, and I continue to have a back and forth about architecture and libraries, asking it if it thinks any particular idea is good or bad, until I get to a place I'm happy.
Then because I want to learn rust and implement it myself, I'm having Claude basically guide me through creating it like a teacher would, with it taking on a very Socratic tone ("now that we've done this, what do you think is the next step?" "We have a list of CSVs so what do you need to do to read their values?"). And I've been moving forward but by bit like this.
I don't know if it's a particularly good way, honestly, I'd love feedback from anyone who's done something similar or whatever!
Barnyard gossip with a pinch of divination. Mad science is actual science but for the explicit purpose of being evil or off the walls whacky; given enough time or a proper application mad science can turn into normal science.
I was thinking the same thing (also zero drive and rf experience lol) but it would seem like an easy way to actually make an escape diversion because the fiber line would typically be pointing to the origin of the attack.
That might actually be a good bot project; just slowly going through Google maps and trying to update missing information from OSM like road type, lane width, etc.
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
Ahh sounds like you had a sort of ad block problem! Turn on an ad block, client doesn't see any ads and then starts thinking "well maybe there just aren't ads and you're not doing anything" so you add a counter to show how many ads are blocked c:
Your gut feeling is the exact same I had when I was reading the report, abysmal. Then I realized it was hosted on the internet without any auth to access the report and that feeling just got worse.
From the very get go I tried to curb their expectations and be wary of spend because of the heavy token subsidation at the moment that's expected to increase especially with the IPOs later this year. At the moment I think I'm going to treat this as a way to introduce systems I thought we needed and have the ability to increase spending to do so, including spending on AI if I think it would be worth while.
Thanks for your input c:
This is wonderful thank you.
I'm starting to get the idea that the LLM is just a small part of this and what's really important is instead the bunch of architecture and guardrails around it to form how the humans and ai will act with any given system.
Those are all very helpful points, especially the last one; I've always tried to include standardization in the company but was never in the position to enforce it before
I hadn't considered making an MCP server for our stuff, it feels obvious in retrospect, thanks! As for the self hosting I'd definitely love to but convincing a small company to shell out the kind of money to run something strong enough locally is something I don't think is going to be likely, even if it'd cost less in the long run.
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"
Lol alright, I'll definitely keep that in mind.
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.
Well if it makes you feel better I hit 100% and am currently trying to learn rust...
Unrelated but the ventoy usb I keep on me really helped me today after a ram stick decided to die and corrupt my system along with it
UK gov saw V for Vendetta and thought it was a guide for oppression
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"
I too want to leave, do you have any resources I can read to try getting out?
I feel strongly that "next" Thursday should be not the next instance of a Thursday but rather the first instance of a Thursday past the contained set of the current week (so the next row on a calendar). I.e. if it's Tuesday, "next Thursday" isn't the Thursday two days from now but the Thursday 9 days from now.
I can't express the amount of visceral discomfort this brought me.
I've also started using it recently and I'm not sure if the way I'm doing it is particularly "right".
I don't have a lot of knowledge of practical coding practices because in school we literally had a new project every two weeks so I never learned things like you need unit tests or proper architectural design. It was mostly making sure whatever project there was that week ran and didn't crash.
So now I'm working as a sysadmin doing the random junk a sysadmin gets pushed on them. What I've been doing is telling it my project plan, Claude will write up something that looks better, and I continue to have a back and forth about architecture and libraries, asking it if it thinks any particular idea is good or bad, until I get to a place I'm happy.
Then because I want to learn rust and implement it myself, I'm having Claude basically guide me through creating it like a teacher would, with it taking on a very Socratic tone ("now that we've done this, what do you think is the next step?" "We have a list of CSVs so what do you need to do to read their values?"). And I've been moving forward but by bit like this.
I don't know if it's a particularly good way, honestly, I'd love feedback from anyone who's done something similar or whatever!
This implies that Pluto is a lovecraftian entity, and that brings me much joy
Barnyard gossip with a pinch of divination. Mad science is actual science but for the explicit purpose of being evil or off the walls whacky; given enough time or a proper application mad science can turn into normal science.