5 ms·

I always have doubt on this, who is developer and who is engineer? I think, Who are capable to using existing languages, frameworks are developers. Engineers

I always have doubt on this, who is developer and who is engineer? I think, Who are capable to using existing languages, frameworks are developers. Engineers are the one who can design & create those frameworks, can understand algorithms and techniques / working principle. A engineer can reinvent the wheel (worst or better engineering from existing one makes good or bad engineer) The term `Senior` always refer the working experience on the field more than 1 time. Not necessarily the years.

gregjor 2y ago
Programmer, developer, software engineer, etc. get used interchangeably, they don't indicate any real distinction except maybe within a single organization. Similarly "senior" doesn't mean anything other than "I got promoted." In the last decade "architect" started to show up as a euphemism for what we used to call "analyst," someone who gathers, makes sense of, and translates business requirements into software development plans. But I have seen relatively junior programmers call themselves "architect," I suppose because it sounds cool. For me an architect designs buildings.
- strken 2y ago
  One of my friends decided to change his job title from "technical project manager" to "solutions architect" for the sole purpose of sales. He and the boss agreed that it sounded more impressive to the clients we were going after. Exact same day-to-day work. Exact same responsibilities and pay. Everyone within the company agreed that it was a complete joke. And yet, we still did it.
  - gregjor 2y ago
    You see that kind of thing a lot with contract programming firms -- they give all of their programmers fancy titles because it makes them look better to potential clients: "We only have senior software engineers available to work on your project, we don't hire junior people." In that environment the customer probably won't individually vet whomever gets put on their project. I have had recruiters tell me to use more impressive titles too.
    - Hashex129542 2y ago
      Yes, absolutely. I was Engineer titled in a company when I were only 1.x years of working experience.

gregjor 2y ago

Programmer, developer, software engineer, etc. get used interchangeably, they don't indicate any real distinction except maybe within a single organization. Similarly "senior" doesn't mean anything other than "I got promoted." In the last decade "architect" started to show up as a euphemism for what we used to call "analyst," someone who gathers, makes sense of, and translates business requirements into software development plans. But I have seen relatively junior programmers call themselves "architect," I suppose because it sounds cool. For me an architect designs buildings.

strken 2y ago
One of my friends decided to change his job title from "technical project manager" to "solutions architect" for the sole purpose of sales. He and the boss agreed that it sounded more impressive to the clients we were going after. Exact same day-to-day work. Exact same responsibilities and pay. Everyone within the company agreed that it was a complete joke. And yet, we still did it.
- gregjor 2y ago
  You see that kind of thing a lot with contract programming firms -- they give all of their programmers fancy titles because it makes them look better to potential clients: "We only have senior software engineers available to work on your project, we don't hire junior people." In that environment the customer probably won't individually vet whomever gets put on their project. I have had recruiters tell me to use more impressive titles too.
  - Hashex129542 2y ago
    Yes, absolutely. I was Engineer titled in a company when I were only 1.x years of working experience.