Hello,
I'm new here.
i hope this is the right forum to post my question, sorry in advanced if it isn't .

A little bit about me
I'm a physics major and soon my second semester of college will start.
I have been advised a lot that I should have a backup plan if things should't work out with physics. So I took up programming,, and now my interest has turned towards linux.
I know c, c++, basic python. I have certification of c and c++.
I have enrolled in a 4 month program which prepares me for red hat system admin and red hat engg certificates.
After this I plan to take a course in advanced bash scripting. I've also done the linux foundation course on edx.

My question is
1.)Thinking practically,, is there something else I should look into?
2.)How does my future look with this background assuming I finish with advanced bash scripting before august 2015?

My physics degree is 3 years. I'll be graduating in April, 2017. But after 4th sem, I wont have enough time to study this stuff cause I'm gonna have to be part of undergraduate research, so less time.

So the most important question is what else should I look into after RHCSA, RHCE and scripting to have a sufficient qualification for a good job?

..and the answer to this is the same with physics or any other field of study: there is NOTHING you can do that will get you a good job. Sorry, but that's just the way it is. There are so many people with RH* 'certifications' that have no idea what they're doing, that the 'certificate' is next to meaningless for many (myself included). And bash scripting isn't anything that's going to help you stand out in the *nix world, since pretty much EVERY sysadmin is going to know it.

If you want to be a programmer, then study programming...a meaningless 'certificate' (RHCSA, RHCE) won't matter for programming jobs, since they are for ADMINISTRATORS. No matter WHAT your qualifications are, it boils down to EXPERIENCE...LEARN Linux. Know what makes it work, how to troubleshoot problems, and how to code correctly. Write code that DEMONSTRATES this, and publish it out on any of the Open Source sites, so that potential employers can look at it, and see how you code and document things. Being able to code is one part..being able to communicate how that code works, how to install it and how to troubleshoot it is another. And when you DO manage to get that first job, it'll be the same as it would be in physics; bottom of the ladder, doing basic work.

1 members found this post helpful.

You hit me hard with the realistic hammer.

THIS IS WHAT I NEEDED THANK YOU.
I need some more information please.
I don't seem to understand what you mean by code properly and show people how you code and document things.

Write programs to solve problems or to get a job done? And explain how your code works.
Isn't that just programming?

Welcome to real life. If you think you're going to graduate and get handed a job in ANY field, you are in for a VERY rude awakening. There is no amount of certificates, diplomas, or anything else that makes things easier.
So what's unclear about this?? "Code properly" means write clear, concise code, that's well commented so it can be maintained, and have that code with as few bugs as possible. "Document things" is even more clear....how do you INSTALL that program? How do you troubleshoot it? What changes have there been between version 1.x and 2.x, for example.
Sure is....which is what you asked about. So, proceed.

1 members found this post helpful.

Hi,

I really think one can prepare for their future by using qualified educational methods. Proving their abilities by use of standard works that others have molded or formed is one way to educate to prepare for the everyday tech world. We have hundreds of schools that do prepare individuals for their desired career fields. Sure experience will enhance any education one gets on the job. I believe graduate degrees, certificates do have worth to everyone involved.
I agree to some of what you stated. Most programmers are not good technical writes nor communicators. Commenting code should be for everyone, I do comment so I can view the code and see what was to be performed plus showing me the state so I do not need to re-read the code to understand what is being done to get the result(s) at any given point. I have seen some programmers' comments that were to deep and just made things worse. One should provide a picture/state of the program at the point of comments. Obvious states do not always need a comment. Common sense comments should be used along with expalination of intrinsic conditions at the point of the comment.

I will not discourage anyone from gaining knowledge be it from a certification or extended education. One should not depend on just education but find the means to enhance your education within your chosen career field by adjoined working within that career whenever possible. Academia in any form will not fulfill the complete needs for employment but should allow you to open doors into that field when you present yourself properly to a future employer.

Hope this helps.
Have fun & enjoy!

1 members found this post helpful.

I'm sorry to disagree, but schools and certifications don't prepare you for a career. While you may learn some of the skills needed, the school/book work does NOT correlate to actual work experience. The day-to-day work is FAR different than what you learn in a classroom.

The point I was trying to make, was that any 'certifications' (which I give VERY little weight to) and diplomas aren't going to set them apart from anyone ELSE in their graduating class. Because who among the graduates DOESN'T have a diploma? You are now one of thousands of others, who took the SAME standardized tests, sat through the same labs, took the same certification tests, etc., and passed them. So, anyone in that set needs to have some actual EXPERIENCE to point to, for me. What did you write? Why? Have you ever done ANY work (paid or not) in the field where you're applying?
Well, I'm not saying they should be technical writers, but they SHOULD be able to clearly communicate. Whether the phrasing can be tidied up or not is immaterial. I'm talking about the README docs that go with the code, and basic communication. Comments should be as clear as they can, and should be used liberally. Something like "/* The user name */", tells someone next to nothing. "/* The user name, from xxx routine/variable/command-line/module, lower case only */" has some meat to it. It tells a maintainer where to look for that variable, where it's coming from, and some details about it.
I don't discourage certifications either, but given the number of people I've talked with/met who were 'certified', and who had NO idea what they were doing, I give them very little weight. A quick glance around this site to the number of people with 'certifications', who clearly don't know the basics is a good reason why.

I do agree with you, in that an education should never, EVER stop...but you don't need a certificate for it. Keep pushing forward every day, OP...learn more, research, read, and figure things out. The depth of knowledge you get from that will be far greater than anything you'll get from a book.

1 members found this post helpful.

Okay,, first of all sorry for the delay.

Well I got confused,, now its clear, thank you.

Well I read more on this topic in the forums. There's some weight to both the sides.There's no point in certification if its certification alone, So getting certificates is only useful if I can prove myself. Since there are people who have the certificate and know nothing, the value of certificate is very little compared to the knowledge and experience I can get and I have to get it by myself. There are nothing that can get me that except my own efforts and that's exactly what the employers seek.I'll study hard. I'm installing arch linux soon. It'll hopefully make my learning curve steeper than ubuntu.

Also TB0ne,, can you give me some head start as to where I can get information about those open source websites you mentioned?
Where I can publish my code and people could possibly review or comment. It would help a lot,,Thank you

Don't misunderstand me...a formal education is not a bad thing, nor are certificates. But this forums is absolutely LITTERED with people saying things like "I'm new to the linux, and want an RHCE!". This typically indicates they're going to buy a quick-study book, grab an ISO image of RHEL, and muddle through a test, to get 'certified'...and they will know VERY little about what to actually DO.

Learning is a process; unless you know how to APPLY the knowledge, it's fairly useless. To look at it another way, you could go online right now, and get VERY detailed pictures, videos, and all the info you need on the human heart. You could memorize EVERYTHING about it...but do you think you could then perform an operation? No...you would lack the hands-on, day-to-day knowledge of how the entire SYSTEM works. This is the same thing...there are THOUSANDS of things an administrator does on a day-to-day basis. Perform that kernel upgrade? Sure, go for it! It's an automated patch, what's the harm right??? Until the Oracle DB deadlocks because that patch wasn't certified with that version of Oracle....and so it goes.
Start with Google, and begin researching things for yourself. Sourceforge is only one place, Google code is another....there are THOUSANDS more open-source projects you can contribute to.

1 members found this post helpful.

Hi,

If you want to participate with a open source project then that could be one way to get some mentoring/hands on experience. You will have to start at the lowest rung of the ladder but once you prove your worth then things should open up or allow you to move within that project. Not to say that the days of basement banging would not produce a valuable piece of of code or project. You still need to hit that niche or as some writers will say 'Hook' that whale.

Prepare yourself for endeavors down the road, you do not pick up a guitar and just start strumming your way to success. Background preparedness will go a long way. How much you really want to get into coding will determine your worth by how much drive you actually have to produce success. Mentors hopefully will assist you into arenas' that will produce the desired successes. Prepared awareness will help you when coding, investigate everything relative to your desires.

Remember to have fun so that you will enjoy the experiences through growth in this chosen field of study.

1 members found this post helpful.

I understand what you're trying to tell me. Nothing comes easy. I realise it Its just hard to accept that fact.

Well Google pops out results like 'top 100 open source websites'. So it's really hard to decide for yourself which are the good ones.
If a list can be made of 100 rankings then I guess there are uncountable websites.
I'll look into those two,, thank you again.

Thank you.
That's the plan thank you for all the advice.

I'll add to reputation after a day or two. Android app has lesser features.

I recommend that you take courses in networking and database.

---------------------
Steve Stites

1 members found this post helpful.

I don't exactly know what type of things I'll be doing in networking or database. I'll do some research and find out.
Thank you for the suggestion.

For many years, I taught at one of the largest community-college systems in America ... a system that has more than 10,000 students every night. Most of these students have four-year degrees: one student in one of my classes was a tenured PhD professor from the University. They're not "going back to school." They're availing themselves of an educational resource; the opportunity to spend time in a classroom, interacting not only with the instructor but with their peers.

Frankly, I suggest that you should never stop doing that. (Also remember that community colleges are always looking for adjunct-faculty instructors!) Teaching was tremendously educational for me, and I plan to resume doing it soon.

But you also need to keep things in perspective. Education does not attempt to match "the real world," but rather to help one prepare for it and to augment it.

"Certifications" are simply a form of continuing-education ... and if you focus upon the instruction, not merely the piece-of-paper, you can get many good things from it. (But, never a "Golden Ticket.™") If you simply focus on the piece-of-paper and on "passing the test," you will get absolutely nothing from it. If you approach it with the assumption that it will cause employers to beat down the doors to hire you, then you're wasting your money, your time, and your dreams. You'll be tossed onto the reefs of Cape Disappointment.

I would also caution you that, if you do pursue a certification, your employer should be footing the bill ... in exchange for your promise that you will continue to work for them for so-many years thereafter. Your employer should be investing in you, and you should be returning that investment. During your classroom time, you should be looking at the bigger picture ... at the entire subtext that the course is intended to teach ... not merely at guessing whether the "right" answer is A, B, C, D, or E. Ultimately, all education is self-education, and you get out of it no more than what you put in.

Never stop "going to school," and fuhgeddabout the pieces of paper unless you just have empty wall-space.

2 members found this post helpful.

Goodness, goodness

Two diametrically opposite opinions and I find myself in agreement with both of them......
I probably need a nap.