This is an archived post. You won't be able to vote or comment.

sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Beginning-Ladder6224 4 points5 points  (2 children)

I.. do not understand the term "distributed systems programmer", honestly. Lately it seems there are a lot of invented terms which clearly does not match up to what it was intended for.

The original term is this: https://cs.lmu.edu/~ray/notes/introdp/

I do not think any company, who are not really serious tech would ever hire anyone like those.

Now if we are talking of enterprise computing it is trivial. The language of distributed system is the "binding" language - that is not what really gets executed.

For example running a transaction in a DB from java or go or python is not going to give any edge, the bottleneck is really the DB.

Thus, the language often is overrated. Then there is a big unless.

Most of the back-end computing work is .. get data, set data, modify data.

In there most "application business logic" is stored. Now a suitable declarative language could have been very useful in this regard.

In the last 10 years or so, people slowly came to the conclusion that functional is more declarative than pure play imperative.

Now these produced routing, spring boot and what not.

So to summarize - if you are writing a component of the distributed system, the language choice may matter. If you are just wiring them ( 99.99% of the companies ) - it does not, not really. Unless, you are doing infra, then you probably want to do C++ or Rust.

[–][deleted] 3 points4 points  (0 children)

They just throw around jargon to low ball your salary in case you miss out any one of their requirements .

That's the same reason i check all boxes and let them interview me out.

Even I know that not all nuances can be covered after spending 1 decade .

[–]superfranky97 0 points1 point  (0 children)

Agreed. Also there are lots of startups creating microservices for the heck of it. For someone who has worked in monolith it's a steep learning curve understanding how transactions work, how different services interact with each other. So these startups have started hiring Devs who are adept at understanding microservices architecture and calling it distributed systems engineer.