@IRJ I think that's the polite way of saying "Snitches get stitches".

I've been programming since the late 80's. I can remember setting the time on my parent's VHS so they could record a TV show.

I can't believe I've been leaving that off my resume all these years!

So, I decided to stop pretending the test was respiring after the first couple of questions. However, I did keep my underwear on through the entire process and managed to pass!

This is a well organized and easily consumable gold mine of material for getting started with Linux. I regularly refer fellow students struggling with Linux to this post. Having the smaller individual posts for each subsection really helps with content retention and keeping things organized logically while tackling the material.

Seems like an issue that should be resolved with company policy, not some overly complicated overly engineered IT/IS solution.

You'll not really benefit from containerized workloads unless you are deploying applications that are designed to be ephemeral and stateless. Trying to deploy an application using a container the same way you deploy an application to a virtual machine, is not the way containers were intended to be used.

Containers should not be thought about in relation to virtual machines, they are two different things. Containers provide an encapsulation and abstraction of a service from the operating system. Containers are not a miniature virtual machine that you deploy your software on or to.

Check out the 12-factor App Methodology for a better explanation:

https://12factor.net/

Fantastic opportunity working in a generalist role for a growing engineering firm in Evansville, Indiana. The position is responsible for managing and supporting all aspects of the company's data infrastructure. Competitive pay, generous performance-based annual bonuses, and a great relaxed environment.

Some other perks of the work environment:

• Unlimited vacation
• Set your own work schedule
• Free coffee and soft drinks
• Work with engineers and be an integral part of developing a variety of new technologies

Position Description:

This position is for a full-time system administrator. Responsibilities include linux-based server administration, Windows
Server 2012 domain management , scripting support, database design, support, and management, and network
administration.

Position Requirements:

Bachelor’s Degree in a related field desired, specialized training or equivalent work experience acceptable.

Areas of Interest:

• Linux: Kerberos, LDAP, SAMBA, Apache, SSH, Virtual Machines (KVM, QEMU, Xen, VirtualBox)
• Scripting Languages: Bash, Ruby, Python, Perl, Powershell
• Version Control: Subversion, Git, CVS
• Networking: TCP/IP, DNS, DHCP, Ethernet, routing, VLAN, firewalls
• VoIP: Asterisk, SIP, GSM, FreePBX
• Databases: MySQL/MariaDB, Postgres, Microsoft SQL
• AWS EC2, DigitalOcean, Google Apps for Business

Ciholas Incorporated is located just outside of Evansville Indiana in the satellite community of Newburgh. They provide Electrical, Mechanical, and Software Engineering to a variety of clients worldwide.

For more information on the company please see, http://www.ciholas.com/

*If you have any questions please feel free to message me directly, post here, or send an email to [email protected].

The creator/author of the "Automate the Boring Stuff with Python" is giving away the course that he put together on Udemy for free until January 2nd of 2016.

https://www.udemy.com/automate/?couponCode=RESOLVE_TO_CODE_2016

@anonymous

How many Linux servers do you need?

All of them. You need them all.

@IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

For me, when I'm looking for a new role I tend to gravitate toward the type and quality of work and the quality of the company. Salary has been an important secondary concern in my last few positions, though I've been lucky enough that I haven't needed to worry much about that much due to demand for Cloud Architects and Engineers, and my flexibility as it relates to relocation. And most of the roles I have taken in the last five years have been somewhat innovative due to the nature of the work and the technologies being used (cloud-native services, serverless event-driven architectures, ML, etc...).

I haven't really cared about my title for quite some time now. I've had one role where my title changed seven times in less than 2 years. In the last five years alone I've been an Operations Systems Administrator, Systems Engineer, DevOps Engineer, Cloud Engineer, and Cloud Architect. Across all of those titles, I've done the same type of work with varying degrees of seniority, responsibilities, and focus.

When it comes to disclosing previous salaries I've been pretty open when I am actively pursuing opportunities. I'm not going to devote hours of conversation and meetings with an organization just to find out the pay and benefits are not where they need to be. That's disrespectful of their time, and a waste of mine. I'll usually discuss that within the first couple of meetings with a recruiter or HR representative, and if appropriate I disclose it without prompting. I've not had a circumstance where it has had a negative result, and in the most recent offer I accepted (last week) I think it helped. In the right situation, I think it is an easy and low-risk means of establishing an open dialogue of trust. Now if a recruiter is contacting me about a role out of the blue, I rarely give out my current salary or even an indication of it until I've had time to research the opportunity. And I can't recollect having anyone outright ask me for my current salary.

@scottalanmiller Yep, I just wanted to share the configuration I use as my daily driver because it makes working in the terminal that much more efficient. The OP mentioned wanting something that was a bit slicker and more powerful, and I think in addition to your choice of terminal, your choice of shell and other tools contributes to having a better experience. I prefer FISH for my shell, and tmux is my terminal multiplexor of choice. ZSH is another great alternative shell as well.

@Obsolesce

The idea of managing that many "Snowflakes" inspires both rage and uncontrollable anxiety.

I'll take 10,000 cattle any day.

I primarily work from a MacBook Pro and use a combination of the following:

• iterm2
• tmux
• FISH shell

@IRJ All that said, I hate touching/managing servers.

@IRJ Absolutely. I mean, blending the skillsets is hard approaching the role from either perspective, but understanding how software runs on infrastructure is super important; especially as more and more automation and code replaces the traditional admin duties going forward.

@IRJ I'm just saying don't sell yourselves short. A lot of "DevOps" engineers that consider themselves as having only an Infrastructure skillset are practiced Software Engineers. Its something that almost happens organically as a result of being put into the role.

@IRJ The newest approach that AWS is starting to push is a declaritive language that generates CloudFormation from code.

The Cloud Development Kit (CDK)

It is conceptually similar to stacker, but a bit more complex. It can reduce template size by up to 70%, and allows you to do conditional provisioning of resources without the added complexity of nested conditions and inflated parameter hell.

And developing a Custom Resource for Cloudformation usually involves Software Engineering, as it is either backed by a Lambda function, Application, or considerably complex architectures triggered via SNS.