/explore
|
You are here 
|
nickhayden.com | ||
| | | | |
venam.net
We're used, as software engineers to try to make things perfect, to see things from above, to think we're great architects and creators. What's more important though is to create software that does an important job for someone. What are the best ways to create such software? |
|
| | | | | ||
| | | | |
rachelcarmena.github.io
Trying to explain DDD easily |
|
| | | | | ||
| | | | |
blog.gougousis.net
[AI summary] A developer provides a critical re-reading of Domain-Driven Design, contrasting tactical patterns with the strategic importance of domain modeling, ubiquitous language, bounded contexts, domain events, and aggregates. |
|
| | | | | ||
| | | | |
www.softdevtube.com
Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and |
|
| | | |||
