Something that a senior dev told me early in my career after I lamented the difficulty of a feature request and suggested we water it down (honestly can't remember details since these words are always at the forefront): "That's not really an option."
I'm not sure exactly how to describe the meaning I took from it but it's something I'm reminded of all the time. It seems all too common to see developers morph a problem into something easier and then solve that problem which nobody has. Be the person who really understands the problem which needs solving and the program will almost work itself out. And that's not just in the context of building a feature; even fixing a simple bug because someone pointed it out is likely to be noticed positively.
Tying that back to the article, my takeaway is that people will take notice of the persons who actually solve their problems and then suggest them to others who need problems solved. Which is a helpful networking strategy presuming that people will likely have problems which you know how to fix.
Most devs are left in the dark and never get the 10,000 ft view and when they do it's often just a laughable item on a checklist and when it's not they're fully unprepared to deal with that kind of stress.
> "That's not really an option."
That only works on some people. People who really care.
