开云体育

I think event modeling is poorly named. Yes these are the main events of the system, but no these won't be the only events. Some events will exist just for the systems sake. It also doesn't capture

Hi JB, It sounds like the New Message I heard c.2013 when Fred George said "microservices are so small you don't need to write tests for them." I asked Fred what he thought was small; "oh, maybe 100

:) Ron Jeffries ronjeffries.com <http://ronjeffries.com/> Everything that needs to be said has already been said. But since no one was listening, everything must be said again. -- Andre Gide

Like Ron, I didn't find much content in that posting, so I went searching and found https://eventmodeling.org/posts/what-is-event-modeling/ It's got more words, but not a lot of clarity. I'm an old

This has the same logic as "Don't do TDD, have lunch instead!" Fortunately, it's not a forced choice. Charlie

I've built event sourced systems, and TDD was very useful, allowing us to evolve our models as our understanding of the business grew, as our software exposed things about the business that had not

Yes, and ... if we were actually perfect designers. the code tells us things about the design. Ron Jeffries ronjeffries.com <http://ronjeffries.com/> Before you contradict an old man, my fair friend,

I agree with Ron. If only we actually knew everything about what the software would have to do to work in the user's reality before we built the software, then designing it right in the first place

It seems to me unlikely that event modeling, even if it were applicable everywhere TDD is applicable, was able to find and correct all the problems that TDD finds and corrects. I think the style of

Hi, folks. Adam Dymitruk wrote this on LinkedIn. https://www.linkedin.com/feed/update/urn:li:activity:6668371835337490432/ I don't like that he framed this as "Don't do TDD; model events,

Hey During interview i explicitly asked: - what should be the output when input array is empty - can input array hold only a particular subset of Ints (like non-negative only) - is input array

There was a function named "updateSubscription" which was used to set a "newSubscription" which was then returned. Inside the very large function was a line which read "validation = isValid(<long list

Massively agree. With legacy tests, I usually try to start with discovery tests - that is, I take my best guess at what the code is doing and write tests to see if I am right. Of course, that

Lately, while helping with some legacy code, I've been finding that my "safe refactorings" aren't quite as safe as I wanted them to be, and that if I had started with the complete test first, I would

wrote:

Anytime I write a test that passes first, I consider: * Was the code so unclear I wasn't sure whether it'd pass? (Often the design--both prod & test--warrants improvement in this case.) Does this test

Hi Steve, I understand the sentiment and I agree with you from a production code perspective, however the interview may be trying to understand if you understand patterns at all, and you're not

Needless to say - if you are on this list and live in israel - you're also welcome to speak on things you're passionate about in the realm of CD/XP. [email protected]> wrote: -- Thanks, Roy

Hey all. If anyone on this list is making their way to Israel soon, i'd love to host you at the CD/XP Israel meetup group. Ping me! -- Thanks, Roy

Steve Gordon wrote on 1/16/20 9:31 AM: You probably didn't want those jobs. :-) Jeff