-
Dealing with github copilot errors
Dealing with github copilot errors is pretty irritating. Especially when dosing some more complex stuff and suddenly “Bam”. Red message. Easiest thing to do ? Switching the model family often works because some models have different capacity pools or stricter preview limits. GitHub documents vaguely that if you are rate limited, you can wait and try again. Just type “continue” and keep your fingers crossed. Otherwise check usage patterns, change the model, or contact support. Common github copilot errors Some run of the mill You probably know already, just put them together as a ‘review’ : Why changing the model helps ? Changing from one model family (vendor) to another…
-
Structure for instructions, agents and skills
This all is the provide a nice clean idea on how to store your files so You can make Your AI assistant / LLM network understand what and how to do. Acording to Your more or less strict rules. This should help You to achieve more repeatable results as expected. The problem : generic answer Do not confuse with generic functions, those rock ! Out-of-the-box, any LLM (here copilot) creates generic code. You could call it ‘vanilla’ flavour. It doesn’t know your conventions, library preferences patterns / anti patterns. This results in something that might work but is hard to maintain, totally different then the rest of the lot and…
-
How to reduce github copilot`s premium requests usage and maximize efficiency
How to reduce github copilots premium requests usage and maximize efficiency ? Make a plan, a kaizen plan at best. Instruct precisely, cover edge cases, allow all tools to execute and pray the LLM will understand You. Want to share my simple methodology that not only can save money but also ease in and smoothen out the workflow. RTFM ! As always You could benefit from RTFM ! Reading the foqing / friendly / flopsy manual. I know You never read it cause real man don`t do it ( how about real woman ? ) ? God knows if gamers would not have to go through the tutorial, they would…
-
Statics VS AI code analysis ~13 tools
Statics VS AI code analysis works best using the pros from both words. Go hybrid ! Static tools understand the syntext, hardcoded parameters and are very strict. On the other hand AI understands context, can figure out business logic, adapt the codebase. Logic flaws or performance bottlenecks rule-based scanners might miss, AI will put more effort into that. Static analysis limits Static tools scan for syntax errors, style violations, and basic security patterns using fixed rules. Always consistenst, very fast but might generate false positives, ignore business logic, and require manual rule overrides. How often did You use @typescript-error 🙂 Do You code for the linter to pass, logic to…
