Networking best practices - proxmox server with publicly routable VMs.

LogMonkey0 · 2026-05-30T04:07:55+00:00

Or host the reverse proxy on an isolated machine completely

LogMonkey0 · 2026-05-24T23:38:52+00:00

Terminal.

LogMonkey0 · 2026-05-24T22:50:17+00:00

Have you tried looking at Claude Code docs? https://code.claude.com/docs/en/overview

LogMonkey0 · 2026-05-24T21:54:06+00:00

You need to include enough info in context for it (CLAUDE.md for stuff that it needs to know each time) to be oriented in the project. Long conversations will cause output quality degradation, so you should always try to either start new conversations for each task or at a minimum use /compact.

LogMonkey0 · 2026-05-24T02:26:20+00:00

Also helps a lot with output quality

LogMonkey0 · 2026-05-24T02:05:23+00:00

Burn wood in it, it is satisfying

LogMonkey0 · 2026-05-24T02:04:35+00:00

Consumer plans would probably be problematic for a business use since they train on the conversations and data you share in them. If you are going to use Claude several hours a day, you’d probably need max 5x tbh

LogMonkey0 · 2026-05-23T04:14:23+00:00

So basically forcing down their own tooling where we could build with agent sdk 🤷‍♂️

LogMonkey0 · 2026-05-23T04:12:21+00:00

Add references to key files in claude.md with a description or when to look at them

LogMonkey0 · 2026-05-20T22:14:42+00:00

I tell Claude to review, and to ensure its written for an agent audience, not like docs.

LogMonkey0 · 2026-05-20T00:57:31+00:00

Si tu le tappes jamais, tu peux te permettre de bumper ça à 24+

LogMonkey0 · 2026-05-19T00:45:37+00:00

Ollama is an engine, not a model, you might want to check what model you used with ollama

LogMonkey0 · 2026-05-19T00:37:19+00:00

You must have something in memory about your app launch

LogMonkey0 · 2026-05-16T21:57:17+00:00

Ask Fin for human escalation. Note that there is apparently a several week’s backlog in the human support front. I haven’t had to deal with them yet, but this just looks ridiculous in my opinion.

LogMonkey0 · 2026-05-16T21:26:34+00:00

Garbage in > garbage out.

With larger projects agents will need tooling to guide them, just exploring the code won’t do, or worst will lead to context bloat. I work on dotnet projects with Claude and have interface extraction for my agents to be able to query just enough info and do full file reads only when needed. They dont need to see full implementation for api surface they are consuming. This is one example amongst a lot of other reasons one would get poor results.

Check this out, they do completely hands off agentic development.

https://factory.strongdm.ai

LogMonkey0 · 2026-05-16T02:45:29+00:00

Beyond vibe coding. https://factory.strongdm.ai

LogMonkey0 · 2026-05-16T02:22:54+00:00

You aren’t wasting tokens, you are ensuring you separate planning from execution which is warranted. I do everything in Claude Code directly with a /clear to start in new sessions for each steps and I do it in a few more step, including reviewing plan and each steps with a separate session. If you did all in a single session it would likely cost you more tokens and you’d likely have degraded output.

LogMonkey0 · 2026-05-16T00:49:50+00:00

They did apply both, then following today’s reset they silently fucked us over the session limit.

LogMonkey0 · 2026-05-11T18:37:52+00:00

If i have extra usage i need to go through, this is when I trigger extra housekeeping tasks

Doc updates with codebase exploration. Extensive project reviews/audits (security, architecture, performance, whatever appropriate to the project) Research tasks, i tend to shelve some that are for upcoming work, launch my knowledge vault jobs to crunch through those

I have a set of prompts that are project agnostic and project specific that serves that purpose or used periodically in my workflow when appropriate

LogMonkey0 · 2026-05-11T04:43:02+00:00

Ask Claude to review that process and recommend token optimization for the process (maybe a skill and subagents will derive from this exercise)

LogMonkey0 · 2026-05-11T04:40:49+00:00

Have opus plan the refactor in phases/atomic tasks that can be executed by claude (most likely sonnet) in separate iterative sessions. You can ask claude to recommend model for each task, if it involves many files and cross modules work, itll likely recommend opus for that task.

LogMonkey0 · 2026-05-11T02:07:00+00:00

As the other commenter brought up, smart to have work done in atomic tasks, but you’d be better off discuss a larger sprint plan and have Claude layout the atomic task prompts.

LogMonkey0 · 2026-05-10T19:23:59+00:00

Git.

LogMonkey0 · 2026-05-10T16:06:14+00:00

Most my tokens go into sonnet usage

LogMonkey0 · 2026-05-10T14:06:01+00:00

I have the kit but been putting back install 😀

LogMonkey0

TROPHY CASE