|
It is very common around here to ask for a degree in job description, but with a long and proven experience it never really matter...however lately CVs are 'read' by software and if no B.A. in it it will be dropped by the software, so there is a dilemma...
The best way I found is somehow get contact with the HR directly and let my CV seen by humans...
(Just saying, that learning for the parer will probably kill you  )
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
School isn't worth it.
It takes lots of time, effort and money.
It sucks the energy out of you.
It doesn't actually teach you stuff you need.
The stuff it does teach you could've Googled when you needed it.
School is a slow way to learn.
I've met IT graduates who literally couldn't declare a variable in C#.
School always lags behind with reality. You'll probably be doing some old version of Java (don't do anything else either, because the teacher won't understand it).
You'd better find a new job if they value four years of schooling over 22 years of experience.
I may be a bit biased as I always hated school.
I liked programming really very much until I decided, like you, to go back to school.
Only now, after having done little schooling for about a year, am I finding my enthusiasm and curiosity is coming back.
If I ever start to hate myself and rather be brain-dead I'll go back to school again.
|
|
|
|
|
I also hate school too but employee requires degree as they control what pay to give and chances for promotion and not everyone is lucky. I have to beat HR and recruiters as they only recognizes degree 
|
|
|
|
|
Seems like your beginner luck has ended then 
|
|
|
|
|
agree, time to go back to school to get degree and be a junior developer/software engineer for degree batch after degree. FYI degree and non degree benefit is different even if is same position of junior.
modified 17-Aug-16 19:08pm.
|
|
|
|
|
The more stuff you have in your arsenal the more chances you have in life. Sometimes we are given a signal about how things may be in the future. There's a chance that the signal can be ignored and all will be fine. It is always better to respond if you are able. If a degree rules you out of consideration for many jobs now then speculate on how things may develop down the road. There are many people today who are unemployed because they did not heed these indicators and fell behind when the competition become very tough.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
I have over 25 years of experience in designing embedded systems, and yet I found I couldn't break into the medical industry without a degree. It was best explained by an HR manager like this:
If I designed a small sub-system of a product, and designed it perfectly, documented the firmware, got it past V&V no problem, but another part of the system failed leading to either serious injury or death, I could be called to give a deposition. One of the first questions I would be asked would be where I earned my degree. If I had no degree, they would blame the failure on the "uneducated" so called "engineer". So at the ripe old age of 56 I went back to school, got my associates, got several contract jobs in medical and now working on my bachelors. It's painful sometimes, but so far worth it.
|
|
|
|
|
demotis wrote: So here is the deal. I have 22 years of experience in IT, with the last 15 in software development. I'm up to date on many of the latest technologies and constantly learning new things (thank you Code Project for your help with that). I have recently started looking for a new job after having worked at a place for 7 years doing C# .Net programming with a hint of PHP/HTML.
With that amount of experience, I would say you're far better qualified than any new graduate, no matter how good their degree.
I dropped out of university over 30 years ago, and although the first couple of jobs were hard to get, and quite low level, once I had a few years experience most of the companies I applied to were very keen to take me on. I can't recall any of them questioning my lack of a degree when compared to even a few years of relevant experience.
It's quite likely the companies you're looking at simply put that clause in to discourage young, inexperienced, applicants. I'd recommend applying, and making sure your CV / resume emphasises your depth of experience.
eta : any employer who insists on a degree (as seems to be the case, reading more of the thread) and will pay an inexperienced graduate more than a seasoned engineer / developer isn't the sort of company I'd consider working for...
Days spent at sea are not deducted from one's alloted span - Phoenician proverb
|
|
|
|
|
molesworth wrote: ... any employer who insists on a degree (as seems to be the case, reading more of the thread) and will pay an inexperienced graduate more than a seasoned engineer / developer isn't the sort of company I'd consider working for...
I have decided to go ahead and get a degree in CS with a emphasis on Programming. Actually, I'm going to get just enough to be a Computer Science, but I'm going to concentrate on Theory so I'm not bored to death making "Hello World" programs and having to explain the difference between an object and Class.
With that said.... You are 100% right. A 4 year degree with 3 years experience? In a best case that's only 7 years experience. I got double that, and mine is real world, on the job experience. But, apparently we are in the minority.
|
|
|
|
|
Consider a Master's Degree. I got mine from Missouri State.Computer Information Systems Graduate Program - Computer Information Systems - Missouri State University[^].
The program was a mix of on campus and online. It took 2 years with 4 weeks on campus plus lots of nights and weekends. But at the end (and I have kids and worked full time) I had a Masters in Computer Information Systems. That degree opened up several doors for me when getting employed. Tuition wasn't too bad, so I paid out of pocket
Good luck!
Hogan
Hogan
|
|
|
|
|
Having been on the other side of the conference table here's what I've seen. In the embedded programming world, and granted it's a bit different from normal programming, there are so many resumes a degree is used as a first order filter (electronics, part of that embedded difference) in selecting who to interview. A BA is better than nothing but for a tech job it really has to be a BS degree, unless it's a tech writer or customer training position.
Equivalent experience is just a dodge to avoid legal hassles for dicrimination. HR puts it in there but it rarely has any relevance to the hiring process. Does a degree actually make a difference otherwise? Only for an entry level position. A senior position is all about experience, because we know technical knowledge has a short half-life.
In interviews I started with a couple tech questions, just to eliminate the resume inflators. After that I was more interested in the non-technical skills, things like communication skills (writing, speaking up to express opinions) and some understanding of the economics of commercial software, the importance of project management and the aility to think beyond the assignment for next week.
And that's where the degree does make a difference. Going to a university or college is more than job training, it's exposure to a variety of disciplines. A code bootcamp can teach someone to write code, but it doesn't teach the ability to extrapolate from the immediate into the abstract. Software is more than writing code (yeah, blasphemy!!), it's economics, politics, sociology, and even psychology when you have to climb into someone's head to reverse engineer undocumented legacy code.
Does the 15 years experience count? Sure, but you have to get out of the pack before anyone looks at it. If the degree comes after the experience, no one really cares, because you won't be applying for Grunt Programmer I job classifications.
So if you do go back to school, take some theory classes, Numerical Analysis, Queueing Theory, Finite State Automata, but don't neglect Economics and English, especially writing. At a senior level you have to communicate your ideas in an effective manner to both management and your junior team members.
|
|
|
|
|
This actually makes a lot of sense. in the short amount of time this post has been out I have resolved myself to enroll for one of the online degrees. I've sent in my info and have requested my transcript from when I was in school back in the early 90's. I hope that at they can count some of my credits.
It is a great idea to take theory classes. I was thinking that I would need to take "Intro to Programming" and start from the bottom, but it is perfectly logical that I could take some theory classes to get a BS and then back it up with my real world experience.
Thanks for the insight.
|
|
|
|
|
I definitely fall into the don't need an education camp, based on my 38 years experience in the field. However I was fortunate enough to earn a degree early on, and along the way fell into the defense industry. In that industry hiring companies must have relevant degrees so that they can slot you into a defense contract. Many contracts for skilled labor don't include categories for non-degreed personnel. You have to fit into one of the contract slots so that the company can get paid. They make their money off of the difference in the contract category payment per hour and your salary. So depending on the industry you're applying for its something to consider as you make your decision. Just offering a different perspective than what I've seen here so far.
|
|
|
|
|
If company wants you to have a paper and sneezes at your experience, you don't wanna work for them. Really, you don't. You would regret it from day one of employment.
|
|
|
|
|
This almost has to be measured person-by-person depending upon your background, skill level, and career goals; however, you make one large assumption that may not be true - that school will teach you things you already know. I know plenty of people with over 20 years of experience that are mystified by "memory overflow" errors. Those individuals never took the time to actually understand the underlying principles of what they did and it held them back. That said, school is expensive and time-consuming. It will require tremendous dedication on your part to fulfill the degree requirements and work full time (if that is what you are planning to do). I followed this path myself many years ago and I didn't regret it, but I also look back and wonder how I managed it all working full time, taking 2 classes per semester, and raising a young family.
|
|
|
|
|
It so much depends on yourself - what you have learnt through those 15 years. I've met quite a few non-academics who have learnt what to do, but with a very vaugue understanding of why they have to (or ought to) do it that way. (As in Geek & Poke: TDD [^].) I was teaching for a few years at a tech college, where we had a terrible time 'deprogramming' some of those self-educated guys coming to us for a degree, 110% confident that they knew all the 'right' ways ... that were not.
Then there are those who have learned from their experienced colleagues, and picked up the good practices, and also know the real world problems to be solved (which those coming directly from high school certainly do NOT). They can be the finest students there are, worth their weight in gold, especially in group projects, and even at lectures, asking exactly the right questions to pinpoint the essentials.
When young people ask me for advice about education, my recommendation is: Get yourself a lower degree to learn some academic principles and methods, and quite a bit about practical work, 'the craft'. That ensures that you, according to a systematic plan, have been 'diciplined' to solve problems in a reasonably orderly manner. Here in Norway, we have these three year engineering schools not classified as universities; they educate engineers to do engineering, not to do paperwork.
Then go out and see if you can handle it well - you probably can. If you are an academic by nature, you will often ask yourself lots of 'why's, you would like to know the underlaying ideas and concepts for everything from design methods to code patterns to whathaveyou. Then, after a few working years, you enter a university to learn the theory, the principles. You have the background to understand why, to ask the right questions, to know how to apply the theoretical knowledge - for all of this: in contrast to your fellow students who haven't had a single working day within that professional field. You will gain a tremendous lot more from the academic theory than they will, because you will know why.
But you don't have to know all the theory. I have had colleagues with 3 year basic engineering only, but their mind has been so 'academic' that the have picked up more than enough of the theory on their own. And they have been truly excellent practitioners of the trade.
Your case is one level below at the academic scale: It is not putting abstract theoretical principles on top of a lower degree plus work experience, but putting a lower degree on top of work experience alone. The difference isn't essential. If you do a lot of work mostly because you know that's the right thing to do, but you don't know why, and that bothers you somewhat, then you definitely should go for the bachelor. If you either say 'Well, I know what to do, and that is good enough', or you say 'But I do know all the 'why's!', then you probably would benefit far less from going back to school.
If you are of the self-taught kind that has not been guided by more experienced colleagues, then you probably could benefit a lot - and it might be painful. I tried to teach my students a number of good principles, and a couple of the self-taught ones handed in coding exercizes of fairly good coding quality, headed by a comment line: "This is how the professor forces us to solve the problem:" - and then followed an alternate code block of really messy code, all commented out and with a heading: "And this is how a real programmer would do it: ...". I smiled, recognizing that they at least had learned the good principles, even though they explicitly rejected them. Hopefully they wouldn't be as much in opposition when getting out into the open world.
So it all depends on what you know, your attitudes and work patterns. If you present a few thousand code lines that you have written, would reveal a lot. Having you explain the architecture, the modular structure, of some large system you have been working on, would reveal a lot. Having you explain the principles behind the design of the internal module interfaces in your system would reveal a lot.
You don't go to U to learn the syntactical details of another programming language. You go to learn the concepts of programming languages in general, so that you later can handle all sorts of languages. You learn priciples of graphics programming, not one specific plotting library. Etc. etc. If you know C#, PHP and HTML, but you have no clue about XSLT, how to write a parser, or algorithm complexity, then maybe a bachelor would be a good idea. Unless you say 'I will never need to write a parser or use XSLT, and the CPUs are fast enough so algorithmic complexity is irrelevant', of course.
(Bonus story: A fellow student of mine, in one of his first job assignments had to make use of his parser programming abilities to parse bacteria(!). More specifically: Writing code for automatically classifying microscope images of bacteria of different types. They defined a BNF syntax for images of each type, and parsed the image according to the BNF. Identifying bacteria type A or type B is like identifying a 'while' loop or a 'for' loop - same method, even though the 'tokens' were graphical elements rather than textual symbols. If he hadn't know the idea of a tokens and parsers, of formal grammars and BNF notation, he would have had a hard time in that project! This is the kind of background you get at a U, but rarely in a programmer position in some arbitrarty company.)
|
|
|
|
|
It so much depends on yourself - what you have learnt through those 15 years. I've met quite a few non-academics who have learnt what to do, but with a very vaugue understanding of why they have to (or ought to) do it that way. (As in Geek & Poke: TDD [^].) I was teaching for a few years at a tech college, where we had a terrible time 'deprogramming' some of those self-educated guys coming to us for a degree, 110% confident that they knew all the 'right' ways ... that were not.
Then there are those who have learned from their experienced colleagues, and picked up the good practices, and also know the real world problems to be solved (which those coming directly from high school certainly do NOT). They can be the finest students there are, worth their weight in gold, especially in group projects, and even at lectures, asking exactly the right questions to pinpoint the essentials.
When young people ask me for advice about education, my recommendation is: Get yourself a lower degree to learn some academic principles and methods, and quite a bit about practical work, 'the craft'. That ensures that you, according to a systematic plan, have been 'diciplined' to solve problems in a reasonably orderly manner. Here in Norway, we have these three year engineering schools not classified as universities; they educate engineers to do engineering, not to do paperwork.
Then go out and see if you can handle it well - you probably can. If you are an academic by nature, you will often ask yourself lots of 'why's, you would like to know the underlaying ideas and concepts for everything from design methods to code patterns to whathaveyou. Then, after a few working years, you enter a university to learn the theory, the principles. You have the background to understand why, to ask the right questions, to know how to apply the theoretical knowledge - for all of this: in contrast to your fellow students who haven't had a single working day within that professional field. You will gain a tremendous lot more from the academic theory than they will, because you will know why.
But you don't have to know all the theory. I have had colleagues with 3 year basic engineering only, but their mind has been so 'academic' that the have picked up more than enough of the theory on their own. And they have been truly excellent practitioners of the trade.
Your case is one level below at the academic scale: It is not putting abstract theoretical principles on top of a lower degree plus work experience, but putting a lower degree on top of work experience alone. The difference isn't essential. If you do a lot of work mostly because you know that's the right thing to do, but you don't know why, and that bothers you somewhat, then you definitely should go for the bachelor. If you either say 'Well, I know what to do, and that is good enough', or you say 'But I do know all the 'why's!', then you probably would benefit far less from going back to school.
If you are of the self-taught kind that has not been guided by more experienced colleagues, then you probably could benefit a lot - and it might be painful. I tried to teach my students a number of good principles, and a couple of the self-taught ones handed in coding exercizes of fairly good coding quality, headed by a comment line: "This is how the professor forces us to solve the problem:" - and then followed an alternate code block of really messy code, all commented out and with a heading: "And this is how a real programmer would do it: ...". I smiled, recognizing that they at least had learned the good principles, even though they explicitly rejected them. Hopefully they wouldn't be as much in opposition when getting out into the open world.
So it all depends on what you know, your attitudes and work patterns. If you present a few thousand code lines that you have written, would reveal a lot. Having you explain the architecture, the modular structure, of some large system you have been working on, would reveal a lot. Having you explain the principles behind the design of the internal module interfaces in your system would reveal a lot.
You don't go to U to learn the syntactical details of another programming language. You go to learn the concepts of programming languages in general, so that you later can handle all sorts of languages. You learn priciples of graphics programming, not one specific plotting library. Etc. etc. If you know C#, PHP and HTML, but you have no clue about XSLT, how to write a parser, or algorithm complexity, then maybe a bachelor would be a good idea. Unless you say 'I will never need to write a parser or use XSLT, and the CPUs are fast enough so algorithmic complexity is irrelevant', of course.
(Bonus story: A fellow student of mine, in one of his first job assignments had to make use of his parser programming abilities to parse bacteria(!). More specifically: Writing code for automatically classifying microscope images of bacteria of different types. They defined a BNF syntax for images of each type, and parsed the image according to the BNF. Identifying bacteria type A or type B is like identifying a 'while' loop or a 'for' loop - same method, even though the 'tokens' were graphical elements rather than textual symbols. If he hadn't know the idea of a tokens and parsers, of formal grammars and BNF notation, he would have had a hard time in that project! This is the kind of background you get at a U, but rarely in a programmer position in some arbitrarty company.)
|
|
|
|
|
BA degrees aren't special, that requirement is just used as an applicant filter. In this case, your experience trumps the degree requirement many times over, so if you've been practicing many of the technologies they need, apply anyway.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
It seems most self-tough developers know about 98% of what need to develop most software application. It is the last 2% that employer are after with developers with college degree. Those 2% are the abstract theories, algorithms, patterns, politics, and communications. It is those with the extra 2% that develop compilers, operating systems, and library frameworks to be use by others.
Getting a BA/BS in computer science will give you that extra 2%.
|
|
|
|
|
As you say: 98% of the 'what'. Far less of the 'why'.
'Develop compilers' - you don't have to develop a compiler to need a parser. Very few self-taught programmers can write a decent parser (or define the grammar of the input), not even a recursive-descent one. But we need it all the time.
Anyone can make their function publicly available as an API. That is not to define a decent module interface. Anyone can declare a struct or a class, but defining the right structure of object classes is a different matter. Choosing a suitable algorithm, data flow, pattern of interaction, protocol structure, layering of both code and protocols, ... You don't learn these things just by trial and error. You learn it from someone. They may be your experienced colleauges, if you are lucky. It might be easier to get it from someone who knows how to teach such matters. If your employer has sent you to a selection of good courses (not those 'how to use the product we sold you, or want to sell to you' courses!) you may have it. If not, then might find it in the educational system.
|
|
|
|
|
I haven't read through the entire thread to see if anyone else has given this advice but trust me, apply anyway. It costs you what, maybe another cover letter?
My experience is not so different from your own. Admittedly I spent most of my early dev career in big aerospace (Boeing, GE, TRW, etc.) so I guess your mileage may vary. But I can tell you that every position I held required a degree. Smart companies will still want to talk to you. I took the interviews, got the jobs, made the same money as everyone else.
The requirement is usually to weed out the timid. Go for it.
|
|
|
|
|
The decision, obviously, is on you, but I found myself in a similar situation several years back. I have 28 years of experience, and I realized that getting a degree after so much time working without one would demonstrate dedication and tenacity, and not just serve to satisfy a qualification item. So, I hooked up with WGU. They are 100% online and utilize a competency-based system (pass/fail) instead of the legacy graded system. Along with the fully-accredited degree, I received several certifications (some which amounted to squat) and it makes my resume look pretty darn impressive.
If you investigate and decide to go with WGU, drop me a line so we can say I referred you to the school. 
|
|
|
|
|
I'd like to start by pointing out that there's a marked difference between a BA and a BS. Bachelor of Arts degrees typically have much lower requirements, namely the absence of a secondary science. I myself have a Bachelor of Science, with my secondary science being Biology. In college I was strongly pressured to make it Physics (with no valid explanation given,) but since my current employ is in the medical field, it certainly paid off.
In my opinion, any place that 'requires' a degree, but is willing to accept a BA, is not some place where someone with 22 years of experience is likely to be happy.
With regard to the degree itself, it is always better to have more credentials on your CV/Resume than less. However, given your length of experience, it is unlikely that a BA/BS will make any difference in your pay; you may just need to negotiate a little harder. I also doubt that, at this point, with 15 years development experience, a BA/BS program is going to teach you much you don't already know.
TL;DR: The degree will likely provide some benefit to you, but is unlikely to be worth the time, effort, and money.
|
|
|
|
|
Years ago, I would have said to get the degree.
I was one of those guys who was out programming a peer who had a masters degree, and it
was my first real job!
I left and got my degree. I left a LOT of money on the table. I was somewhat bored by
the courses, but I learned a lot, and I never looked back. I doubled my salary getting out.
So, it DEPENDS. If you have a degree and can easily get another one, using your degree to cover
your basics (reducing your effort to a single year, or 2 years part time). then "Consider" it.
And you WANT to do it.
Otherwise, no.
But make sure your Resume makes up for the lack of THAT degree.
BTW, having Any 4yr degree is a great start. (It shows you can follow directions, although
nowadays it means you might need a safe space from people like me, LOL).
If you REALLY want a specific job, be up front about the degree you have, and highlight the
actual skills you have, and ALL of the courses, etc. Iterate the various places you spend time
learning.
As a hiring manager (in my old days), I would sort resumes by: Educ + Exp, Exp Only, Educ Only, Trash
So, you are in the second pile, or the BOTTOM of the first pile in my system.
Hiring is tight. Your resume should get you the first interview.
If there is a strong gate keeper, find them and work with them.
That is their wish list. If they get 3 resumes, they are going to read ALL 3 of them.
HTH
PS: One of the reasons for wanting the degree is easier communication. So display a willingness to do reading. We have a required reading list for all NEW developers. Some of the books are from old college courses. But it helps us to all use the same language.
|
|
|
|
|
I've full of boring meetings for the comming days even the next few weeks. What a waste of time ahead.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
