4 ms·

Isn't that the distinction between "Programmer" and "Architect" that some places use? Although, it isn't really standardized.

• navd 8y ago
  Not to me. I think the distinction between these titles are silly. Part of programming is architecting applications. There really isn't a way out of it unless you've just been maintaining and patching up existing code your entire life.
  • 52-6F-62 8y ago
    I'm not settled. Do you see a difference between designing and implementing? From experience, I do... but I'll happily hear other opinions.
    • navd 8y ago
      The line seems blurred. I've found the end result is much more desirable designing and iterating on existing code as you implement.
• WorldMaker 8y ago
  I've never seen a formal definition for "Architect" that applies to more than one usage of that term across companies. Standardization would be the key to it for it to ever be a meaningful distinction. Similarly, some companies use "Programmer" versus "Engineer", but also there aren't good standards there, and worse that bumps into the expectations in the rest of the business world for what "Engineer" is supposed to mean. (Professional Engineering accreditations and licensures.)