DDD/CQRS Made my daily tasks boring

[Alexander Pletnev]

Good day everyone.

Im full-stack web developer. Im writing some kind of software for
Sport Science.

At that moment when project started, obviously I was less experienced
that today. I did not know DDD patterns, Layered Architecture, and
other good software practices.

I had no any Code Review from mentors or someone. But App has been
needed for new features and code base grew fast. Happily I was using
TDD approach almost everywhere and on one moment TDD started to
show me drawbacks of ways I was using. Like coupling with Framework,
messing different layers (there was not any layers yet) =) , etc.

And in one moment I decided implement Layered Architecture and DDD
way. Not full rewrite, but just in a way "All new features writes with
new approaches". "Old features if they need BIG changes, do full
rewrite with new approach". And it started working for me.

Code became much managable, cleaner, less coupled and easier to
understand (sure if you anderstand layers and ddd).

But today I feel very boring with my day-to-day tasks. I feel that Im
doing the same things every day. I have nothing new. New features now
looks for me: derive correct names for components, place them into
right layers, code them, release thing. I have no WOW-effect in my
every day tasks.

So the question is: What to do? I want to continue build my project,
it bring really good things for its users. But it's now boring.

Thanks

[Colin Yates]

Assuming you are being humorously sarcastic :-), some good yak shaving exercises you can sink months into:

- evaluate and decide upon one of the off-the-shelf emacs configuration bundles (prelude is my favourite)
- now build your own emacs theme
- convert your code base to a literate format
- evaluate and choose a _unit_ testing framework, now decide to write your own, now chose a different one
- reformat your computer to tidy it up (equivalent to a big rewrite)
- did I mention emacs?
- decided to ‘make consistent’ all your JSON keys - then decide to change the capitalisation to sentence-case, now realise the horror and go back
- 2 or 4 spaces? Really? Sure?
- package by component, tier or ‘things that change together’
- repeat the same process for unit tests but now for BDD
- DAOs or SQL (linq) in the Controllers?

And of course, there is always the ‘SQL or Document database?’

Finally, if you really are twiddling your thumbs, go make sure all your sequence diagrams are up to date.

If you weren’t being humorous then I have nothing more to say :-).

> --
> You received this message because you are subscribed to the Google Groups "DDD/CQRS" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dddcqrs+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Kijana Woodard]

After getting emacs straightened out, realize that writing the code was never the interesting part. It only seemed interesting because it was new. 

The real fun is in solving problems. Especially if you're doing ddd, 90% of the excitement is before the "derive correct names for components" phase.

[goto theant]

Brilliant Colin :-)
Thank you

[goto theant]

Made me want to look at emacs !!!;-)