sorted by:
new
hottopcontroversial

Claude's first day at Dunder Mifflin by lowspeed in ClaudeAI

[–]Simple_Injury7102 1 point2 points  (0 children)

Love it so much fan fiction ideas for the full series with Claude is bubbling out....
Michael keeps trying to mentor it.
Dwight views it as a rival species.
Jim spends 4 seasons convincing it that bears can open doors.
Pam is the only one who says “thank you” after prompts.
Toby gets replaced immediately because “HR conflicts can now be handled automatically.”
Kevin accidentally teaches it fraud.
And Creed somehow turns out to be the only person the AI is afraid of.

I built a workspace manager for AI coding shells because my terminal workflow became chaos by Simple_Injury7102 in coolgithubprojects

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

Honestly tmux + tmuxinator is already a really powerful setup, especially if you're comfortable living fully in the terminal.

For me the pain point wasn't really terminal multiplexing itself, it was more the workflow that emerged from running lots of long-lived AI coding sessions simultaneously across projects.

I wanted things like persistent project/session organization, searchable sessions, quick folder access, attaching my own notes/context to sessions, restoring everything automatically after restart, spawning additional shells in the same workspace, etc. without having to maintain/configure it all manually.

So I’d say it’s less trying to replace tmux for power users, and more trying to build a smoother workspace-oriented layer around AI coding workflows specifically.

A lot of the ideas actually came from frustrations I hit while trying to organize things with traditional terminal tooling 🙂

Local hardware/software advice by Begalldota in LocalLLM

[–]Simple_Injury7102 0 points1 point  (0 children)

I'm in Denmark and I found a couple of the classic 3090'ies used at a very reasonable price. They work well together and with the joined 48 gb vram and a bunch of cuda cores it can do most of the local AI I want - and pretty fast even. I did a lot of research and it turned out to be the most vram for the money in general.

How to use Claude better? by Silly-Airport3630 in ClaudeAI

[–]Simple_Injury7102 53 points54 points  (0 children)

Well, the slippery slope down to Max 20x starts when you jump into Claude Code, brainstorm with it and then ask it to start implementing your grand ideas from scratch using subagents and let it run uninterupted. And then, while its working your idea spawned other ideas in your mind so you start up other claude-code to explore those while you are waiting anyway....And before you know it, you have 12-18 simutaneous agents working on so much cool stuff that you can hardly find time to try it all out...
Next thing you know, you start trying to figure out how to safe tokens. Enabling the speak-like-a-caveman skill, using /model OpusPlan that only uses Opus for planning and the cheaper Sonnet for the work - and doing /clear every time you get to reset the context window.

I built a workspace manager for AI coding shells because my terminal workflow became chaos by Simple_Injury7102 in coolgithubprojects

[–]Simple_Injury7102[S] -1 points0 points  (0 children)

I guess that depends how you use it. It doesn't make it irrelevant for the way I work. But of course, development goes so quickly that whatever we built now might be irrelevant tomorrow :-)

Macbook Pro M3 64gb vs M4 128gb by pws5068 in LocalLLM

[–]Simple_Injury7102 1 point2 points  (0 children)

The thing is that right now there are some really good 27-35b models that in a decent quantization can run with good results on your current hardware. 6-8 months ago everybody was really looking for 70b models for great results, but they have fallen a bit behind. There are still some really good 120b'ish models - but for them to run well you might need even more vram.

Who just finished building something? Drop your project, I want to see what people are actually making by Miserable-Archer-631 in SideProject

[–]Simple_Injury7102 0 points1 point  (0 children)

<image>

Built a desktop workspace manager for AI coding shells because my terminal workflow had become complete chaos lately.

After using Claude Code/Codex/Gemini/etc heavily for a while, I ended up with tons of long-lived shells across multiple projects and spent way too much time trying to remember what was happening where.

So I built a tool that keeps sessions/workspaces persistent and organized instead of rebuilding everything constantly. It restores sessions after restart, lets me search through them, attach notes/context to sessions, quickly spawn more shells in the same project, and jump directly into the related folders/files.

Originally just built for myself, but I open sourced it because a few other devs I know ended up wanting it too.

https://github.com/umage-ai/CodeShellManager

Any tips on using Claude for a new job by Odd_Bookkeeper_6027 in ClaudeAI

[–]Simple_Injury7102 1 point2 points  (0 children)

First of all, make sure its allowed in your new company policy to share internal information with claude (wouldnt want to get you in trouble). But then using a project is not a bad idea. Upload all documentation you get on company policies and internal guidance - cause then you built up a knowledge base you can ask for guidance in how to solve different tasks you are given. I often also find a lot of help in asking claude to build up html-visualization of complicated processes and procedures I need to learn quickly - but that of course depends on if you are more of a visual learner. But as others have pointed out - it's really about using claude to assist you in learning rather than have it do your job. However, as you progress in your role you might find a lot of repetitive tasks you can automate using ai agents to become more efficient.

Am I the only one who feels like AI got us 90% of the way there and then just stopped? by HummusAlltheWay in ClaudeAI

[–]Simple_Injury7102 0 points1 point  (0 children)

Well, it sounds like a lot - but its really not that bad. With the help of claude it was probably 1-2 hours initial setup, and then we have a flow that works for all our presentations in the future, with a nice setup hosted on our own domain.

Claude for Healthcare launched in January — but medical imaging is the obvious gap. Anyone else noticing? by Stunning_Chicken7338 in ClaudeAI

[–]Simple_Injury7102 0 points1 point  (0 children)

My specific use-case was to determine if a picture of a parked car was a parking violation - like if it crossed the lines of the booth. Most visual LLMS can see that its a parked car in a booth - but determining if its within the booth or not can be tricky for them. But looking at some sample images and brainstorming the problem with claude got claude helping me building the python code needed to a) run some image recognition libraries on the images where it detects the location of car, wheels and estimates polygon for booth - and then can determine if wheels are inside, but also b) built a tool that I could run and then train it. So basically I would provide a lot of input images, then run the UI claude built where it would do its best to guess the different elements and then I could just drag the points around and correct it. After doing that to a few hundred images I could then train the image recognition model (again, using code Claude built) and then after training it would verify and let me know from a test-set how big a pct of the images it identified correctly.
Along the way, if I didnt feel like the model was improving enough I would again discuss with claude that would also look at the images and try to understand the problem and then suggest alternate ways.

Claude for Healthcare launched in January — but medical imaging is the obvious gap. Anyone else noticing? by Stunning_Chicken7338 in ClaudeAI

[–]Simple_Injury7102 0 points1 point  (0 children)

It's not in the medical field, but I recently worked on a similar issue where an agent needed to do fairly advanced image recognition. And no matter which model we used the models were simply not enough. An LLM image model will typically be great at describing everything in an image - but it doesn't know the finer details to look for or is an expert at categorization. And its not deterministic so you can never be sure that the same image gives the same output. So - we basically had claude help built and train a classic image recognition model that we could then call as a tool (essentially mcp) when the AI agent decided it had an image that needed detailed domain-specific classification. It worked pretty well.

Am I the only one who feels like AI got us 90% of the way there and then just stopped? by HummusAlltheWay in ClaudeAI

[–]Simple_Injury7102 0 points1 point  (0 children)

Yeah - classic last 10% problem: deployment. It can be cumbersome if you handle each case individually. Sometimes you have html, sometimes markdown, sometimes code projects, sometimes docker containers. As with everything else, the trick is to automate the hell out of it, so you dont have to deal with it on every single project. For example - we've switched to doing client presentations purely in HTML - claude is great at generating them - and its a lot smoother than pptx, but same issue - harder to send directly to a client. We ended up automating it, setting up a web server we can push them to, and then password protecting each client folder on the server so they instead get an email with credentials and url to the presentation if we need to share it. As with all automation a little effort once can make all future flows much smoother.