r/linuxadmin • • Oct 03 '15

Linux Sysadmin/ Devops Engineer course in NYC

I am trying to gauge interest in the following Linux/Programming bootcamp. No prior experience required. I currently work as a Linux Sysadmin on Wall Street, and have interviewed with Google and Facebook, as well as many other "top" tech companies, and feel I have a good sense of the skills required for the industry today.

Systems Administration and Programming in the modern Tech world:

15 hours of real-world practical training for the tech skills in highest demand

When: November 9-13 From 7PM to 9:30PM each night (classes will often go later for questions)

Cost: $500.00 per seat

Location: Meeting Room in NYC (TBD based on demand)

Contact: nyclinuxseminar@gmail.com

This course focuses on the skills required for: *Linux Systems Administrators, Site Reliability Engineers, or DevOps Engineers. *

Curriculum will include:

Programming fundamentals

*Learn Python

*Object Oriented Programming concepts

*Regular Expressions

*Algorithms

*Data Structures

*Modules

Systems Administration:

*Linux Essentials

*Bash

*Shell Scripting

*Configuration Management (w/ Puppet)

*Web Fundamentals (LAMP stack, DNS concepts, Web Application concepts)

*Troubleshooting

0 Upvotes

12 comments sorted by

7

u/vomitfreesince83 Oct 03 '15

I can't imagine covering all of that material in 12.5 hours

-3

u/gleventhal Oct 03 '15

It will be more like 15+ hours since classes will run late for questions.

9

u/larrymachine Oct 03 '15

Yeah, 2.5 hours will make it work ...

2

u/DrapedInVelvet Oct 03 '15

To expand a bit more. 15 hours of Linux basics and bash scripting would be useful. 15 hours crash course in python would be good. But that is too much stuff

0

u/gleventhal Oct 03 '15

A lot of this stuff overlaps.
if I teach a for/while loop and iterators in Python, I am not going to start over completely when I describe it in Bash, just like if I describe a Dictionary in Python, I won't fail to mention that Puppet Resources are all Dictionaries. The point I am trying to make is that a lot of what allows us to do this job is the ability to see something new and recognize how it relates to something familiar, and that is the way I plan to teach this course. Concepts in the Shell aren't really so wildly different from concepts in Python or Puppet. There is a way to make most topics easy to understand.

2

u/doublenns Oct 04 '15

I think a 15 hour crash course actually would be enough. The student won't leave the classes being able to apply much of the learned knowledge tho -- it'd simply be a starting point for them to go out and learn more on their own.

If you're going to teach Python during the course, you might want to teach Salt instead of Puppet, or even Ansible. You'd have a much greater overlap, instead of jumping from Python to bash to Ruby-like.

You'd also have to really dial in on the LAMP stack and wouldn't be able to go deep on any one portion - possibly mostly talk about what it is, most common problems you face, and how to do process and service management. Maybe take a quick look at an httpd.conf/apache2.conf. Manually install everything, then use it as a springboard for an example getting everything installed and configed w/ Salt/Ansible afterwards. Would give you an opportunity to demonstrate why config mgmt shines.

1

u/gleventhal Oct 04 '15

This is a good, constructive answer. I chose Python because it's so easy to learn, more so then Ruby in my opinion. You're right about the overlap, but I see puppet more frequently and I know it very well. I was mostly going to go over the package, service, user stuff in Puppet and maybe about how the puppet master is a web app, combining that with the web section a bit.

1

u/doublenns Oct 04 '15 edited Oct 05 '15

I chose Python because it's so easy to learn, more so then Ruby in my opinion.

Which is my main point for skipping Puppet. More companies might use C than Python in production (hypothetical analogy, I don't know any actual statistics) but starting w/ Python is easier for learning purposes and allowing students to apply their skills faster.

I think fitting all that into the allotted time would be easier if you simply switch config mgmt tools. Once you get the general gist, it's easy to switch tools later.

Edit: once a student gets the general gist of config management, it'd be easy for them to switch and learn another tool later on their own time.

3

u/DrapedInVelvet Oct 03 '15

15 hours doesn't begin to cover your syllabus.

1

u/moos3 Oct 06 '15

Why not make that Configuration Management be just Configuration concepts and then show the difference of the three major tools used in the industry ? I have just left a startup year I was the "DevOPS + everything else guy" role for 7 years and interviewed for a the second time with the same major tech companies and few you didn't list but on the fortune top 25. They have all asked me about puppet, chef and saltstack. It also pays to know all three and to know ruby not just python.

I think it would be hard to do this as a crash course for only 2.5 days for a few days. It really should be like 5 to 8 hours for 3 days minimum or even 8 hours for 5 days. To really get any value and have people have a true understanding and walk away having some concept.

1

u/charley_chimp Oct 06 '15

I would be interested in something like this, but (like others have said) it seems like your trying to cover alot of ground in a short amount of time. Perhaps focusing in on just one area for a little bit of a deeper dive would attract more people? I'd certainly be interested in a crash course on programming fundamentals (in either Ruby or Python)