Global Feed Post Login
Replying to Avatar daniele

This has a mirror point of view: many developers have a way of working that excessively focuses on abstract details (refactoring, optimization, obscure edge cases, niche features) which in the end often simply means staying in their own really technical comfort zone, procrastinating the shipping of a truly functional product.

I think the solution is simply integrating competencies, investing 80% of your time on the core skills and spending 20% on collateral ones. Improve the variety of your skills and put yourself in others' shoes. This 20% permits overlapping others' core skills, creating a valuable collaboration.

And finally, don't forget to listen to the end users.

nostr:nevent1qqspw6tt2awlug7707zguv8vmhwnwlt02h8wtv7k98cus8wxsq97ypgprdmhxue69uhkx6rjdahxjcmvv5hxgar0dehkutnrdakj7q3q0000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsxpqqqqqqzuvcsqe

Avatar
tee 9mo ago

the problem for new devs is that there are so many unknown unknowns. we don't know what the core competencies are, so by that logic - prioritizing making the unknown unknowns KNOWN unknowns would make sense.

The new problem becomes - how to do that, and the only solution I've come to is to try to read more, a lot more, and try to read deeper, better things.

Would love to hear other peoples thoughts on the topic of making unknown unknowns known unknowns.

Reply to this note

Please Login to reply.

Discussion

No replies yet.