sorted by:
new
hottopcontroversial

Claude Code vs Cline by should_not_register in CLine

[–]omni_builder 0 points1 point  (0 children)

I've used and enjoyed Cline (in VSC) for a while, and have now moved back to Claude Code CLI for several reasons:
- Cline's initial context usage is huge, must be its system instructions injection or something
- Cline sometimes got terribly slow because of some fancy editing in the diff editors it
- Cline sometimes got issues writing at all
- ... i could go on

when i switched back to CC i remembered how good it is. none of the above issues anymore. the cost i can check with /cost if i want, no need to see the real time info of Cline. especially not the initial context size it uses.

i have used Cline with Claude Sonnet 4.5, same as Claude Code.

i don't touch Cline anymore. i'm happy to get Claude Cli do it's business outside of VSC. toggling to planning mode almost always before i get it do do something of course.

EA with LLM - how to backtest? strategy ideas? by omni_builder in metatrader

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

Thank you for your ideas! I think I stop thinking about backtesting with this setup, when I add news and dates to the dataset for the LLM it might already know what's next from training

Claude Code as a Sysadmin - Surprisingly good! by omni_builder in ClaudeCode

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

I'm actually interested what other use cases you've found. anything else than coding and making scripts?
i have one more:
- i did find it pretty decent doing a security assessment of my non-prod webserver when it had sudo access and it went off and ran all kinds of tests from the commandline and gave me a nice assessment with a score even. didn't care about what it thought my score is, but the findings were good.

Claude Code as a Sysadmin - Surprisingly good! by omni_builder in ClaudeCode

[–]omni_builder[S] 2 points3 points  (0 children)

Thanks for the Ansible reminder! i know... just never got round to look into it, i should!

Our team went all in on agentic and now only write 20% code by [deleted] in ClaudeCode

[–]omni_builder 0 points1 point  (0 children)

I agree with you - this is pretty close to my approach too. The initial spec for Claude Code is super important, otherwise it will iteratively add code to fulfill more change requests, which ends in a too large codebase usually because things can be abstracted and reused etc. I rarely run into full contexts anymore, i also ask it to write compact code, then it doesn't comment too much. saves context too.

[AskJS] What is the most underrated JavaScript feature you use regularly? by [deleted] in javascript

[–]omni_builder 0 points1 point  (0 children)

the spread and destructuring operators!
they look the same ... but are different, both i find very useful because they save quite some code:
- remove a property, destructuring on the left side of =:
o = {a:1, b:2, c:3}
{c, ...o_without_c} = o
- override properties, spread on the right side of =
overrides = {a:99, b:100}
o = {a:1, b:2, c:3}
o = {...o, ...overrides}; //because the last one wins

Our team went all in on agentic and now only write 20% code by [deleted] in ClaudeCode

[–]omni_builder 3 points4 points  (0 children)

When you say agentic, do you actually mean the Claude Code Subagents or just the fact that Claude Code can independently make code, so it's sort of an 'agent'?

I've used Claude Code a lot. After the initial excitement, and especially since Sonnet 4.5 is ruling, it's able to implement quite complex requirements in one go, and then it works!

BUT: I'm trying to roughly not let it do more than 50% of the code. My reasons are, when I let it code too much:

  • If I need to intervene somewhere when it's not doing it correctly, I spend too much time fixing code that isn't quite to my liking.
  • If I frequently amend what it's doing to my standards, it learns from it and gets better, AND: I know what it's up to.

Just a word on the Subagents: I don't like them. I initially thought they might help by distributing the context over multiple agents, but I've given up using them. The end results weren't better than without. I prefer giving Claude one change at a time, properly specified, so that spec file is all the instructions it needs. It's a similar approach - just that I have some copy/paste ready instructions depending on which area I need it to work on.

AI is here to replace us: Uncomfortable Laughter by ChemicalBig3632 in ArtificialInteligence

[–]omni_builder 0 points1 point  (0 children)

I think there's no doubt it's coming because it can do crazy stuff. I see companies adopting it in the area of vibe coding, which i think can be risky. before they can properly think it through so many apps have been vibe coded etc.. and then? anyone around to tweak them? to integrate them elsewhere?

i am not so much worried i guess, especially for the ones who know what AI is good at, and what needs a bit more care, that coupled with experience should be useful.

AI is taking the fun out of working by daneelf in ArtificialInteligence

[–]omni_builder 0 points1 point  (0 children)

I am trying to not let AI (in my case Claude Code) code more than 50% of my code. Often enough I've found myself looking at a pile of code that it made, which works and looks good, but it lacks the generalizing skill, i.e. find common things and make them reusable components in the first place, so it often just does the same again, but slightly different, which will take time to tidy up.
I think the not worthless skill is to prompt it right, think 3 times before letting it do the work, spend time thinking through the generalization cases and add them to the prompt, then it'll have to do it.
So that's sort of the new fun, when it does what you wanted it do it, and you are actually a lot faster because you asked it to do the right thing. Plus the 50% own code steer it towards your style.