Skip to main content
11 events
when toggle format what by license comment
Aug 6 at 6:33 comment added Stanislav Bashkyrtsev I see.. Well, my advice is to try it on a small part of the project. Otherwise you're risking to seriously damage it. This is your 1st attempt at DDD, so you may not fully understand what you're doing. And you don't yet realize that DDD works only for simple projects (github.com/ctapobep/blog/issues/18), and for complex cases it leads to overengineering. My advice is to look at complicated projects that are well structured and written by seasoned engineers (Postgres, Linux) and learn from them. Or better start with algorithms (take Sedgewick course) - they teach to write simple code.
Aug 6 at 1:31 comment added Bernardo Benini Fantin @StanislavBashkyrtsev, the initial reason I started with DDD in frontend was because most code I read was just html+css+some js without much structure. Since this is the most complicated and business-rule-rich project I've ever worked with, DDD seemed like the best design to try in the frontend because of separation and encapsulation of contexts and because it forces you to think in terms (language) of the business.
Aug 5 at 20:53 comment added gidds (This is a classic example of why StackExchange should show tags above the question body: the question is pretty meaningless if you don't know what DDD stands for in this context, and it's long enough that in many cases below-question tags won't even be visible unless/until you scroll…)
Aug 5 at 20:25 comment added Stanislav Bashkyrtsev What makes you think DDD is a good choice here?
Aug 5 at 17:35 vote accept Bernardo Benini Fantin
Aug 5 at 12:52 answer added VoiceOfUnreason timeline score: -1
Aug 5 at 10:53 history became hot network question
Aug 5 at 8:39 review Close votes
Aug 10 at 3:00
Aug 5 at 7:02 answer added Doc Brown timeline score: 1
Aug 5 at 3:17 answer added Greg Burghardt timeline score: 2
Aug 5 at 0:31 history asked Bernardo Benini Fantin CC BY-SA 4.0