3 ms·

I've had the unfortunate luck of working with a couple of people with "senior" in their title that once faced with an error message from a open source library,

I've had the unfortunate luck of working with a couple of people with "senior" in their title that once faced with an error message from a open source library, starts their troubleshooting with searching for the error message and if nothing comes up, opens a issue on the issue tracker and then wait. They didn't even consider digging into the source code of the library to figure things out themselves. I haven't worked with a lot of people like that, but enough to guess that there is quite a bit of people who work that way.

orwin 4y ago
To me, it is only an issue if they sit still after and do not start to work on something else. But I am unashamed to admit that if I don't find the error in github/gitlab issue tracker, and if it seems to take more than 20 minute to investigate, I'll open an issue then move on (if I already know the library, if it's new to me, I'll assume Pebkac for at least two hour and try to rubber duck the issue)
- Mezzie 4y ago
  Depending on how much you have on your plate, this is ideal from a time management perspective. Knowing when and how to delegate is a very important skill. Just because you can do something doesn't mean that it's a good use of your time.