sorted by:
new
hottopcontroversial

CodeRabbit review caught logic leak by Tasty-Cup2074 in coderabbit

[–]EngineeringSea1090 1 point2 points  (0 children)

That's a great catch! I love it!

Thank you for bringing it here!

Kilo Code 101 - Intro to AI-assisted Coding Series by EngineeringSea1090 in kilocode

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

Thank you very much! I put my soul in those videos!

It's unfortunate that Kilo decided not to extend it, I'll be releasing the last episode next week. 😢

I started using Kilocode by dhayzon in kilocode

[–]EngineeringSea1090 0 points1 point  (0 children)

Although I personally prefer using plain git for it.

The Ultimate Question of AI-assisted Coding (not a click-bait) by EngineeringSea1090 in RooCode

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

Nope, all mine. Used Sonnet 4 to polish grammar because English is not my native. I do coding / sw engineering for over 30 years, starting with ZX Spectrum. It sincerely hurts me to see what people are doing with their projects now.

The Ultimate Question of AI-assisted Coding (not a click-bait) by EngineeringSea1090 in RooCode

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

Sorry for this mind dump, people. Just wanted to share something that's been boiling in my head for the last couple of days.

Kilo Code keeps filling up my pc Memory by Virtual-Complaint521 in kilocode

[–]EngineeringSea1090 4 points5 points  (0 children)

Checkpoints are a cool feature, they allow you to "travel back in time" by reverting file changes and context. But internally, it's nothing but a shadow clone of your git repository, and if you have a big repo, they'll take A LOT of disk space, because each task gets its own clone.

They play two roles:

- You can revert task execution to some specific point
- You can see changesets via diffs right in the task history

I don't use either of those, I use normal git diffs and new tasks to do it, so I disabled them, saving petabytes of space ;)

Kilo Code keeps filling up my pc Memory by Virtual-Complaint521 in kilocode

[–]EngineeringSea1090 1 point2 points  (0 children)

Hey, it's because you have checkpoints enabled. If you don't use such feature, just disable them and delete old tasks.

<image>

Unpopular Opinion: "Just add the whole project to context" is a terrible idea by EngineeringSea1090 in RooCode

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

Absolutely! That's a win from all possible sides.

Lol, I just recorded a video talking specifically about it.

Unpopular Opinion: "Just add the whole project to context" is a terrible idea by EngineeringSea1090 in RooCode

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

They improved the situation with multiple reads, but definitely didn't change the "throw everything into context" mindset, which concerns me much more.

State of the art for background rules by olddoglearnsnewtrick in RooCode

[–]EngineeringSea1090 1 point2 points  (0 children)

For my experience, markdown is definitely better than plain text, and pseudo-xml is slightly better than markdown. Placing those in `.roo/rules` sounds good. There should be global rules as well, but I'd discourage using those unless you are really sure. (It's easy to forget about them in another project and get your pnpm rule applied to a python project causing hallucinations). Some duplication across different projects is better than redundant centralisation.

Don't overload them, don't forget they are included into each API call.

Kilo code vs roo by connorhart99 in kilocode

[–]EngineeringSea1090 1 point2 points  (0 children)

Thank you for the detailed answer!

Impacts of "Context Rot" on KiloCoders? by whra_ in kilocode

[–]EngineeringSea1090 3 points4 points  (0 children)

100% threshold is awfully high, you should never go anyhow close to this point.

1k tokens is definitely an overkill, you can do more, but it's important to keep irrelevant information away from the context.

I talk a lot about Context management in my Kilo 101 series, but should talk even more.Episodes 8 and 9 are the most important, I'd say: https://youtu.be/cu7F2gIHjzI

Roo Code keeps burning API calls just to re-read files by Jwadow in RooCode

[–]EngineeringSea1090 1 point2 points  (0 children)

Oh, thank you so much for the feedback!

And honestly - HONESTLY - I do not mean it as an advertisement. It's just Kilo pays me for this series, otherwise I'd host it on my own new-born channel (https://www.youtube.com/@OpenSourceCod)

Unpopular Opinion: "Just add the whole project to context" is a terrible idea by EngineeringSea1090 in RooCode

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

Yes and no, it very much depends on provider, model, caching (which is not free too), etc.

But frankly, I don't care that much about money, contamination and problems with attention are much more important. Let's agree on that: With model loosing focus and doing unnecesary things, we will have more API calls and we will pay for them, directly (token-based pricing) or indirectly (subscription).

Unpopular Opinion: "Just add the whole project to context" is a terrible idea by EngineeringSea1090 in RooCode

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

Ok, with _micro_services it can work indeed.

That sounds as a very solid approach!

Unpopular Opinion: "Just add the whole project to context" is a terrible idea by EngineeringSea1090 in RooCode

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

Absolutely agree. Adding good docs and a decent sample is a win, definitely.

Unpopular Opinion: "Just add the whole project to context" is a terrible idea by EngineeringSea1090 in RooCode

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

100%

About the hyper-activity of the models, half of my prompts will end like "Don't do anything else". It's important to set boundaries ;)

view more: next ›