Until the more senior member quits because they are wasting the vast majority of their time answering questions that could have been answered by just trying for more than 30seconds after hitting an obstacle...
How to be a wizard programmer
21–30 of 69 posts
Re: How to be a wizard programmer
#22Is wizard better than ninja or rockstar? (Am I the only one that gets put of by job ads asking for nonsense titles like these?)
Re: How to be a wizard programmer
#23Earlier quoted context omitted.
> it's the first search result for a term they didn't happen to know > even the concept of "search for the error message" is a pattern someone needs to learn I suppose if we're talking about a graduate or intern this is okay, but when you have somebody that supposedly has a few years experience this is just infuriating. There is also the point that you shouldn't be getting a graduate/intern to be doing work they have…
>but when you have somebody that supposedly has a few years experience this is just infuriating. You know how sometimes programmers on Hacker news talk about toxic team mates who are hard to work with and bog the whole team down through arrogance? Becoming furious when someone asks you a question and truly wishing they'd waste half a day deriving it from first principals themselves rather than just asking you and hav…
Given the choice, I don't want a "10x" programmer who works alone or only wants to work with other "10x" programmers. I want a 2x programmer who turns everyone around them into a 2x programmer while becoming a 4x programmer, and who then turns all those 2x programmers into 4x programmers while becoming an 8x programmer, and whose newly minted 2x programmers turn everyone around them into 2x programmers while becoming 4x programmers.
Re: How to be a wizard programmer
#24Earlier quoted context omitted.
More likely in my experience, the senior member feels valuable for being able to answer questions and help others.
Not after twentieth question of similar construction and similarly easy to be answered by the one who asked if he actually read the friggin' docs. Seniors like to help learn, not to be used as a walking manual.
Re: How to be a wizard programmer
#25Until the more senior member quits because they are wasting the vast majority of their time answering questions that could have been answered by just trying for more than 30seconds after hitting an obstacle...
I like answering questions, especially when this leads to someone's growth; it's a satisfaction to me when the junior goes from newbie questions to more and more advanced ones.
But, even if I disliked answering questions, I'd still very much prefer answering questions than having to clean after a junior that didn't dare to ask a question.
Re: How to be a wizard programmer
#26Is wizard better than ninja or rockstar? (Am I the only one that gets put of by job ads asking for nonsense titles like these?)
In job ads rockstar is definitely the most annoying/lame one.
But, yes, wizard is better.
Re: How to be a wizard programmer
#27Is wizard better than ninja or rockstar? (Am I the only one that gets put of by job ads asking for nonsense titles like these?)
The first type of company is a great place to learn new things if you're quite junior. The second is a good place to demonstrate your ability to hack solutions together fast if you're mid-level.
If you're more senior then you should probably avoid all of those sorts of companies because neither will want to do things in anything resembling a sane way.
Re: How to be a wizard programmer
#28Is wizard better than ninja or rockstar? (Am I the only one that gets put of by job ads asking for nonsense titles like these?)
Re: How to be a wizard programmer
#29Until the more senior member quits because they are wasting the vast majority of their time answering questions that could have been answered by just trying for more than 30seconds after hitting an obstacle...
Note also that there's a subtle difference between senior devs and experienced jerks.
Re: How to be a wizard programmer
#30If you run into problems none of the senior devs have experience in and have no answers for, my first concern is that you're massively over complicating something we've solved in a simpler and less risk-exposed way. My second concern is that you're intentionally reinventing the wheel in a way that is massively over complicating something we've solved in a simpler and less risk-exposed way just for your own interest.