Psychology
-
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,…
-
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…
-
Developer vs. Engineer in Software and AI: What’s the Difference?
The terms “developer” and “engineer” are often used interchangeably in tech, but there are meaningful differences in how they approach problems, especially in software and AI. At a high level: Doesn`t matter the title. We are still the part of the same team. In AI, this distinction becomes even more interesting, because AI systems are inherently probabilistic and data-driven, unlike traditional deterministic software. Developer vs. Engineer: Core Mindset Developer Mindset In AI, an AI developer might: Engineer Mindset In AI, an AI engineer might: As one analysis puts it: “Software engineers build deterministic systems with predictable outputs, while AI engineers build systems that are probabilistic and require managing uncertainty.” Key…
-
What is heuristics ? Key Definitions and 10 biased examples people use without any data
What is heuristics ? Fancy word people tend to use but i found not all of them know what is it. Heuristics are simple, practical mental shortcuts that help us to make decisions, solve problems and form judgments. Often without any data or with limited information, little analysis, lack of formal reasoning. Think about a stereoptype. Steoretypes are heruistics. Stereotype -> heuristic i.ex big glasses -> good at math. They’re not guaranteed to be correct or optimal, but they’re fast and usually “good enough” for everyday use. As a species we tent to simplify so we can use as little energy as possible. Double edged sword if You ask me.…
-
First principles methodology in AI by Aristotle – 5 step framework
First principles methodology is the practice of breaking a problem down to its most fundamental truths. What we know to be the absolute truth(s). Then we try reasoning upward to build new solutions with what we know to be the fundament. Instead of copying what’s been done before ( haha, said no developer ever). This methodology goes back to Aristotle, the ancient Greek philosopher who first articulated the idea of reasoning from “first principles.” What Is a First Principle? A first principle is a basic, foundational truth that cannot be deduced from anything else. It’s the bedrock of a problem: In AI, first principles might be: Anything else like framework…
-
How to de clutter You code ( and life)
How to de clutter You code ? Remember the quote “It`s not You , it is me?”. Start with an uncomfortable truth. It is Your mess created by you. Every developer knows this moment. You open a file and wonder who wrote it. Then Git blames shows the true colors. The problem is not just messy code. The problem is how easily clutter sneaks in, in life, in general, everywhere. Why code (and Life) gets cluttered Code rarely becomes chaotic overnight. It grows like a blob ( remember GhostBusters ? ), one “quick fix,” one “temporary solution,” one “I might need this later” at a time. Life follows the same…
-
Psychological safety vs producive stress. How not to go #toxic.
Psychological safety vs producive stress is a conflict of interest. People usually think that much “safety” can lead to laziness ? Don’t rest on your laurels as they say ? On the other stress and some level of danger motivates us to harder work. Workplaces need a certain level of pressure to move forward. Deadlines, feedback, and responsibility all matter. But pressure is not the same as panic, and motivation is not the same as fear. The real challenge is to create an environment where people feel safe enough to speak honestly, while still being stretched enough to grow (or just get exploited and run down the mill?). Safety leads…
-
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…
