I haven’t really set goals since 2022. I set themes instead. 2025 was about exploration. Saying yes to things I would normally avoid. Doing at least one thing every month that I’d usually say no t...

Reframe your testing from fixing bugs to understanding systems through small, deliberate habits that shape how you think and decide.

Impact statements describe the outcome of your work rather than the task you performed. Instead of listing what you did, they show what changed because you did it. They make your contribution clear, measurable, and easy for others to understand.Example: Task: Created API test suite Impact statement: Improved release confidence by reducing post-deployment API failures

The STAR model is a simple structure for explaining real experiences. It helps you tell a clear, focused story by breaking it into four parts:  Situation – The context or problem you were facing Task – What you were responsible for Action – What you actually did  Result – What changed because of it  Example:  Situation: A regression cycle kept slipping because no one trusted the test results.  Task: Improve the reliability of the suite.  Action: Identified the top flaky tests, stabilised them, and moved the suite into CI.  Result: The team cut regression time by half and stopped rechecking everything manually.

Build a test-first onboarding path that strengthens new testers’ observation, questioning, and risk-finding skills

Solve stubborn bugs faster by breaking things on purpose, questioning your assumptions, and thinking your way to clarity.

A command-line search tool that finds patterns in text — short for Global Regular Expression Print. In simple terms: it hunts through files and tells you where the thing you’re looking for is hiding.

A debugging technique where you explain your code (and your confusion) out loud — often to an object, like a rubber duck. The magic: saying the problem forces your brain to slow down and reprocess the logic, and half the time you’ll spot the issue before the duck even blinks. How it works:  Pick your “listener” — a duck, a plant, a coffee mug, or a colleague who can tolerate monologues. I have a lot of friends on my table to listen to me, my fav - sleeping Pikachu.  Walk through your code line by line, explaining what it’s supposed to do.  Wait for the moment you realize what it’s actually doing.  Why it works: Turning thought into speech forces clarity. You can’t gloss over details when you have to articulate them — even to plastic.

A distributed version control system that helps you track changes, collaborate without overwriting each other’s work, and recover from “oops” moments and make them "aha" moments. Think of it as a timeline of every decision your codebase has ever made - the good, the bad, and the experimental.Common commands:  git clone <repo-url> – Makes a local copy of a remote repository. Basically, downloads the project (and all its history) onto your machine.  git status – Tells you what’s changed since your last commit. Great for confirming if you’re in control or if chaos has already begun.  git add . – Stages all modified files for commit. You’re telling Git, “These changes matter — track them.”  git commit -m "message" – Saves a snapshot of your changes. The message is your future debugging diary — write something meaningful.  git push – Sends your commits to a remote repository (like GitHub). The part where you finally share your brilliance — or your broken code.  git pull – Fetches and merges the latest changes from the remote. Always do this before pushing, unless you enjoy merge conflicts.  git log – Shows commit history. Great for tracing when that one bug was born.  What's the git command that you learnt the hard way?

Doing this certification was cool, haha!! I'm Software Testing Essentials Certified (STEC) !! Thanks guys, for creating an opportunity to contribute to this certificate. Got to know a lot of "ho...