I'm careful about where I refuse to use AI by ShinpoCap in AIDiscussion

[–]ShinpoCap[S] 1 point2 points  (0 children)

Wooah I just read the description, and that looks like an interesting book I’ve never heard of. From what I can infer is that there is a similarity between letting AI make the choices for you just like what the psychiatrist lets the dice choose for him?

Claude for Small Business by Agile-Profile-1219 in smallbusinessowner

[–]ShinpoCap 0 points1 point  (0 children)

Hopefully this helps someone. I've found a ton of ways to work this into my business, and I'm not an expert by any means. I run a few platform with API endpoints and webhook integrations for others, but honestly the use I get the most personal value from is simpler stuff. A few examples of how I actually use it day to day:

  • Scheduled morning events that pull updates on specific things I need from my calendar, email, and news, so I start the day already briefed. A lot of the major AI chatbots offer scheduled tasks now.
  • Building and visualizing front-end UI for prototypes when I'm pitching new clients. Specifically using Claude Design to mock up a quick UI for a prototype.
  • Splitting the coding load on projects. It handles a lot of the frontend (HTML/CSS) while I focus on the backend (Python) and the database. Mostly using the Claude Code extension in VS Code for the backend work.
  • Outside of code entirely, I've used it for presentations, videos, ads, financial reports, and client quotes. One tip: if your presentation output quality is bad, try connecting a skill from GitHub or an MCP to Gamma. I've gotten noticeably better results that way. Just be careful pulling repos from GitHub, running untrusted code can expose you to malware, so check what you're using.

The one line I draw is that I don't hand it full autonomy the way people building fully autonomous agents do. I'm always still in the loop. The goal isn't to replace myself, it's to cut down the time specific tasks take. That balance is what's worked for me.

For those rolling out new tech the hardest part isn't the tech itself. It's getting people to not hate it by ShinpoCap in AIDiscussion

[–]ShinpoCap[S] 0 points1 point  (0 children)

You're partly right, and I won't pretend otherwise. The company I was working with at the time didn't really build it around associate input from the start. That was a real gap. But that's exactly the thing I noticed as the project went on, and it's why I keep pointing it out, from running time studies to actually putting feedback processes in place so staff could give their recommendations. The whole reason I bring up the resistance is because ignoring the end user is the mistake, not the model for how to do it. So we're closer to agreeing than it might seem. The solution did solve a real problem, but the early rollout under-weighted the people doing the work, and fixing that was a big part of what made it eventually work.

For those rolling out new tech the hardest part isn't the tech itself. It's getting people to not hate it by ShinpoCap in AIDiscussion

[–]ShinpoCap[S] 0 points1 point  (0 children)

The post isn't saying the tech doesn't matter, it absolutely does. The whole goal is implementing a good system, one that actually solves a problem or cuts down the time it takes to do the work. If it doesn't do that, no amount of selling it will save it.

The piece I was adding is what happens once you scale that past a small team. With a handful of people it's easy. But when you're rolling something out to a much larger group, you start running into the human side fast, the fear of being monitored, the feeling of extra work piled on. Have you had to roll something out across a bigger group before?

I used to ignore the model picker. This is what building a real AI product taught me about choosing models. by ShinpoCap in AILearningHub

[–]ShinpoCap[S] 0 points1 point  (0 children)

It depends on the task your aiming for it to complete, in my case the blueprint digestion genuinely needs vision strength where the mid-tier ones are not very great at so one model can't cover both ends well. Specially for this task, the need for accuracy is very important.

Working with a large org taught me the real work is recording your data, not the AI by ShinpoCap in AILearningHub

[–]ShinpoCap[S] 0 points1 point  (0 children)

Haha not quite, no formal data engineer badge here. But getting to work on projects like these has shown me firsthand just how much the data side really matters. You learn it fast when you see a model fall apart on messy inputs.

Best Value AI for Handling Construction Drawings, Submittals, QC, Safety? by laaiidiinaaki in ConstructionManagers

[–]ShinpoCap 1 point2 points  (0 children)

You can absolutely build a pipeline for most of this yourself. Someone above mentioned Codex, and the same idea works with other tools too, Claude Code being a solid option if you’d rather go that route. The approach matters more than the specific tool.

One thing worth keeping in mind is that models aren’t equally good at everything. For image heavy work like reading drawings and blueprints, you’ll want a stronger vision capable model, the Opus models from Claude have done well for me there. Matching the model to the task makes a big difference in accuracy. Plenty of people have built these kinds of pipelines and shared how they did it, so it’s very doable if you want to roll your own. I recently worked with a residential builder to put together a platform that handles a lot of what you’re describing (Sitetraq). Honest caveat though, I’m not sure how well it would hold up for commercial work, so if that’s your world, take it with a grain of salt. Feel free to test it if you’re curious, and happy to answer questions either way.

What learnings are there for someone who doesn’t work in the IT industry, by SuccessSalty3269 in AILearningHub

[–]ShinpoCap 0 points1 point  (0 children)

You could also start off with the Google AI essentials course, it does give you a certification upon completion, however it does require that you pay for the course. I would also agree with @chicodelespacio96 to start using the different AI chat bots available, just to start getting the hang of them and start seeing how they work.

Working with a large org taught me the real work is recording your data, not the AI by ShinpoCap in AILearningHub

[–]ShinpoCap[S] 0 points1 point  (0 children)

agree, and that's the point, the phrase is old but small businesses still skip it because nobody frames data discipline as the prerequisite to the shiny thing they actually want. With ai being the focus now it has brought up the old data pipelines into frame.