Conversation

I had an informal expertise extraction conversation yesterday, with a senior software engineer I respect. The preliminary takeaway for software design expertise is that experts *attempt to predict the direction of change* for their software requirements, and design accordingly.

Replying to

What do you think about strong engs trying to find the right set of concepts/abstractions for the system, which are: - capture as much use case complexity as possible - non-overlapping - small in number ? In other words, breaking down complex system into manageable MECE parts.

Cedric Chin

@ejames_c

Replying to

@mikpanko

I don't get the sense that that's the way this senior engineer thinks about the problem. He mostly talks about essential vs incidental complexity as tradeoffs when picking the right set of abstractions for the domain.

1:59 AM · Jun 24, 2022TweetDeck

Replying to

and

Dave farleys modern software engineering is good at describing the dimensions a senior eng may want to consider. Tradeoffs and situational decisionmaking all difficult to make generalised advice, but its a good book.