Job offers and teams often ask
for good writing skills but having a colleague with good reading skills is a whole other benefit to be had.
=> More informations about this toot | More toots from simeon@indiehackers.social
@simeon oh for sure, peer reviewing code is a good skill to have, in fact, in interviews I much rather have someone review some code than write some.
=> More informations about this toot | More toots from hvdklauw@mastodon.social
@hvdklauw Interesting, I've never heard that one before. The focus seems to be on producing code, either on the spot or as homework, while, indeed, we spend a lot of time reading (and reasoning about) code as well. (1/2)
=> More informations about this toot | More toots from simeon@indiehackers.social
And then there's the prose we write when communicating scope, problems, solutions, debugging sessions, customer/user requirements, etc. etc. And while code is somewhat standardised (i.e. a limited set of instructions), prose is richer, more freeform, and therefore more open to interpretation and cofusion. (2/2)
=> More informations about this toot | More toots from simeon@indiehackers.social This content has been proxied by September (3851b).Proxy Information
text/gemini