In the government’s schema, programmers do the grunt work while the much more numerous — and much faster-growing — software developers enjoy a broader remit. They figure out what clients need, design solutions and work with folks such as programmers and hardware engineers to implement them.
That's still what it means at my company: tech-y stuff that doesn't involve programming. It usually involves more direct contact with clients, insulating the programmers from that. I'm not sure why it's called "system analyst," since they don't analyze systems.
The other programmers call themselves coders or developers. My official title might even be "developer." I tell people I'm a programmer because I'm 55.
Government statistics consider "system analyst" to be a third, different thing (https://www.bls.gov/ooh/computer-and-information-technology/...). "Computer systems analysts study an organization’s current computer systems and design ways to improve efficiency."
It is, at least from the visual of different "coding" type jobs there is still a slide for System Analyst. I have no idea what most of the differences are.
IIUC, if I come to you and say I want a website that looks like this slide I drew that makes you a _programmer_. You're mechanically implementing somebody else's design.
If I come to you and say I want to sell these widgets on a website and you develop the website then that makes you a _developer_. You're mechanically implementing your own design.
In the government’s schema, programmers do the grunt work while the much more numerous — and much faster-growing — software developers enjoy a broader remit. They figure out what clients need, design solutions and work with folks such as programmers and hardware engineers to implement them.