Yep, you nailed it. Had it not been for ACA, making the career leap to co-founder would have been incredibly difficult. Two years later, it's a honor to be able to provide insurance to our employees.
My actual suggestion was to hop on with the product team/co-founder. This article is a narrative about something we found pretty interesting during product development.
Similarly, the offer here is to take a deeper look at what we're building and a (quite genuine) offer to incorporate any suggestions you might have into our roadmap.
@trevyn We've got some things in that vein that are working in the app today — and are working toward even more. If you’d like, we could hop on a call and give you a tour of the app and show you where we’re headed?
Seems like you've given this some thought on how this should be done right; would love to include them in our product development discussions.
Would love to better expose our data set. It’s a bit tricky however: we’re specifically interested in enterprise software engineering (the patterns of which differ radically from the open source world).
In order to dig into enterprise data, we sort of need to have a ToS that only allows us to talking abstractly about aggregate data.
You’re right: this post is a narrative about product development, and a strong correlation we found between two variables across 20 Million+ commits that we thought was fascinating and supports general 'kitchen logic' around best practices. The axes are not labeled, but if you like we can set you up with a demo account and walk through your data with you.
One other note: the typical common use case for the product has been stakeholder management; something we have doubled down on in product development. Any specific critique about how we can improve most welcome!
This is a big part of why we think engineering metrics are a tough nut to crack: there’s a fair bit of research that suggests tying KPIs to compensation is a huge anti-pattern for certain types of work (chiefly those involving lots of novel problem solving).
Highly recommend Daniel Pink’s “A Whole New Mind” on this topic; it’s pretty fascinating stuff.
@Bartweiss thanks for the feedback. The thing about “gaming the system”, is that it presumes an adversarial relationship between engineers and non-engineers. That’s pretty unfortunate, and it’s our view that a good portion of this is due to non-engineers not really understanding what happens software development.
But yeah, my co-founder has a pretty interesting take on gaming the system.
Ah nice, @Eiriksmal — 'once upon a time…' and 'pre-impact', sounds like this was a while ago now :) Encouraging to hear that this has been helpful for you.
"Every measure of a good developer is qualitative. That makes them all subjective."
^ This post scratches the surface on a timely and relevant question many teams face, but the author seems to throw hands up and say everything is subjective.
Yeah, have to agree with louprado here. The 'People around you control your mind' although a bit more entertaining and click baity is actually more accurate than 'peer' or 'pressure'.
It's all about the elevation. You can drive for hours on the east coast and be in the same relative eco-system. Here in the west, you drive an hour and can move through several. Start in a scorching red-rock desert and move in elevation to an alpine meadow in a short drive. And the temps drop 3°F for every 1k feet you gain in elevation.
Whoah.