-
Rule of least surprise
Rule of Least Surprise says: anything ( some it system in our case) should behave in the way that causes the least surprise to people, users, us. We all love suprises we feel good about… not the biggest fans abotu those bad or negative experiences. Surprise creates confusion, bugs, and lost trust. Prefer predictability over cleverness. Think about it… when you call a function, you expect it to do what it says, not sneak in extra behavior. Silent mutations are a classic trap. Side effects are unknown to the user. Trust me, the user will NOT FIGURE IT OUT. Passing an object and having it changed behind your back. Magic…
-
How to work with GitHub Copilot Limits (Without Fighting Them)
Schedule around them. GitHub Copilot is great (was better, latest updates ruined it) until you hit the quota. Then suddenly your flow breaks and it feels like someone unplugged you from the matrix. Just as you were starting to get productive and claryfing the code. Instead of treating that as a problem, I started treating it as a constraint. Nasty one, ugly one, but hey ! We did work over some worse issues. Don’t fight the limits – schedule around them. Remember to do everything You can to squeeze out as much as possible out of every token. In example : build proper context, descripe properly the plan, be precise,…
-
What is a token in AI ? Prompt examples
What is a token in AI ? – A piece of text, usually a word that we send to the LLM. The same goes for when we get a response ( usually number of words = number of tokens, roughly). How to use it ? Since we pay for it , rather cautiously. We want to send the minimum and get the maximum out of every request. Pretty much the basics of economics. Below are couple of prompts i used to analyze my tokens usage. Something are obsiously hallucinations but on the other hand we get a prety decent breakdown of all the data i did send for that coding…
