AI
-
Markmap vs Mermaid for Spec-Driven Development (SDD)
Markmap vs Mermaid for Spec-Driven Development You will consider sooner or later. When You have to go „full on AI” documentation stops being a nice-to-have and becomes a must be part of the product. We need to convey a lot of information, with hopefully as little text as possible so we can easily read it and digest the information. Two popular options for Markdown documentation features are Markmap and Mermaid. They solve different problems, and the best choice depends on whether you want fast idea mapping or more structured diagrams for flows. When to use Markmap Markmap turns Markdown headings and bullet points into an interactive mind map. Useful for…
-
Jevons paradox in AI workplace
Jevons paradox in AI workplace Jevons paradox in AI workplace is introduced at work with a simple promise: do more in less time. In practice, the result are messy and stack the work. Jevons paradox is the idea that when something becomes more efficient, people and organizations often end up using more of it. In the AI workplace that can mean faster tools, automated work that do not always reduce workload. They can also expand expectations, volume, and ambition to utilize the improved (AIed ?) processes. Be aware At first glance, this sounds contradictory and just wrong. If a team can draft emails, summarize meetings, and generate reports in minutes,…
-
Need to know old boy. Principle of Minimum Access for LLMs
Principle of Minimum Access for LLMs can be described by Timothy Dalton as James Bond in „The Living daylights”. Bond says the phrase “Sorry old boy, section 26, paragraph 5, need to know.” to a fellow agent and drives off escorting a VIP – very important target. Behind the scene is a practical idea that fits modern AI systems very well: an LLM or agent (as in the movie) should only be given the minimum access it needs to do its job. Not more, not less. Bare minimum. Of course Mythos probably could jailbreak anyway but still… controll is the best form of trust ? This is not just a…
-
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…
-
Protect your work with poison ?
Protect your work with poison ? Is there no other way around. Robots.txt ? Nobody cares. Copyrights ? LOL. Fair use policy ? As long as i don`t get caught. Protect your work with poison is the oldest trick in the book, especially by plants. Most of them have to be cooked, to be eaten and digested with benefit for us. Why not doing it with our work ?I am thinking about healthy amount of protecting our work. Does it mean anyone making a rembrandt style photo should pay the author of that style ? For 70 years ? How much and how long ? Why money at all ?…
-
Yet another basic AI glossary part 1
AI & Machine Learning Glossary for Beginners Yet another basic AI glossary part 1. This is base what i need to learn better and understand all that „AI” and „LLMs”. Feel free to go through all of it and dive deeper on those subjects. Defining here ai concepts, ideas, math functions, slang and anything that might be helpful in better understanding „the whole lot”. 1. Logit A logit is the raw output we get from a model before any functions are applied. Before the softmax functions. During classification logit shows the confidence of the model about everypossible output. 2. Logit Definition (Mathematical View) In math logits are real numbers output…
-
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…
-
Deeplearning.ai text-embedding model error. Change to text-embedding-005
Deeplearning.ai text-embedding model error for „textembedding-gecko@001” requires You to simply change it to another one. Instead of the original pretrained models we should use the newer ones. Those models are succeeding the gecko series in Vertex AI. Google Vertex AI Options OpenAI Options Those are just some of the available models. Usage Comparison Model Provider Dims Max Tokens Best For text-embedding-005 Google 768 2048 English/code gemini-embedding-001 Google 3072 Varies High quality text-embedding-3-small OpenAI 1536 8191 General/RAG Summary Once upon a time, and still we can find many many things thanks to start overflow and people willing to share knowledge… let us hope the next time you google something…
-
Productive struggle vs AI slop
Productive struggle vs AI slop is quite the topic these days. On one hand we have to do the hard, boring, frustrating work. Do it long enough to learn the whole lot, reshape skills, gain confidence. Opposition of escaping to quick fixes with or without AI. When used in conjuction with AI, we should still keep the struggle but without the pointless friction. That way more energy and cognitive power goes into craft and progress, long-term growth… instead of refactoring some legacy code and working over things that should not be that hard in the first place. What is productive struggle? Productive struggle is the time and space where a…
-
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…
