A definition of DDD as a software design discipline
A lot of software engineers, including myself, are passionate about code quality. This striving for a well-shaped codebase, while getting things done could cost one quite a few hours and nerves, though. I’m constantly looking for ways to achieve these two goals without significant trade-offs. Stand by for the current state.
Do you really need to create tests? Of course, there are many reasons to do so – improved quality of software, decreased risks while making changes in the code, identifying errors, checking business requirements, improving security…I could go on and on with that. The point is – tests do make a difference.
When radical innovations were rare, businesses could afford to treat application modernization as a sporadic reaction to change. A decade ago, most organizations modernized only when they were compelled to.
However, in the era of open-source and continuous innovation, modernization can’t be an isolated, one-off project. Businesses need to embrace a culture that celebrates change to thrive in the digital age. According to a report by F5, the past year has witnessed 133% growth in application modernization.
As technology becomes more central to peoples’ lives, and to what businesses do, and how they succeed, the ethics of technology must come into sharper focus.
Despite technology becoming a critical part of what enterprizes do, it’s not always clear how to approach and apply technology in an ethical or responsible way.
The Responsible tech playbook is a collection of tools, methods, and frameworks that help you to assess, model and mitigate values and risks of the software you are creating with a special emphasis on the impact of your work on the individual and society.