Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask stupid questions as a new software developer

nikitakazakov.com

Post reply on HN
Print view View original

71–80 of 87 posts

Re: Ask stupid questions as a new software developer

#71

Post by hutzlibu »

ChrisMarshallNY wrote: post #35
hutzlibu wrote: post #26

Earlier quoted context omitted.

"Don't treat any question as 'stupid.'" There definitely are stupid question that shows the person asking them was too lazy to think for a moment or at least google it. If people do not value my time, they are not worthy of it. But yes, it is important to seperate that from beginners question, as it is easy to forget, that we all started as beginners.

I’d say that a significant number of folks in this industry seem to have severe self-image issues, and get some kind of balm from attacking/looking down on the work of others. As the recipient of a great deal of this behavior (see “I ask ‘stupid’ questions all the time,” above), I think that it’s better to say “this is why we can’t have nice things,” and simply cover all my bases by not attacking others. It’s quite e…

"If someone asks a question I can easily answer; even if they are being “lazy” (which I believe to be an overused, and misunderstood word), or even trolling, I answer it in good faith. If I don’t have time, I say “I’m not able to answer that, right now,” or simply ignore it, if I can do so, in a way that does not come across as judgmental."

That is a nice habit, but I actually think I have the right to sometimes answer in a judgmental way, to honestly communicate my emotions about the topic (time wasting). And I found out, that this can work, too. But yes, if I am particulary annoyed, that can also lead to other people getting afraid to ask me anything at some point and rather continue do something stupid.

Re: Ask stupid questions as a new software developer

#72

Post by avmich »

junon wrote: post #37
onion2k wrote: post #28

Earlier quoted context omitted.

Very often you won't get that upfront research because juniors don't have the knowledge necessary to even start looking for themselves. Because you expect them to come to you with evidence before they ask you, your devs will just avoid asking you and spend hours wasting time instead. Any minimum requirements are a barrier. Barriers are bad for learning. You need to welcome questions even from people who have apparent…

> Very often you won't get that upfront research because juniors don't have the knowledge necessary to even start looking for themselves. Advice for junior devs: Asking "how do I even go about searching for this?" is also a perfect acceptable question. Another format: "how do YOU generally research things?"

For both of those questions peers answering them can choose.. to actually switch to answer some more simple questions - like, what to do in this specific case. They'll even ask for details - "how do I even go about searching for this?" - "the information you need is here", or "how do YOU generally research things?" - "what specifically you want to find?"

People aren't perfect.

Re: Ask stupid questions as a new software developer

#73

Post by pm90 »

throw_m239339 wrote: post #59
cupcake-unicorn wrote: post #58

Earlier quoted context omitted.

Most cases of sexism aren't "clear cut". If you're the only woman in the office, it can be hard to figure out what's going on. Believe me that you try to explain certain things away and don't want to go to sexism as a first choice or a choice at all. But when you're a year in and you still notice there are very real differences in the way you're treated versus your male colleagues you have to start accepting that sex…

> Most cases of sexism aren't "clear cut". If you're the only woman in the office, it can be hard to figure out what's going on. Believe me that you try to explain certain things away and don't want to go to sexism as a first choice or a choice at all. But when you're a year in and you still notice there are very real differences in the way you're treated versus your male colleagues you have to start accepting that s…

Have you ever tried reporting anything to HR? HRs main job is to protect the company. If the person you’re reporting about is higher up/difficult to hire for/knows the right execs, HR doesn’t really have much power to do anything. For cases where there isn’t enough clear evidence, their incentive is to not take any action at all. The reporter is now recorded as being “a problem” and they will get treated even worse.

Re: Ask stupid questions as a new software developer

#74

Post by rramadass »

onion2k wrote: post #28
mceachen wrote: post #3

Please ask me any question, regardless of how dumb you think it will make you look, after you've spent at least 5 minutes trying to answer it yourself. Bonus Points if you summarize your quick research efforts. Extra Bonus Points if this leads to more questions. (Caveat emptor: _many_ engineers are decidedly antisocial, but if you show that you did prior research before asking, you're showing to them that you value t…

Very often you won't get that upfront research because juniors don't have the knowledge necessary to even start looking for themselves. Because you expect them to come to you with evidence before they ask you, your devs will just avoid asking you and spend hours wasting time instead. Any minimum requirements are a barrier. Barriers are bad for learning. You need to welcome questions even from people who have apparent…

Disagree.

With the resources available today there is just no excuse to not do some preliminary research on your own before asking others for help. Nothing is more infuriating than when somebody comes to you with some detailed question the answer (or an idea as to the possible answer) to which is readily available a Google search away. You have to do some homework before asking for others time to solve your problem. This is the only way to mentally get involved and engaged in problem-solving and is a necessary part of learning. Too many people nowadays don't even want to take the first step but want everything spoon-fed. This should not be tolerated nor encouraged.

Re: Ask stupid questions as a new software developer

#75

Post by rramadass »

gregkerzhner wrote: post #61
onion2k wrote: post #28

Earlier quoted context omitted.

Very often you won't get that upfront research because juniors don't have the knowledge necessary to even start looking for themselves. Because you expect them to come to you with evidence before they ask you, your devs will just avoid asking you and spend hours wasting time instead. Any minimum requirements are a barrier. Barriers are bad for learning. You need to welcome questions even from people who have apparent…

I would argue that those "hours wasting time" looking for an answer yourself before you give up and ask someone more senior aren't a waste - they are an invaluable part of becoming senior yourself. As a senior engineer, you will often spend hours and days stuck trying to solve hard problems with noone else to ask, and having the grit, determination and creativity to do this is one of the greatest skills you can teach…

Absolutely correct!

>you will often spend hours and days stuck trying to solve hard problems with noone else to ask, and having the grit, determination and creativity to do this is one of the greatest skills you can teach an engineer

I would argue that _is_ the very definition of an Engineer.

Also it is an invaluable necessary skill to cultivate to navigate Life itself.

Re: Ask stupid questions as a new software developer

#76

Post by devwastaken »

devwastaken wrote: post #45
mceachen wrote: post #3

Please ask me any question, regardless of how dumb you think it will make you look, after you've spent at least 5 minutes trying to answer it yourself. Bonus Points if you summarize your quick research efforts. Extra Bonus Points if this leads to more questions. (Caveat emptor: _many_ engineers are decidedly antisocial, but if you show that you did prior research before asking, you're showing to them that you value t…

What is the best method for students to get a summer internship? What kind of things does hiring want to see from a student? What format of resumes are the most appealing? How do you negotiate costs and ensure the student can actually afford to live that work? I've asked a number of people, including uni admins, and none of them are based on words from the people whom actually hire. Especially in software where resum…

I realize this was not a call for questions. Can't delete it lol.

Re: Ask stupid questions as a new software developer

#77

Post by [deleted] »

cupcake-unicorn wrote: post #66
throw_m239339 wrote: post #59

Earlier quoted context omitted.

> Most cases of sexism aren't "clear cut". If you're the only woman in the office, it can be hard to figure out what's going on. Believe me that you try to explain certain things away and don't want to go to sexism as a first choice or a choice at all. But when you're a year in and you still notice there are very real differences in the way you're treated versus your male colleagues you have to start accepting that s…

There are few positive benefits currently to reporting things like sexism in the workplace, sexual harassment, even rape. It sucks that it's like that but that's the reality right now. The reality is that they probably won't be addressed. If less than one percent of rapists actually get convicted, what kind of "positive impact" do you think will come of reporting workplace sexism? Like the other reply to this post, t…

[deleted]

Re: Ask stupid questions as a new software developer

#79

Post by ryloric »

ryanianian wrote: post #39

The article is right but its ambitions are too low. Everyone needs to ask helpful questions in the right way and at the right time. This is simple but not easy. I'm a staff-level engineer at a well-known tech company. One of the most important things I do is ask simple/"dumb" questions of other very smart but more junior engineers. I try to ask questions they haven't considered or explained well. I ask questions that…

I feel what most call "stupid questions" come from people assuming others have the same context and have the same assumptions about some topic. It's a kind of communication failure imho.

Your advice (which is excellent btw) mostly targets this kind of thing.

Re: Ask stupid questions as a new software developer

#80

Post by ChrisMarshallNY »

hutzlibu wrote: post #71
ChrisMarshallNY wrote: post #35

Earlier quoted context omitted.

I’d say that a significant number of folks in this industry seem to have severe self-image issues, and get some kind of balm from attacking/looking down on the work of others. As the recipient of a great deal of this behavior (see “I ask ‘stupid’ questions all the time,” above), I think that it’s better to say “this is why we can’t have nice things,” and simply cover all my bases by not attacking others. It’s quite e…

"If someone asks a question I can easily answer; even if they are being “lazy” (which I believe to be an overused, and misunderstood word), or even trolling, I answer it in good faith. If I don’t have time, I say “I’m not able to answer that, right now,” or simply ignore it, if I can do so, in a way that does not come across as judgmental." That is a nice habit, but I actually think I have the right to sometimes answ…

Oh, I have the right (and linguistic skill) to be dick majuere. But, like so many of these “rights,” I should also expect to be held to account, and suffer consequences, for exercising said “right.”

If people see me being cooperative, helpful, and a source of good information, they will develop one type of opinion of me.

If they see me as prickly, judgmental, arrogant, and pugilistic, then they will develop another type of opinion of me.

Depending on who is developing that opinion, the consequences (and rewards) to me can be quite significant.

Post reply on HN