I'm a developer with over 10 years of commercial experience. I've worked on all areas of the stack (Web and OS) but do not claim to be a specialist in any one single area.
In my experience, a good rule of thumb to go by when trying to source a 'decent' developer is seeing if they respond to problems with possible solutions.
You'll be amazed how many developers are happy to expect others to actually do the problem solving; they are only interested in the instruction.
My goal is to make useful and helpful advice and content that will help others!
New content everyday, please leave feedback if there is something you want to see!
To add to this, it’s also is interesting to see the problem solving threshold people have. Some people give up immediately when an issue occurs and ask others, some never ask and might spend forever trying to solve a problem. A good balance is needed to solve things on your own but also ask others once you’ve properly exhausted your options.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
in my experience the key is not to have solutions, but to resist the urge to propose your solution, and instead to do a root cause analysis until the problem is so clear that the problem becomes obvious
I'm a developer with over 10 years of commercial experience. I've worked on all areas of the stack (Web and OS) but do not claim to be a specialist in any one single area.
That's the holy grail! Good luck finding a management layer understanding of this in the common working world where technical debt is difficult to describe.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my experience, a good rule of thumb to go by when trying to source a 'decent' developer is seeing if they respond to problems with possible solutions.
You'll be amazed how many developers are happy to expect others to actually do the problem solving; they are only interested in the instruction.
To add to this, it’s also is interesting to see the problem solving threshold people have. Some people give up immediately when an issue occurs and ask others, some never ask and might spend forever trying to solve a problem. A good balance is needed to solve things on your own but also ask others once you’ve properly exhausted your options.
in my experience the key is not to have solutions, but to resist the urge to propose your solution, and instead to do a root cause analysis until the problem is so clear that the problem becomes obvious
That's the holy grail! Good luck finding a management layer understanding of this in the common working world where technical debt is difficult to describe.