Comment by peteforde
23 days ago
You're projecting several layers of bias onto this scenario.
The more busy you are, the more valuable your time... the more expensive context switching is. When you are known as the person with the answers, your day is at least partially structured around getting people to leave you tf alone so that you can actually concentrate on getting your own work done.
There's a really toxic expectation that people who are senior should stop what they are doing XX times per day to help other people figure out their issues. Usually there's zero consideration given to how much each one of these interruptions takes away from them. Resentment builds cumulatively.
Before LLMs, this conversation usually went like this:
"What should I do?"
"What do you think you should do?"
"X"
"Do X"
There's only so many times that can play out before you really want everyone to just fro.
Anyhow, you should try hard not to "hate and despise" LLMs. Life is too short to invent paranoid reasons not to use the best tools available. That's another instinct you learn as an experienced dev.
if this is the experience in a team, then the team already has a problem. i expect these things to be made clear up front.
when someone joins a team they should be assigned a mentor whom they can ask any question, no matter how dumb, and the mentor then guides the new team member in how to approach such a question, which at that point can include asking the LLM. it is the mentors responsibility to point out when it is ok to ask another senior developer. daily standups can also help with this sort of thing.
in a close knit team i would also expect that either everyone can ask anything from everyone else, and that everyone learns when it is ok to ask questions. the situation you describe should simply never arise. if it does, then something is going wrong
Alternative take: the assumption that senior engineers get pressured into agreeing to mentor without it formally being an acknowledged part of their job - that is, that a significant percentage of their time is supposed to be allocated to making themselves available to juniors - is fundamentally a problem.
There is so much stigma associated with being an senior engineer that simply wants to spend 95% of their day working on the problems that they were hired to solve. The worst part is that the vast majority of people in this situation are not compensated for this time, and they are expected to keep up with their actual assigned responsibilities.
This state of affairs is a relatively new thing. The idea that you would join a company with the expectation that the most important people to the success of a project should drop what they are doing to context shift to someone else's problem several dozen times a day is not something that would have been remotely normal twenty years ago.
I am not saying that mentoring is bad or that asking for help is bad, just that there's been a change and the unspoken vibe is that if you're not happy to work at ~30% capacity because you need to mentor people, you're some kind of antisocial jerk.
If a company wants seniors to mentor, pay them to mentor. It's very simple.
mentoring juniors should always be part of the job. sharing your experience and knowledge is part of the common job description. the idea that you just write code and never need to share your experience with others is a fundamental misunderstanding of what your work is about. you would have expressly negotiate an exception into your contract if you want that, not the other way around.
what doesn't work is the assumption that mentoring doesn't take any of your time and that you are expected to manage the same workload with and without mentoring. that's not ok. and spending 70% of your time mentoring may also be a bit to much, but if that is what the company needs then it is still your job.
4 replies →
Why would you accept a scheduled call if you want to be left alone? That makes no sense.
You're the one projecting bias onto this scenario. You assume people only want to talk to you to waste your time. If you work with professionals, you can assume that when they ask you a question, they have a reason to ask you that question. Assuming that they're just being lazy is bad faith.
Accepting a call and then giving someone this kind of non-answer is extremely disrespectful of their time and their professionalism.
> Anyhow, you should try hard not to "hate and despise" LLMs.
That's not what I wrote. You're being needlessly dishonest and disrespectful right here.
Again: getting a call is enough to knock someone out of deep concentration.
Anyhow, in addition to not hating LLMs, I would add "try not to use dramatic, hyperbolic devices in casual writing, it makes you sound ridiculous" to my advice.