meaboutsoftware

6 ms·

1. 1.▲
   Show HN: An Introduction to Event Storming and DDD(leanpub.com)

   1 points by meaboutsoftware 1y ago|0 comments
2. 2.▲
   Show HN: The raw truth about self-publishing first technical book(newsletter.fractionalarchitect.io)

   1 points by meaboutsoftware 2y ago|0 comments
3. 3.▲
   by meaboutsoftware 2y ago

   Thanks! That was the idea of the book - no philosophy, just practical stuff
4. 4.▲
   by meaboutsoftware 2y ago

   Thanks for this comment. It is important to consider everything you said. CQRS is part of this book, but it is more of an explanation and might help you at some point (but does not need to). I think that's the main problem of CQRS - it
5. 5.▲
   by meaboutsoftware 2y ago

   Does 10 years count as a recently graduated student? Thanks, I feel very young again! :)
6. 6.▲
   by meaboutsoftware 2y ago

   Thank you Marcin!
7. 7.▲
   by meaboutsoftware 2y ago

   Thank you! This would not have been possible without stopping almost all other work. This is my tip: if you want to write a book, plan unpaid holidays, or stop all consulting/freelancing work. Then, it is not that hard to keep up the t
8. 8.▲
   by meaboutsoftware 2y ago

   Thank you! :) I have similar observations, and over the years, I kept looking for something that would stand the test of time. I still remember horrors related to documenting architecture in Word documents (and requirements in Excel, omg).
9. 9.▲
   by meaboutsoftware 2y ago

   Nice one!
10. 10.▲
    by meaboutsoftware 2y ago

    I partially agree with you- nothing is better than working on "your own" mistakes, but some mistakes often repeat in software architecture. Why not take advantage and not repeat them by learning from others' mistakes? :)
11. 11.▲
    by meaboutsoftware 2y ago

    Thanks for the tip! The book describes the approach that helps prevent my mistakes, and in each "step," I add several warnings and information sections about what to do and what not. I will try to think of how to add a better demo
12. 12.▲
    by meaboutsoftware 2y ago

    Thank you very much! I tried to keep writing daily—sometimes for just 4 hours, sometimes for 13. On average, it was more than 8 hours a day, with some longer (1-week) breaks in between. I will write another post on writing experience in the
13. 13.▲
    by meaboutsoftware 2y ago

    Thanks for your input - the evolution of the architecture is the apple of my eye. The demo part of the book comes from the evolutionary architecture step, which is described on around 100 pages. I hope you will enjoy it!
14. 14.▲
    by meaboutsoftware 2y ago

    Great idea - I already have a repo for the book where I store diagrams. I haven't thought about it. I will move it there. Thank you!
15. 15.▲
    Show HN: I published a book to save you from my software architecture mistakes(leanpub.com)

    100 points by meaboutsoftware 2y ago|33 comments
16. 16.▲
    Technical debt is like using a credit card – we have to pay it off(newsletter.fractionalarchitect.io)

    2 points by meaboutsoftware 2y ago|0 comments
17. 17.▲
    Evolve Your Software Architecture(newsletter.fractionalarchitect.io)

    1 points by meaboutsoftware 2y ago|0 comments
18. 18.▲
    by meaboutsoftware 2y ago

    Totally understandable!
19. 19.▲
    by meaboutsoftware 2y ago

    Each architecture decision record should be added after the decision of the entire team. Then one folk can be assigned to add the ADR to the repo. It will work fine even if you do feature branches (battle-tested but you need to keep you bra
20. 20.▲
    by meaboutsoftware 2y ago

    YYMMDD is also a cool idea! I used it in one of previous projects. What I don't like in your proposal are initials - since 2020 I worked in the environments where all folks were invited in making architectural decisions (that's th
21. 21.▲
    by meaboutsoftware 2y ago

    In case of monorepo where there are several independent deployment units, separating it via dir is quite simple solution. Additionally, if you move the code to some other provider, you move it together with the code (what is not guaranteed
22. 22.▲
    by meaboutsoftware 2y ago

    First answer: if you don't have any ADR yet, start with documenting the first decision that comes - don't go back in time to record 2 YO decisions. Second: I described it as "Considered alternatives". There are 2 schools
23. 23.▲
    Document Your Architecture Decisions with ADRs(newsletter.fractionalarchitect.io)

    10 points by meaboutsoftware 2y ago|12 comments
24. 24.▲
    Evolutionary Architecture by Example (.NET)(github.com)

    1 points by meaboutsoftware 2y ago|0 comments
25. 25.▲
    by meaboutsoftware 3y ago

    In recent years, I have encountered many problems in IT companies caused by incorrect software architecture. What do I mean by incorrect? In most cases, this is one direction – either it is too trivial or incredibly complicated in relation