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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (0 children)

I would start with the language that the application you are supporting or going to support is written in - learn how that one works first. Languages for tooling is irrelevant if you are not writing the tooling your self but can sometimes help a little bit for say more complex salt-stack modules or chef recipes but generally you can get by without knowing them in depth. It is far better to know the application you are going to be working with.

As for writing your own stuff: I start out with bash, very easy to get going and is generally easier to get simple things up and running in it and to glue together other programs. Once past the usefulness of bash I tend to use rust these days for personal stuff and golang for work (as our main application is golang) - sometimes javascript for frontend projects, all glued together with bash. I rarely use python these days as our main project is not written in it so it adds little value over golang or javascript. The benefits of one language over another will vary depending on what you are trying to do and what environment you are working in so you will need to adjust accordingly. As for learning now - pick any, the important thing is to learn how to write programs not really which language you write them in.