Writing on Testing
Articles on Testing from Tauseef Fayyaz: practical writing on engineering, AI and tech careers, drawn from leading a team and mentoring engineers.
27
Articles90K+
Readers on LinkedInPosts tagged testing
5 posts tagged “testing”
The Defaults I Would Learn First as a Software Engineer
Every roadmap for learning software engineering is the same technology list in a different order, and it tells you nothing about what to do when you are sitting in front of an unclear requirement on a Wednesday afternoon. Fourteen situations you will keep meeting, paired with the move that is usually right, from prototyping a vague requirement to blaming the system rather than the person.
Five Kinds of API Test and When Each One Earns Its Place
Two engineers can both say the API is tested, both be telling the truth, and still disagree about whether it is ready. Functional, integration, regression, load and security testing, what each one catches, what each one structurally misses, how to spread your effort between them, and the one minute authorisation check that finds the most common serious API vulnerability.
Six Rules That Keep a Codebase Worth Working In
Every one of these gets quoted as an acronym in code review, usually by somebody who read the expansion and not the reasoning, and applied without judgement they produce worse code than if nobody had heard of them. Separation of concerns, DRY, KISS, YAGNI, test driven design and writing for the next reader, each with the thing it protects against and the way it goes wrong.
What Actually Happens Between Your Pull Request and Production
Most engineers learn CI/CD as a sequence of buttons rather than a system, which works right up until the pipeline goes red and nobody knows which stage failed or why it matters. The five stages walked through one at a time, what each is protecting you from, why builds pin their versions, the difference between rolling, blue green and canary releases, and the ten second skill of reading a failed stage.
The Fundamentals Worth Learning as a Software Engineer
Frameworks are the fastest moving and least valuable part of what you know. This is the layer underneath: how a computer runs your code, data structures as trade offs, complexity at conversational depth, storage, networks, concurrency, version control, testing as a design tool, and the two skills engineers skip that decide how far they get.
Browse writing by topic
Every tag has its own page.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Every session is free; a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com
Follow along
New writing, resources and project ideas land here first.