3 ms·
Why should anyone care about the US Bureau of Labor Statistics definitions? Especially since they're defined in a way that you can fit most software jobs in eit
by jstx1 5y ago
Why should anyone care about the US Bureau of Labor Statistics definitions? Especially since they're defined in a way that you can fit most software jobs in either category. It's not obvious to me that there's any meaningful difference between the two descriptions.
Programmer vs developer; or software developer vs software engineer - all of those arguments seem either like pointless nitpicking or an attempt to generalise things that can't be generalised.
Whatever you do, you have some job title and job responsibilities - that's your most reliable point of reference even if the title isn't descriptive or accurate. So if your company has called you a $x, you're $x until you get a job with a different title. And if you get a job with the same title but different responsibilities, then you're still $x even though you do something completely different.
Basically, your title only has meaning in the context of your current company and team. Don't try to compare across companies or generalise too much because you end up with useless definitions like the ones from the BLS.
- toast0 5y ago> Why should anyone care about the US Bureau of Labor Statistics definitions? I'm sure some people have obligations to use BLS definitions for something, and those people have to care (should or not). But, my employers seemed to draw titles from a hat, and the IRS lets you write whatever.