Credit Unions exist, though.
Credit Unions exist, though.
With only 2 developers, CI/CD can be your best friend. Automate the daylights out of testing your code.
Remember to tag your regression tests in some way - any test that is preventing a production bug that actually happened needs to be marked as a ‘regression’ and treated as high priority to keep passing.
Treat all others tests as more art than science. Keep the reliable ones, toss out the brittle ones.
Look for a network traffic recording/replay library for your toolchain. Reusing integration tests as unit tests is a huge time savings.
If you have live data access, build yourself a few charts that represent a typical day. Knowing what “normal” looks like in your database can be priceless on a weird day.
That makes me so happy.
Rarely. Require linear history for the win.
Heh. Thoughtful post. But yeah. Income is a leading indicator of ability to build wealth. And rainfall is a leading indicator of whether the ground will be wet.