4 ms·

I hope I'm not actually expected to know what any of those is.

• erkkie 13y ago
  If you're a developer and want to stay relevant I suggest you read up. With distributed systems becoming the norm rather than the exception, developers will need to understand how and where their code runs in production (and how it gets there) to be able to debug issues or write better behaving code.
  • agersant 13y ago
    This may be a simple oversight and I hope I don't sound too pedantic but you may need to broaden your definition of developer a bit. Developers who work on OS, games, embarked systems or professional applications (think CAD) are not very likely to need these anytime soon. More knowledge is always good so I'll check some out anyway!
    • clone1018 13y ago
      Vagrant can help developers who make OS and Games :). It can be used for simple testing on another OSes and environments.
    • erkkie 13y ago
      You're right, I should've narrowed the scope to client-server or perhaps "the web" (although the exact lines are blurry).
  • jimmaswell 13y ago
    are you saying the average developer is going to have to work with distributed systems in the near future (few years)?
    • erkkie 13y ago
      I would say there's a strong tendency towards that, depending on how one exactly defines 'average' and 'distributed'. Using a distributed datastore and/or a messaging queue in ones app is pretty common already, logical next step is for app components to follow the trend.
• vajrabum 13y ago
  If you're working or wanting to work as a Devops engineer or as a full stack engineer then you might want a new attitude about new stuff.
  • gaius 13y ago
    I currently work on an estate of thousands of unix hosts. We don't use anything on that list. Real engineering is not about jumping on bandwagons.
• pessimizer 13y ago
  It would take about an hour to be conversant in all of them.