Learn AI

The Qirava blog

Articles with voice and rigor on artificial intelligence, software quality, and method. Pick a section and start reading.

Fundamentals

12 articles
Show more · Fundamentals
Fundamentals

What machine learning is for people who do not code

The machine is not thinking. It is tuning thousands of knobs until it gets things right. I will show you how, with an example you can follow in your head.

· 7 min
Fundamentals

The six levels of context in AI: the ladder that decides whether your assistant remembers or improvises

There is no single way to "give context" to a model. There is a ladder with six rungs, from a loose prompt to a vector database. Here I show you which one you need and why climbing too high also has a price.

· 8 min
Fundamentals

The machine that read too much

A large language model knows nothing in the way you know things. And yet something happened when we fed it nearly everything we have ever written. This is the story of what that thing is, with no mysticism and no smoke, and of why predicting the next word turned out to be far deeper than it seemed.

· 6 min
Fundamentals

The vector space: how meaning becomes geometry

Before a machine can search by meaning, someone had to turn words into coordinates. This is the story of how meaning took on shape, direction and distance.

· 7 min
Fundamentals

What is an AI agent and why it is not the same as a chatbot

A chatbot answers. An AI agent pursues a goal: it plans, uses tools, acts in steps and verifies. This is the difference that matters.

· 8 min
Fundamentals

Types of artificial intelligence: narrow, general and the one that does not exist

The AI you use today is a specialist, not a universal genius. Telling the types apart saves you from misplaced fears and inflated expectations.

· 7 min

How it works inside

8 articles
Show more · How it works inside

Prompting and practice

9 articles
Show more · Prompting and practice

Training

1 articles

QA

26 articles
QA

Unit tests: what they are and how to write your first one

The smallest unit of trust in your code. If you cannot test a function in isolation, you probably do not fully understand it either.

· 7 min
QA

The four test levels and why their order matters

Unit, integration, system and acceptance are not the same test in different sizes: each level answers a different risk. Skipping one does not save time, it defers it.

· 8 min
QA

Code coverage: the metric that lies hardest right when you trust it most

80% coverage does not mean 80% tested. You can run every line and verify nothing. Here is what coverage actually measures and why chasing it as a goal backfires.

· 8 min
QA

Exploratory testing: when the script never finds the strange bug

Scripts test what you already imagined. The bugs that hurt live where nobody thought to look, and those are hunted down by a human exploring with judgment.

· 7 min
QA

What software testing really is: the guide that separates signal from noise

Testing is not clicking around until something breaks. It is designing experiments that answer one concrete question: does this do what we promised? Here is the full map, no filler.

· 8 min
QA

What is QA (Quality Assurance) in software, made simple

Quality is not "having no bugs". It is having a way to know, before you ship, whether the software does what you promised. That is QA, and it is not the same as testing at the end.

· 7 min
Show more · QA
QA

ISO/IEC 25010: the map of what “quality software” actually means

When someone says “quality” without defining it, arguing is pointless. ISO 25010 gives names to the eight characteristics you can actually demand and measure in a product.

· 8 min
QA

Functional vs non functional testing: what each one measures

A button working is functional. That button holding up under 5,000 simultaneous users is non functional. A product can pass every functional check and still be unusable in production.

· 7 min
QA

Integration testing: when the parts pass alone but fail together

Every module passes its unit tests and the system still breaks. The bug lives in the seam between components, and only integration testing catches it there.

· 8 min
QA

Performance testing: load, stress and spikes explained

It works perfectly with three users. The question is what happens on launch day with thirty thousand. You do not guess that: you measure it.

· 7 min
QA

How to report a bug the developer will actually want to fix

"It doesn't work" is not a report, it's a complaint. A good defect report is reproducible, states expected versus actual, and cuts the fix time in half.

· 7 min
QA

Verification vs validation: the question almost nobody knows how to answer

'Are we building the product right?' and 'are we building the right product?' are two different questions. Confusing them is why so many teams pass every test and still fail.

· 8 min
QA

The life of a bug: from 'new' to 'closed' without losing it along the way

A defect is not fixed, it is managed. New, assigned, resolved, verified, reopened: each state exists for a reason, and skipping them is how 'fixed' bugs come back.

· 7 min
QA

QA vs testing vs quality control: they are not the same

People use them as synonyms, but they are not. QA is the process that prevents, testing is the activity that verifies, and QC is the inspection that detects. Mixing them up leads you to hire wrong and measure worse.

· 8 min
QA

What ISTQB Is and Whether the Certification Is Worth It for Testers

It is the de facto standard for talking about testing with a shared vocabulary. It will not make you a good tester, but it gives you the language the industry speaks.

· 8 min
QA

The testing pyramid: why not everything should be E2E

Many teams have the pyramid upside down: mountains of slow, brittle E2E tests and almost no unit tests. The result is a suite that takes hours and that nobody trusts.

· 8 min
QA

Line, branch and condition coverage: they are not all worth the same

Covering lines is easy and deceptive. Covering branches and conditions is where the real bugs hide. The technical difference that changes how much you trust your number.

· 9 min
QA

Test case, scenario and script: three things that are not the same

Sloppy vocabulary breeds sloppy suites. Telling case, scenario and automation script apart is what keeps your suite readable a year from now.

· 7 min
QA

End-to-end (E2E) tests: exercising the user’s entire journey

They mimic a real person doing the task from start to finish. They are the most realistic and the most expensive to maintain, which is exactly why they should not be the majority.

· 7 min
QA

Regression testing: making sure fixing A does not break B

The most innocent change revives a bug you thought was dead. Regression testing is the safety net that warns you when the past breaks again.

· 8 min
QA

Severity vs priority: why a critical bug can wait

Severity is how much it hurts; priority is when you fix it. Confusing the two makes teams put out small fires while the house burns down. Here is the matrix that sorts it out.

· 8 min
QA

Black box vs white box: two ways of looking at the same code

One tests what the software does; the other tests how it does it. They do not compete: they complete each other. Picking just one leaves you with half the risk map.

· 8 min
QA

Smoke testing: does the build even power on?

Before you test in depth, make sure the build is not dead on arrival. Five minutes of smoke testing save hours spent on something that never boots.

· 6 min
QA

How to design test cases that actually catch bugs

Equivalence classes, boundary values, decision tables: techniques that turn 'what do I test?' into a repeatable method instead of intuition that runs dry.

· 9 min
QA

The test plan: the document almost nobody reads and everybody needs

A test plan is not bureaucracy: it is the written answer to what you will test, what you will not, the criterion that tells you to stop and the risk you accept. Without it, you test blind.

· 7 min
QA

Acceptance testing (UAT): when the decider is not the tester

Code can pass everything and still not be acceptable. UAT is the moment when the business, not QA, says 'this works'. And it is almost always done badly.

· 8 min

Method

8 articles
Method

Human in the loop: why the best AI keeps people inside

Human in the loop is not distrust of AI. It is designing when it decides alone and when a person reviews, so the result gains value without losing control.

· 8 min
Method

What an AI workflow is and how to build one

An AI workflow is not a loose chat: it is a chain of steps where the model does some and people do others. Here is how you build it.

· 8 min
Method

How to run an AI company with governed agents

How to run an AI company with governed agents: strategy from the chat, execution by a swarm, governance that lends judgment.

· 8 min
Method

Deliberating without faking execution: governing agents under SDD

An agent that proposes is not an agent that did. Confusing the two is what fills your systems with work that looks finished but is not. Here I show you the exact line.

· 8 min
Method

What Spec-Driven Development Is (and Why We Left Vibe Coding Behind)

You asked the AI to "see what comes out" and something came out. The problem is not what came out: it is that nobody wrote down what should have come out. The spec fixes that, not the prompt.

· 8 min
Method

The Qirava factory: roles, skills and maturity gates (G0 to G3)

A lone agent improvises. A factory does not. Here I show you how a line of governed agents is organized: each role with its own package of skills, and nothing moves forward without clearing its gate.

· 7 min
Show more · Method

Costs and business

6 articles

Ethics and bias

6 articles

History

2 articles