We have a project, and to make it easier, we use specific standards. E.g., we use spaces in every file.
But sometimes, we get to a situation when these standards are stressful. We don’t understand them and just want them to bend over. How does our short-term need for pleasure affects long-term well-being of the project?
How designing for business opportunities and the rate of change may give you better contexts.
Flaky tests are automated tests that are non-deterministic. That means they may pass or fail when executed against the same build artifact or deployed system.
If you’ve ever retried the execution of a failed test run in your CI/CD pipeline tool without any code or config changes in order to get a failing test case to pass, that’s an indicator that you have a flaky test case.
Serverless adoption brings promises to many organizations! Promises of cost efficiency, engineering efficiency, and business efficiency. However, serverless is not a technology that, once successfully adopted, can be left unattended to rust.
The motivation to adopt serverless should never be to get the job done and never look back. If you adopt it with this attitude you will inevitably get into the legacy migration juggernaut that will haunt you much sooner than you anticipated.