Weekly newsletter about leadership, technology, books and anything else we felt compelled to share with others
Year 3 - Edition 35
A Fistful of Links is a weekly newsletter about leadership, technology, books, and anything else we felt compelled to share with others, brought to you by Og Maciel and Mirek Długosz.
How to Test Anything
By James Thomas
Sometimes you’re asked to start testing in a context that is not ideal: you’ve only just joined the project, the test environment is broken, the product is migrating to a new stack, the developer has left, no-one seems quite sure what’s being done or why, and there is not much time.
Knowing where to begin and what to focus on can be difficult and so in this talk I’ll describe how I try to meet that challenge.
What if you need to investigate a new technical field right now, let’s say this week, to proceed with the project at hand? (…) In this article, I will share my approach to a quick technical investigation. I apply it to new technologies and any other unknowns as they appear in my daily tasks.
The main idea behind benchmarking or profiling is to figure out how fast your code executes and where the bottlenecks are. The main reason to do this sort of thing is for optimization. You will run into situations where you need your code to run faster because your business needs have changed. When this happens, you will need to figure out which parts of your code are slowing it down.