I cannot tell if it is domain knowledge, the type of programming, or the industry you're in, but I get the feeling we live in completely different worlds despit

I cannot tell if it is domain knowledge, the type of programming, or the industry you're in, but I get the feeling we live in completely different worlds despite our similar responsibilities (working with SaaS, hiring devs, etc). I get the feeling there are a lot of people who are developers by trade who are following what they feel they should do to progress their career rather than what they should do to work on something that interests them. Sure, the industry isn't what it used to be in terms of job market, but for a good long while there it was relatively easy to find something that interests you if you were competent. But if you're not interested in what you're working on, I find it strange to write a blog about the C#/.NET journey. I'm asking these questions genuinely: Was this a self imposed expectation for career reasons? To have a tech blog? Are you actually interested in programming or is this something you found that you're decent at and knew there were career opportunities? About SQL knowledge, over the many years in this profession, I've re-learned SQL three times. This is because I'm a generalist, and there were large portions of time where I just didn't need to know it. But surely, in all your years of experience, you must have realized: You will never know or recall everything you learn or even scratch the surface of what you haven't. Even if you did remember everything about SQL when you learned it, you're going to have to relearn it anyway. Everytime I touch Postgres there's loads new features out. That is how any maintained software is. That is just the job, as far as I'm concerned. Very few people have the luxury of being able to hyper specialize and looking things up isn't just important, it is necessary, because being an encyclopedia of product development isn't why you're employed. The knowledge and expertise you are paid for isn't SQL syntax or how well you know C#, it is your ability to apply technology to solve problems and effectively work within a team to do so (a tangent, but this is why in the long wrong AI won't replace you). I don't mean to preach or give a tome of a message. I am _genuinely_ interested in your perspective. I have bounced around a lot in my career but generally have to mentor folks and I'd love to chat more about this particular struggle because I hear it frequently. Especially from those who seem to have a bit of an identity crisis in their profession.