Just finished "Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman". Some useful bits, but overall the crafting rethoric rubs me the wrong way. I can't pin it down yet, it just doesn't feel "right". I also can't shrug off the vein of elitism underpinning it.
There is very little mention of teamwork across the whole book. Interactions are always individual to individual (rubbing elbows, mentorship, pair programming, etc.) and, even if not directly stated as far as I can recall, success looks pretty much like a function of one's skills
-
-
Which is in sharp contrast with my own experience: no matter how talented an individual might be, it's the chemistry and the processes inside the team that make it or break it. And if the focus in craft is on producing something useful, then teamwork deserves much more space.
-
I agree, with this sentiment. That said, there's a lot of books about how to make teams and teamwork better, but few about self-improvement (in the context of software engineering).
@apprenticeshipp fills in this gap, IMO.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at