CTO · I write about engineering leadership, systems, and staying human
(Posts filtered by dev.)
There is definitely not one-size fits all situation here. And there are many perspectives that need alignment
How writing tests for your software can get you closer to being an innovator
A good startup = idea x execution x timing + listening to the customers.
One common pitfall is focusing too much on the idea and not enough on the execution.
The execution needs to be good, yet fast. You cannot afford architecting the "best" system, implementing the "best" code etc.
It's a good idea to take on some tech debt but only if you make sure to take care of it.
It's a delicate balance.
What management thinks a developer does:
What a developer actually does:
I found that developers have two main ways when creating an API do deal with errors and status code
Some gotchas while setting these up together with nginx Alpine and PHP-FPM
Send multiple POST requests with some JSON to test the performance of your app