3 ms·

I don't think there's a reason for you to feel dumb: there are a lot of candidates that are the opposite of the grandparent, and want to do "it" for the rest of

by ratww 5y ago

I don't think there's a reason for you to feel dumb: there are a lot of candidates that are the opposite of the grandparent, and want to do "it" for the rest of their lives. However, a lot of times the "want to do it forever" part could be a sign that the candidates doesn't want to learn anything new, which is indeed a very bad sign. On the other hand there are people who want to want to keep doing tasks so they get a deeper understanding of the domain, as mentioned elsewhere in the comments... and you can't afford to say no to those people.

nocman 5y ago
> However, a lot of times the "want to do it forever" part could be a sign that the candidates doesn't want to learn anything new, which is indeed a very bad sign. While that is true for a lot of jobs, there are also a fair number of employers that are perfectly content to have an employee that does job X at their company for as long as they are of working age. In the software world it pretty much follows from the fact that the largest chunk of development jobs out there are just CRUD apps and processes that feed them. Many companies do the same things with largely the same software for years and years and years. As long as an employee is getting the work done, many of those employers are thrilled to have a long-term employee doing the same tasks they've been doing for years.
- ratww 4y ago
  A developer that isn't willing to learn new things won't be able to do CRUD for long. You can stick with the same technology and language, sure, but the frameworks and the language will evolve under you. Tools evolve (Git? Github? CI?). Processes evolve (Scrum?). Requirements change (HTTPS? Accessibility?) There are gonna be lots of changes coming from the outside. Heck, when I think of it, frameworks targeted at CRUD apps were probably the things that have changed the most during my career. I have a few friends doing stuff with C++ and they joke about how much tech in the web/enterprise bubble changes.

by ratww 5y ago

nocman 5y ago

> However, a lot of times the "want to do it forever" part could be a sign that the candidates doesn't want to learn anything new, which is indeed a very bad sign. While that is true for a lot of jobs, there are also a fair number of employers that are perfectly content to have an employee that does job X at their company for as long as they are of working age. In the software world it pretty much follows from the fact that the largest chunk of development jobs out there are just CRUD apps and processes that feed them. Many companies do the same things with largely the same software for years and years and years. As long as an employee is getting the work done, many of those employers are thrilled to have a long-term employee doing the same tasks they've been doing for years.

ratww 4y ago
A developer that isn't willing to learn new things won't be able to do CRUD for long. You can stick with the same technology and language, sure, but the frameworks and the language will evolve under you. Tools evolve (Git? Github? CI?). Processes evolve (Scrum?). Requirements change (HTTPS? Accessibility?) There are gonna be lots of changes coming from the outside. Heck, when I think of it, frameworks targeted at CRUD apps were probably the things that have changed the most during my career. I have a few friends doing stuff with C++ and they joke about how much tech in the web/enterprise bubble changes.