-
Goodhart’s Law in software development
Every metric that becomes a target looses its value as a metric. The specific phrase “when a measure becomes a target, it ceases to be a good measure” is known as Goodhart’s Law. It originates from British economist Charles Goodhart, and the exact modern phrasing was popularized by anthropologist Marilyn Strathern. Core Ideas of Goodhart’s Law A Practical Way to Think About It Treat metrics as signals, not goals. Use them to start conversations, not to close them. Combine quantitative KPIs with qualitative checks (code reviews, incident deep-dives, customer feedback) so no single number can be gamed without being noticed. Goodhart’s Law exmaples in Business Goodhart’s Law exmaples in Education…
-
Design by contract as self testing code idea by Martin Fowler
Yes, this pattern has names and precedents. Martin Folwer official site. Sits boldly and pains some developers… at the intersection of a few well-known ideas. Helps as and works a “fill in the gaps” kind of approach. Names / related patterns But Hey ! It is “heresy” to put tests in production code? Feels counter‑intuitive only if you equate “tests” with “unit test files that should never ship”. Advocated by people is a yes or not purely based on their experience. If it works for You – go for it ! You can always remove it later. If it helps You in any way, the idea is just. There is…
-
Suno AI template for power metal opera – make AI slop fun
Looking for a Suno AI template ? For power metal opera ? It is a universal example and approach. It is not a guarantee, nothing in the world is… but it can take you quite a bit. It is as always a subject to question. Suno AI is a probabilistic generator, same prompt will produce different results across attempts. The best results usually come from one clear direction: compact, readable prompt with a strong core – genre, clear vocals, defined instruments, a defined mood. Simple narrative structure following well established pattern. In other words, the prompt should sound like a music brief, not a pile of random keywords with best hope behind them. The main warning: contradictions break the prompt This…
-
Configuring my own internet – router on a stick with Netia and MikroTik.
Configuring my own router for internet was pretty… hectic. The whole issue is that ican`t be at two places at the same time. Some of us nerds like to have stuff on cable instead on infitnite packets floating around. Since i am paying for 1gbps i would like to have 1gbps . Even though i do had around 300 mbps on my wifi (v6) it is not the point. It just wasn`t right. My old laptop barely got any signal if i went to my working space. Laptop`s wifi was slower and the signal falloff was drastic, and it got lost from time to time. On my desktop too. Developers…
-
Best Phrases to Test LLM Security Bypass in Red Teaming – jailbreak, overrides, etc
Best Phrases to Test LLM Security Bypass in Red Teaming are not existing. Ever case is different. Try the whole list below 🙂 Here’s a practical red-team list of prompt-injection / jailbreak test cases you can iterate over in your system. Inspired and created after some AWS Red-team security training. These are framed as test prompts to check whether your LLM resists instruction overrides, role confusion, obfuscation, and data-exfiltration attempts. The general categories and examples below align with OWASP-style defenses. Check out the cheatsheet : cheatsheetseries.owasp Remember that different defenses require different attack vector. You can look up repos similar to : https://github.com/langgptai/LLM-Jailbreaks Would recommend running an unbiased uncensored model…
-
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…
-
Where to get data for my machine learning project
Where to get data for my machine learning project is a olot simpler. There are multiple sources You can use freely. Getting good data is usually harder than building the model itself. Without solid data on the input there is no way you wil get any decent answer. The upside of this struggle is that there’s a huge amount of public data out there ready for grabs. On the other hand of you get bad data you end up with something like below…. ( bad data beeing the memory registry … ) Remember that it is up to You to decide if the data is worth anything. Good luck 😉…
-
Improve your AI instruction on the fly …
Improve your AI instruction on the fly is easily doable with a simple set of generic instructions. Start as always with something basic, nothing fancy. Then move forward keeping in mind my favorite principle “First get it work, then make it better“. This will improve your instructions for any llm on its own. Below an example that works for me. Especially when i tell my LLmem that it is a nice soluion, i like it and good job. Instruction example That`s all folks ! Improve your AI instruction on the fly is nothing more then a feedback loop that is computed every time. Remember to keep overall instructions not too…
-
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,…
-
Greek gods in software development
Greek gods in software development can teach us. Ancient wisdom will always stand it`s ground, universally. Beyond time and space. Their domain and virtues stand firm through the ages. Relevant now as those were years ago and will be long after we are gone. Why not ? People define their own set of rules and best practices according to their own taste and work. I envourage You to do the same for Yourself. Then write those down as a proper prompts / instructions for Your AI agents so they will be good little minions. Greek gods in software development – make your own rules ! God Domain Law / Rule…
