It's awesome to see this insight. One question/quibble about the junior devs / parents analysis: it seems to assume that junior devs aren't parents. That might be generally true, but I'm guessing there is also a fair number of people with kids getting into software (e.g., career-changers like myself!).
Thanks as always!
While I don't have kids yet, I'm also a career-changer. I will likely change careers again (and again?!) after I start a family of my own.
I didn't mean to say that these are distinct, non-overlapping groups! Poor communication on my part if that's what comes across. The dev.to community could include junior devs, experienced devs with children, and/or junior devs with children. I don't share data to indicate what the break down is, but it is interesting that "Good for Junior Devs" and "Ideal for Parents" are both popular among members of the dev.to community, especially when compared to those from Hacker News (or Product Hunt).
This Idea is the best.
Awesome analysis, Lynne. Did you know you could use <figcaption>A caption of my graph</figcaption> in the editor? Works like a charm! (Also, we should put it in the editor guide, oops)
<figcaption>A caption of my graph</figcaption>
What's interesting to me is that I really appreciate the work/life balance and "good for junior devs" (me) that dev.to has, and it's great to see that almost 3000 dev.to readers feel the same way.
Also, I think the bar graphs colors should correspond with the attribute instead of the position, but I'm not an expert on data visualization. 🙈
FIGCAPTION. I did not know about that!!! Thank you 🙌
I also really appreciate the dev.to community and the culture readers here have created. I'm pretty junior too. I guess it depends on who you ask, but in some scenarios, I'm extremely junior.
I'm not an expert on data visualization either, but these graphs are from Amplitude. I was definitely too lazy to create my own bar graphs, or modify colors. If that's an option, I wasn't even aware. 🙈
Haha no worries, I've never used Amplitude so I have no idea whether it's customizable.
Also, that was the same reaction I had when I found out about figcaption! It's amazing.
I love how as developers we all still get excited by the same silly things.
I've found that when I switch jobs, some of the biggest, most important adjustments I need to make are things that nobody at the new job talks about, even if asked. The bedrock of how a company or team operates often becomes unconscious, because it becomes hard to imagine working another way.
And I worry that teams self-report the values they aspire to rather than the values they actually hold. I've seen Agile put to great use, and I've seen it twisted into something deeply toxic. In both cases, the company and management felt they'd used Agile methods in a way that was "pretty standard."
How are you avoiding these pitfalls? Does it all simply average out once you collect enough data and compare across companies?
I love love love what you're doing. So much of the decision-making around hiring new devs, or accepting a new job, is done at the gut level. I love the idea of moving toward a more data-driven approach precisely because it could shed some light on the actual differences between company cultures.
Hi Chris! I so sorry that I didn't see this comment sooner –– I'm not even sure how I missed it!
Re: Aspirations vs. reality, this is something that teams who are truly introspective bring up themselves. Typically, teams will say outright whether X is something they're actively working towards or an accurate description of who they currently are. (This usually comes up when talking about diversity and inclusion, or code quality.)
Re: Agile example, this is exactly what I'm trying to get at! Everyone has a different definition of what Agile, work/life balance, or even engineering-driven means. I spend a lot of time "coaching" teams to explicitly write out their definition. Why? Because of exactly what you said above! People forget that how they work/operate/communicate is not how other teams work/operate/communicate.
I can't know how users interpret each value (so their are some unknowns when looking at the data I've collected thus far about user behavior), but the whole point of having profiles is for teams to tell us how they interpret each value. Now, we can all compare how different companies talk about the same values.
Did I answer your question at all? If I didn't, I hope you'll give me a second shot! 😉
No worries! I'm just grateful you spent the time on my silly questions! I'm extra-curious because the worst teams I've worked on are the least introspective, and the most likely to say they're doing things just like everyone else, have good work/life balance, etc. I think if I can avoid those places for the rest of my career, I'll be much happier. ;)
I really want Key Values to bring some sunlight to the problem, both so that motivated job seekers will have a better resource for finding like-minded teams, and so that teams will have a bit of a reality check as to how they compare with the rest of the industry.
I'm really impressed and pleased that it sounds like you're taking time with each team to create a really representative profile. That's immensely valuable for job-seekers, and I think will really help the teams your working with, too!
Best of luck!
They're not silly questions at all! They're actually really important ones.
It might help you to know that I've had 20+ teams email me with their 8 values, saying, "We'd love to create a profile!" and then never following through. They're surprised by how much effort goes into writing a profile and say they don't have time or resources. To me, simply having a profile says something about a team.
Please, let me know if you have other questions/ideas about how I can improve Key Values and help motivated job-seekers to find like-minded teams! While I identify as an ideal user for Key Values, I also recognize that I don't represent the entire population I want to serve.
It's really shocking how few people realize the importance of being team oriented. The fact that it shows up so low on these lists prove the need for awareness of the issue
Or that the survey has a bias Heavily Team Oriented has a default negative connotation, so I'm not surprised it ended up at the bottom.
Thanks Rodney! It's been equally interesting hearing people's responses to it!
People are surprised to see X so high on the list because they personally don't care about that thing. This is awesome (to me), because it demonstrates the diversity of values people have and why "good culture" isn't a one-size-fits-all type of thing.
The second thing I'm hearing a lot is that the values aren't clearly defined. I think that I can probably do a better job communicating this on my website but... this is the whole point! Each teams describes what value Y means to them, and we as job-seekers/developers can compare their responses.
great write-up. Huge fan of KeyValues.io and really appreciate you taking us all on the journey with you :)
Thanks Peter, that means the world to me. I really appreciate you building dev.to and creating such an amazing community for all of us. Before Key Values, I wasn't really familiar or integrated w/ any online communities. Now that I've been learning more about the different audiences that exist out here (in the interwebs 😂), it's clear how special dev.to is!
As a junior developer, I can say that I feel very comfortable here on dev.to to express my opinion, to ask for advice.
Great stats, Lynne!
I hadn't seen this before, and it's really cool. The presentation and the idea are both... well, really cool.
Haha, thanks Ben! Glad you dig it ☺️
It shows that most of developers worry about life work balance.
Thanks Lynne! Love the project and this post about things that developers value. I'm definitely sharing this widely. Thanks for the awesome work!
Yay! That makes me incredibly happy to hear!
Fun fact 😜: Many months later and Work/Life Balance is still #1. High Quality Code Base has competition for the #2 spot though.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.