Career Goals - Futures in Linux Careers
-
@nerdydad said in Career Goals - Futures in Linux Careers:
I see that there is KVM and LXD and Kubernetes and OpenNAP.
That's kind of a weird list of things to put together. Is that like a solution stack you want to try?
Anyways, I would recommend getting vary familiar with monitoring and metrics. That's something that you can apply to your current job. Learn how to create meaningful alerts from the data being collected. The industry needs more people who can do this kind of stuff with their eyes closed, and less cowboys who put it off as a 'nice to have some day'. So you might want to get familiar with some open source options so you have something up your sleeve no matter where you're working and no matter the budget.
In 5 years we might be dealing with the descendant of Kubernetes, but you might as well get your foot in the door now since that kind of shit is the future.
-
@flaxking said in Career Goals - Futures in Linux Careers:
That's kind of a weird list of things to put together. Is that like a solution stack you want to try?
Not these altogether. I have just heard of these technologies, want to explore them so that I am ready for the next iteration or 2 within the 5 years. I know that a lot can change within 5 years.
-
@NerdyDad I have the same goal and have had it for a few years. Everyone should know at this point how they learn best. For me it's a combination of reading books (The Linux Command Line: A Complete Introduction by William E. Shotts Jr. was absolutely fantastic) and playing in my test lab. Frequently on ML there are guides written by @JaredBusch which I basically dismantle as much as I possibly can. If I don't know what s specific command does or a modifier associated with it I consult the man pages. I also bug him a lot and ask questions regardless of how stupid they may come across. The point is to learn so you may get some harsh comments from some of the people on here. Just understand that the more picky and specific people are the more beneficial it is to you. That book is for Linux, not a specific OS (Fedora, Ubuntu, etc) so it applies to everything. It's an incredibly good starting point. After that the RHCE cert book is a good followup.
I don't bother @scottalanmiller as much as I have historically, but there has been years of contact almost daily with him mentoring me. This community is a great resource for specifically what you want. Only limited by your motivation.
-
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
-
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr.
The book is free
-
@aaronstuder Actually, its here.
https://sourceforge.net/projects/linuxcommand/files/TLCL/17.10/TLCL-17.10.pdf/download
Just one less click.
-
@nerdydad said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
There are commands that you will likely very rarely, if ever use. So I can't say that my memory is so good that I will never reference it again. However the need to reference it will go down the more that you play with stuff and the more experience you gain. IMO understanding a concept and applying it are the two sides of learning something. If you do both then you're golden.
-
@aaronstuder said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr.
The book is free
Yes it is. I personally don't like reading through extremely long PDF's, but everyone has their preferences.
-
@nerdydad said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
I used a command line book for UNIX and Bash in 1994 and have never used one since. I got the basics, now I just look up specific commands online.
-
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@nerdydad said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
I used a command line book for UNIX and Bash in 1994 and have never used one since. I got the basics, now I just look up specific commands online.
Yeah. Those books get quite complex though. Bash can do a lot as you know.
-
@wirestyle22 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@nerdydad said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
I used a command line book for UNIX and Bash in 1994 and have never used one since. I got the basics, now I just look up specific commands online.
Yeah. Those books get quite complex though. Bash can do a lot as you know.
BASH is a pretty basic programming language. It has very few constructs. Pipelines, standard IO, a few really basic data constructs, that's all that there is to know. It's a "learn in a day" kind of language.
-
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@nerdydad said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
I used a command line book for UNIX and Bash in 1994 and have never used one since. I got the basics, now I just look up specific commands online.
Yeah. Those books get quite complex though. Bash can do a lot as you know.
BASH is a pretty basic programming language. It has very few constructs. Pipelines, standard IO, a few really basic data constructs, that's all that there is to know. It's a "learn in a day" kind of language.
For you maybe. Not for me
-
@wirestyle22 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@nerdydad said in Career Goals - Futures in Linux Careers:
@wirestyle22 said in Career Goals - Futures in Linux Careers:
The Linux Command Line: A Complete Introduction by William E. Shotts Jr
From talking with you before, you've been working on this for sometime now. Do you continually reference this book or did you read it to learn and then never touched it again?
I used a command line book for UNIX and Bash in 1994 and have never used one since. I got the basics, now I just look up specific commands online.
Yeah. Those books get quite complex though. Bash can do a lot as you know.
BASH is a pretty basic programming language. It has very few constructs. Pipelines, standard IO, a few really basic data constructs, that's all that there is to know. It's a "learn in a day" kind of language.
For you maybe. Not for me
Likely you are thinking of something other than BASH then. BASH is very simple.
-
The hardest thing in BASH is learning the evaluation options, and those you just look up in a table.
-
Once you know > >> < | plus sourcing, if and for... you are basically done.
-
@scottalanmiller said in Career Goals - Futures in Linux Careers:
Once you know > >> < | plus sourcing, if and for... you are basically done.
With BASH, yes.
Learning
sed
orawk
are rather more difficult. You need to learn regular expressions, which aren't quite standard. Once you do learn them, shells and scripting are a lot easier and faster. -
@travisdh1 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
Once you know > >> < | plus sourcing, if and for... you are basically done.
With BASH, yes.
Learning
sed
orawk
are rather more difficult. You need to learn regular expressions, which aren't quite standard. Once you do learn them, shells and scripting are a lot easier and faster.Certainly, but those aren't BASH and are used identically regardless of the calling shell. SED is a text processor application, AWK is a competing programming language.
-
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@travisdh1 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
Once you know > >> < | plus sourcing, if and for... you are basically done.
With BASH, yes.
Learning
sed
orawk
are rather more difficult. You need to learn regular expressions, which aren't quite standard. Once you do learn them, shells and scripting are a lot easier and faster.Certainly, but those aren't BASH and are used identically regardless of the calling shell. SED is a text processor application, AWK is a competing programming language.
I know it's difficult to remember what a thread is supposed to be, but we're not discussing BASH here, but what someone should be learning.
I am guilting of using AWK as nothing more than a text processor most of the time, so it lives right alongside SED in my head.
-
@travisdh1 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
@travisdh1 said in Career Goals - Futures in Linux Careers:
@scottalanmiller said in Career Goals - Futures in Linux Careers:
Once you know > >> < | plus sourcing, if and for... you are basically done.
With BASH, yes.
Learning
sed
orawk
are rather more difficult. You need to learn regular expressions, which aren't quite standard. Once you do learn them, shells and scripting are a lot easier and faster.Certainly, but those aren't BASH and are used identically regardless of the calling shell. SED is a text processor application, AWK is a competing programming language.
I know it's difficult to remember what a thread is supposed to be, but we're not discussing BASH here, but what someone should be learning.
I am guilting of using AWK as nothing more than a text processor most of the time, so it lives right alongside SED in my head.
It was specifically brought up that BASH is hard and complicated and would take a long time to learn. My point was that it was not and that if he thought that it was, that he might be confusing other things (like AWK) with BASH. So it was totally the point.
And even if you don't think of AWK as a language, but as an application, that's till my point - it's in no way BASH. It works the same on PowerShell, on CMD, on ZSH, as on BASH. It's an application.
One of the things that makes BASH seem hard to people is they think that every application opened using the command line is part of the command line. It would be like installing some software on Windows, and confusing that with Windows. And if that application you installed was hard, thinking that Windows was hard because Windows was used to call it.
-
So mashing those things together derails people from learning, because they aren't even clear what they are using, what it does, where to find resources. It might see pedantic, but pedantisism is often the difference between finding the world simple and obvious, or hard and confusing. Learning BASH when you don't know what it is is really hard, learning BASH when you know what it is is really easy.
And there is a reason that books on BASH don't teach SED and AWK, they aren't BASH. And that's why there are books just for SED and AWK. You have to know which is which just to know which books to look to for answers.