7 ms·

It's not bad advice - and also nothing new - but it's very condescending: "I want to help average developers who want to improve by calling out 10 performance-k

by vosper 14y ago

It's not bad advice - and also nothing new - but it's very condescending: "I want to help average developers who want to improve by calling out 10 performance-killing behaviors that stagnate the careers of most developers". What makes this guy so great? He states that his product is "difficult even for large companies to master" so I'm inclined to think he's doing a few things wrong himself.

exodust 14y ago
He paints a black and white picture and divides everyone into "average" or "good", that's my only issue. In reality, each project demands different solution, some have heavy UX challenges, others strictly an architecture puzzle. There's bound to be variation in how "good" our work is for each aspect of the project. In one year, most of us have done lots of stuff, some really good, other stuff good. Like making an album, not every song will be a classic, but you'll break even and be home before midnight most nights. Sometimes the solution is not pretty. There's also developer ability in the mix too, and developer-philosophy! With javascript, for example, sometimes your function might be "the long way around" but still fine. Ok so it could have been done a little more efficiently if you'd constructed that other array and took that extra step etc etc. But here's the thing: in some languages such as javascript, taking the long way around might afford you better readability of your own code later, or just easier to work with for adding new elements later. It's YOU who makes that call. Sure, there's advice to be shared and we're all learning, but there's also a flexibility with programming that affords all but the most critical applications a bit of breathing room. If someone sees a better way to write a function, then great, update it if you feel it's a good choice. Or tell them they can update it anytime.
Aaronontheweb 14y ago
OP here. Our product is an analytics service and we manage large volumes of time-series and cohort data. Every developer has lots of room for improvement. I'm no exception. What I'm calling out is that there's a large cohort of developers, I've labeled them as "average developers," who completely stop growing intellectually and professional. They're technically passable but are stunted. Strong developers, a small cohort of 10x developers (I'm a 10x developer) who I've labeled as "strong developers." The reason they are so productive is a strong focus on self improvement in areas that drive productivity. For some really gifted developers this may come naturally / intuitively; for others like me it was more intentional / learned. I wanted to share those learnings with average developers who are self-aware enough to realize that they're not growing and don't know how to fix it. The condescending tone is intentional. Having a thick skin is a requirement to confront your own weakness. If the tone bothers you, you're probably a little too sensitive. And in case you're curious: I would never talk down to an engineer on my team this way. I can recognize the difference in writing a blog post intended for the anonymous Internet versus an intimate conversation with someone I work with 12 hours a day.
- vosper 14y ago
  I am always concerned when I hear a developer self-identifying as a "10x developer" - you may well be right, but it smacks of arrogance as well. Likewise, being intentionally condescending is an unusual approach to take at any time - even to the "anonymous internet". No-one likes to be condescended to (by definition) and so if you're attempting to promote your company and opinions I'd advise you to reconsider your tone.
  - Aaronontheweb 14y ago
    I'm not the best developer in the world and probably won't be, but I'll freely admit that I'm excellent when it comes to productivity and iteration speed. There's nothing "arrogant" about believing that you're good at something, particularly after spending many many years believing that you weren't and working really hard to improve. And there are many things I still do wrong and I'm working on improving those too. Most of the feedback I've received on the article has been overwhelmingly positive, which leads me to believe that it's a small population of sensitive people who take issue with the tone.
general_failure 14y ago
Give it a rest already. Most advise is condescending. Including yours. If you haven't worked on a product that is 'difficult' for other to master, maybe it's because you just haven't solved any hard programs. Can you list all amazing programs that you have written? Here is a dude who has started a company and he has something to say. He has written something nice and instead of appreciating what he has written and what he wants to convey, people go on and on nitpicking about irrelevant stuff. Sorry, but yours is a terrible comment.

by vosper 14y ago

exodust 14y ago

He paints a black and white picture and divides everyone into "average" or "good", that's my only issue. In reality, each project demands different solution, some have heavy UX challenges, others strictly an architecture puzzle. There's bound to be variation in how "good" our work is for each aspect of the project. In one year, most of us have done lots of stuff, some really good, other stuff good. Like making an album, not every song will be a classic, but you'll break even and be home before midnight most nights. Sometimes the solution is not pretty. There's also developer ability in the mix too, and developer-philosophy! With javascript, for example, sometimes your function might be "the long way around" but still fine. Ok so it could have been done a little more efficiently if you'd constructed that other array and took that extra step etc etc. But here's the thing: in some languages such as javascript, taking the long way around might afford you better readability of your own code later, or just easier to work with for adding new elements later. It's YOU who makes that call. Sure, there's advice to be shared and we're all learning, but there's also a flexibility with programming that affords all but the most critical applications a bit of breathing room. If someone sees a better way to write a function, then great, update it if you feel it's a good choice. Or tell them they can update it anytime.

Aaronontheweb 14y ago

OP here. Our product is an analytics service and we manage large volumes of time-series and cohort data. Every developer has lots of room for improvement. I'm no exception. What I'm calling out is that there's a large cohort of developers, I've labeled them as "average developers," who completely stop growing intellectually and professional. They're technically passable but are stunted. Strong developers, a small cohort of 10x developers (I'm a 10x developer) who I've labeled as "strong developers." The reason they are so productive is a strong focus on self improvement in areas that drive productivity. For some really gifted developers this may come naturally / intuitively; for others like me it was more intentional / learned. I wanted to share those learnings with average developers who are self-aware enough to realize that they're not growing and don't know how to fix it. The condescending tone is intentional. Having a thick skin is a requirement to confront your own weakness. If the tone bothers you, you're probably a little too sensitive. And in case you're curious: I would never talk down to an engineer on my team this way. I can recognize the difference in writing a blog post intended for the anonymous Internet versus an intimate conversation with someone I work with 12 hours a day.

vosper 14y ago
I am always concerned when I hear a developer self-identifying as a "10x developer" - you may well be right, but it smacks of arrogance as well. Likewise, being intentionally condescending is an unusual approach to take at any time - even to the "anonymous internet". No-one likes to be condescended to (by definition) and so if you're attempting to promote your company and opinions I'd advise you to reconsider your tone.
- Aaronontheweb 14y ago
  I'm not the best developer in the world and probably won't be, but I'll freely admit that I'm excellent when it comes to productivity and iteration speed. There's nothing "arrogant" about believing that you're good at something, particularly after spending many many years believing that you weren't and working really hard to improve. And there are many things I still do wrong and I'm working on improving those too. Most of the feedback I've received on the article has been overwhelmingly positive, which leads me to believe that it's a small population of sensitive people who take issue with the tone.

general_failure 14y ago

Give it a rest already. Most advise is condescending. Including yours. If you haven't worked on a product that is 'difficult' for other to master, maybe it's because you just haven't solved any hard programs. Can you list all amazing programs that you have written? Here is a dude who has started a company and he has something to say. He has written something nice and instead of appreciating what he has written and what he wants to convey, people go on and on nitpicking about irrelevant stuff. Sorry, but yours is a terrible comment.