Same. Also when I see a spec for example or some summary I always have the impression it doesn't get to the point. Like, the core ideas are in there but also somehow lost and I have to work them out again which makes me wonder if the person generating it understood what is going on or if it would just have been fast to just write it by hand (you still use LLMs for research and such).
The potential I see with LLMs is that a single team or even IC can now deliver whole feature end to end. Having just more services only means I get bogged down in PR review by other teams. Or I lose time waiting on them to do the change. In other words, any gain I got I lose tenfold because of inter-team coordination.
I think if you want to see delivery speed up focusing on what a team can own is more relevant than if you have merge conflicts.
over the last few years an intuitive mental model formed in my mind that helped me deal with uncertainty in technical projects. I started out articulating it and this is the first installment. Would be interesting to know if it brings anything new to the table.
Unfortunately no. We only provide you with slides, exercises, and projects. But I put a reference to Scala books into the README which should fill the gaps.
