Liked this content a lot . Specially the part about balance between "going wild" or "ignoring" . For me , software architecture , and software development is all about balance - whether it is balance between quality and speed , or balance between business deliverables and non-functional requirements , and so on. At the same time , for us , software dev/architects , our legacy is inherently in our code/documentation/architecture design , so we should try to be true to our purpose , and not take short-cuts just because we are lazy.
@RealDogDad
3 жыл бұрын
I love this, the Pragmatic Programmer turned me onto it and has since changed my project structure.
@goobar
3 жыл бұрын
Me too!!! Such a good book 💯
@Utubewonderful
3 жыл бұрын
Hi could you have any idea of plan to start a golang related videos your very cool and calm content provider in youtube. And more than that you have very good plan when it comes to explain the concept deeper
@goobar
3 жыл бұрын
I don't have much experience with Go, but it IS something I've wanted to learn more about. Perhaps no can share some of that learning in the future
@jasonbarrett5489
3 жыл бұрын
Great topic. I'll say that I do appreciate the safety net of a strong automated test suite when I decide to fix some broken windows in a codebase.
@goobar
3 жыл бұрын
Yes! Definitely. A good test suite. A good CI setup. Anything we can do to give confidence that we haven't broken things can really help empower a team to be more proactive in fixing the "broken windows"
Пікірлер: 8