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.
Here is our monthly selection of knowledge on programming, software testing and project management. This month you will find some interesting information and opinions about women in Agile, Domain-Driven-Design, Scrum sprint planning, technical debt, Java integration testing, managing software development, software design, testing Javascript.
When I relocated as a software developer to San Francisco in 2011, I didn’t know much about mental health. My solid background in computer science didn’t prepare me to fend off the depression and the burnout that unfortunately affected both my personal and professional life for several years. I learned …
Are you dreading an email from work while you follow this presentation? Ruminating over last week’s outage? Worried you are not learning enough because you cannot stay focused on the talks? These are three kinds of suffering we all experience at work: uncertainty, failure, and insufficiency.
As software developers, we are asked to absorb even more information than ever before. More APIs, more documentation, more patterns, more layers of abstraction. Now Twitter and Facebook compete with Email and Texts for our attention, keeping us up-to-date on our friends’ dietary details and movie attendance second-by-second.
Have you ever worked as a software developer on a legacy project, like lots of source code, but no unit tests? Or no continuous delivery? Static code analysis completely missing, or even a simple code standard totally absent? Projects like these are still more often the case than we like …
