The concept of B2D is that we're not treating developers as Consumers nor Businesses that much. We treat them as Developers.

This has an impact on the planned work on the CRM. The CRM will probably be more like DRM or DevCRM.

In the first spikes/explorations I will focus on modelling Arkency business processes, but the goal is to extract reusable domains, which can be applied in other projects too.


*****
Find more:

➡ Andrzej Krzywda on Twitter: https://twitter.com/andrzejkrzywda
➡ Andrzej Krzywda on Instagram: https://www.instagram.com/andrzejkrzywda/
📖 Domain-Driven Rails: https://blog.arkency.com/domain-driven-rails/
📖 Fearless Refactoring: Rails Controllers https://rails-refactoring.com/
📖 Frontend-friendly Rails: https://blog.arkency.com/frontend-friendly-rails/
📖 React.js by Example: https://reactkungfu.com/react-by-example/
📖 Rails Meets React.js: https://blog.arkency.com/rails-react/
📖 Asnyc Remote: https://blog.arkency.com/async-remote/
📖 Responsible Rails: Trustworthy Developers: https://blog.arkency.com/responsible-rails/
📖 Blogging for Busy Programmers: https://blog.arkency.com/blogging/
➡ Arkency Website: https://arkency.com/
➡ Arkency Blog: https://blog.arkency.com/
➡ Arkency on Twitter: https://twitter.com/arkency
➡ Arkency on Facebook: https://www.facebook.com/arkency.com
➡ Arkency on LinkedIn: https://www.linkedin.com/company/arkency/