Practical DDD in TypeScript: Factory
<p>Some software developers provide a bunch of superfast code, destroying the scrum board. The two-week-long sprints start on Wednesday, and by Friday morning they already finished all their tasks.</p>
<p>I’ve seen this multiple times. And each team needs at least one such girl or a guy to be able to do things quickly. Unfortunately, many struggle with code quality, which sometimes hides potential bugs.</p>
<pre>
Other articles from DDD series
1. <a href="https://medium.com/javascript-in-plain-english/practical-ddd-in-typescript-why-is-it-important-ac3ba03afbdd" rel="noopener"><strong>Practical DDD in TypeScript: Why Is It Important?</strong></a>
2. <a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-value-object-b76bcd2d9283" rel="noopener ugc nofollow" target="_blank"><strong>Practical DDD in TypeScript: Value Object</strong></a>
3. <a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-entity-fc79002d0015" rel="noopener ugc nofollow" target="_blank"><strong>Practical DDD in TypeScript: Entity</strong></a>
4. <a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-domain-service-8c32afefb102" rel="noopener ugc nofollow" target="_blank"><strong>Practical DDD in TypeScript: Domain Service</strong></a>
5. <a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-domain-event-dda7076385df" rel="noopener ugc nofollow" target="_blank"><strong>Practical DDD in TypeScript: Domain Event</strong></a>
6. <a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-module-21df3e6989d0" rel="noopener ugc nofollow" target="_blank"><strong>Practical DDD in TypeScript: Module</strong></a>
7. <a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-aggregate-fd47a6631865" rel="noopener ugc nofollow" target="_blank"><strong>Practical DDD in TypeScript: Aggregate</strong></a></pre>
<h2><a href="https://blog.ompluscator.com/golang-blogs-875ab3bda75?source=post_page-----10bea4cfc8fe--------------------------------" rel="noopener ugc nofollow" target="_blank">Golang Blogs</a></h2>
<h3><a href="https://blog.ompluscator.com/golang-blogs-875ab3bda75?source=post_page-----10bea4cfc8fe--------------------------------" rel="noopener ugc nofollow" target="_blank">Here you can find all Golang Blogs done by me.</a></h3>
<p><a href="https://blog.ompluscator.com/golang-blogs-875ab3bda75?source=post_page-----10bea4cfc8fe--------------------------------" rel="noopener ugc nofollow" target="_blank">blog.ompluscator.com</a></p>
<p>I know that. I was one of those “guilty” ones. Providing tonnes of code, but poor quality. Logic spread in many places, abnormal classes and methods, code difficult to unit test, and bugs constantly coming.</p>
<p>Luckily, one summer I spent some serious time reading probably the most important book in my career — <a href="https://www.amazon.de/-/en/Robert-Martin/dp/0132350882" rel="noopener ugc nofollow" target="_blank">Clean Code</a>. Consequences? Same pace of coding, but <a href="https://www.tripscovery.io/" rel="noopener ugc nofollow" target="_blank">production</a> code which still has zero bugs, even after 5 years.</p>
<p><a href="https://javascript.plainenglish.io/practical-ddd-in-typescript-factory-10bea4cfc8fe">Visit Now</a></p>