plaugg

There are (at least) three aspects to consider:

- How will the company / your boss decide that you are doing a good job? - Focus on that first. Include the parts they don't directly value but where you think you need them in order to reach that goals.

- How do YOU know you are doing a good job? - to develop that taste you need peers to look up to. Find them in meetups, in un-conferences, conferences or on the internet.

- Build your skills in three main areas:

   - "Behavioural" skills (a.k.a "soft" skills) - written communication, verbal communication, be good at giving and 

receiving feedback, building professional relationships, organize your work, learn to "manage up"

   - domain skills (learn about the company & the field)

   - tech skills - focus more on concepts & principles and less on the "framework of the day".

Note the publishing date on that RFC.

Also (of course) there is a Wikipedia list of funny RFCs, many with a similar publish date: https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for...

90% sure it's "dark matter developers" as in "they never write blogs, they don't go to user groups, they don't tweet or facebook, and you don't often see them at large conferences." - https://www.hanselman.com/blog/dark-matter-developers-the-un...

isn't this just showing the effects of your filterbubble as defined by google?