Hacker News new | past | comments | ask | show | jobs | submit login

Almost correct.

Systems analyst was the person writing up an extremely detailed specification of what a program was supposed to do, which a programmer then implemented in a particular language.

The two merged at some point, when the demarcation line between the two of them became vaguer and overlapped more. This more or less coincided with more powerful 'frameworks' (if the name even applies) and libraries becoming available, as well as a massive increase in computing power which allowed for a near real-time edit-compile-test cycle which made programmers so much more productive that they suddenly weren't the bottle-neck in the process any more.

Another factor was that plenty of 'hobby' programmers found their way into professional IT jobs and they'd been doing this 'programmer/analyst' hybrid thing all along so for them it was a natural to continue to do so.

This happened somewhere in the mid 80's.

Then the web happened and the analyst job eventually became much more high level, nowadays we'd call a person that does work related to what an analyst used to do product owner or similar.

All of these definitions have meant different things at different points in time.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: