benlakey

10 ms·

61.
by benlakey 14y ago
That's not what I'm suggesting at all actually. Again, you're implying this is a zero sum game, in which the world has nothing but 'A' players. Thats not what I've said. Being a 'hard worker' is completely and totally irrelevant in software
62.
by benlakey 14y ago
I'm most definitely not a designer. :-) If you're interested, it's just the 'Responsive' wordpress theme. http://wordpress.org/extend/themes/responsive
63.
by benlakey 14y ago
This is also how GitHub operates, but it's only viable if you have 100% 'A' players.
64.
by benlakey 14y ago
You're implying that what's being discussed is a zero sum problem. We're simply saying that 'A' players work best with 'A' players, and if you fight for that in your organization then you'll do great things. 'B' and 'C' players will still e
65.
by benlakey 14y ago
Pay is actually quite low on the list of things that a great developer will value when choosing where to work. And I think it's dangerous to just lock the A players in a room amongst themselves; they need to communicate closely with others
66.
by benlakey 14y ago
Agree. Financial compensation is actually often much lower on the list of things software developers value at a company, particularly when they are 'A' players. Solving problems, working with other 'A' players, and stretching ones abilities
67.
by benlakey 14y ago
Fake it 'till you make is time and time again proven itself to work, especially when you surround yourself with people smarter than yourself.
68.
by benlakey 14y ago
Good stuff, dabent. I agree; Abstractions are valuable tools, but it's important to know whats underneath the abstraction, for when the abstraction leaks, or when it's the wrong tool for the job.
69.
Steve Jobs on Average vs Best Software Developers(benlakey.com)
112 points by benlakey 14y ago|123 comments
70.
by benlakey 14y ago
I don't think it's quantifiable. The numbers are imprecise opinions.
71.
by benlakey 14y ago
I agree that it operates on that assumption, and that the full-stack developer assumption is a good one. Have a read of this blog post for the mindset: http://codercake.com/benefits-of-becoming-a-full-stack-devel...
72.
by benlakey 14y ago
The 10x/20x thing doesn't refer to productivity at all. It refers to ability. So I think we're in fact saying the same thing here.
73.
by benlakey 14y ago
I suspect you're right, though I'd rather they share the non trade secret advice that they have in a more public fashion, such as a blog or stackoverflow.
74.
by benlakey 14y ago
Would you agree that being a great communicator, and growing as a person to be less nervous are aspects in the makeup of a great developer? (I'm not saying they are, just curious what you think).
75.
by benlakey 14y ago
These are fine points. Apologies if it came off sounding self-congratulatory.
76.
by benlakey 14y ago
I agree with you wholeheartedly, and I think the points are complimentary. I also wrote a post prior to this one, in which I argue that a team of good developers that can work together is far better than a team with one technically superior
77.
by benlakey 14y ago
I think the key here is 'good criticism'. It's important to be critical, but it can still be done in a respectful way.
78.
Why You Need To Hire Great Developers(benlakey.com)
21 points by benlakey 14y ago|31 comments
79.
Respect Among Software Developers(benlakey.com)
6 points by benlakey 14y ago|2 comments
80.
Maintainable Software and Premature Optimization(benlakey.com)
2 points by benlakey 14y ago|0 comments
81.
Software Development Technical Debt(benlakey.com)
1 points by benlakey 14y ago|0 comments
82.
Performance on-demand; Giving your ops team runtime flexibility(development.msnbc.msn.com)
1 points by benlakey 15y ago|0 comments