Software development quotes
Before giving any feedback, it’s important to understand that every relationship is two-sided. If you’re having interpersonal issues while working with someone, it’s just as much on you as it is on them to change, in order to get to a better working relationship.
Since 2006 the era of “Everything as a service” has advanced quickly. Cloud computing is dominant. Infrastructure as a service is now standard, as are Platform and Software as a service. Function (also known as Serverless) is about to be the next big thing. AI is potentially the next elephant …
Migrations matter because they are usually the only available avenue to make meaningful progress on technical debt.
Healthy, high-performing teams decide how they are organized, how they work, and what tools and processes they use. To do this, they need to be held accountable for the value and quality of results they deliver, not micro-managed on how to get those results.
The reoccurring question for all Product Owners is: What should be built? It occurs in sprint planning: What should be built this sprint? It occurs in thinking about the near future: What should be built next? And it occurs when thinking further out: What should be built next year?
The golden rules of Test-Driven Development (TDD) are: Don’t write source code until a test requires it Reference new classes, methods, variables etc in your test first, so the code won’t compile, and then fix it by declaring them Aim to have just one thing broken at a time if …
