Your Degrees
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
KenBonny wrote:
What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
Degree: BS in CS, but back when higher degrees weren't important to get a decent job. These days, I'd probably have spent the extra 10 years and gone for a full PhD so I could get the kinds of jobs I enjoy doing. Do/Did: I've done anything and everything at one time or another. I've always been willing to take on pretty much anything that was needed, no matter how uninteresting it seemed at the time. I've always tried to do every job to the best of my abilities. The dull druggy ones I've usually managed to document and tidy up to make passing them off to the next fool.. er co-worker easy, and I've succeeded in passing them all off to someone else. This may be partly why I've never been pigeon holed into any of those dull druggy tasks permanently. Got here: I think I may now know more about all sorts of unrelated, useful and esoteric bits of our product than any single other person. I'm now sort of a defacto architect, although we've recently had a management changeover and I'm not being uitilized that way anymore. Masters degree: In this hiring climate, I think its a minimum requirement to land an interesting job right out of college. Companies are not bothering to hire mere Bachelors grads when there are Masters grads out there that will work for the same money and have proven themselves "capable" in the academic world. Whatever you do, be careful about getting pigeon holed into a speciality. Specialization will make you more recession proof as long as your speciality continues to be critical to the business, but less recession proof when it is no longer critical. The change can be abrupt and if you're not one of the people helping to put your speciality out of existence, it can (and probably will) blindside you. Specializing in an older, less interesting technology is a smaller pool of job competition than trying to specialize in whatever the hot technology is. Large companies look for and require more tightly specialized workers than smaller companies. Real small companies are just the opposite, needing more broad talents, more the jack-of-all-master-of-none types -- they need the master types, but can't afford to hire that many people to have every worker be the master of their area. Smart small companies recogonize this, dumb ones survive by acc
-
Each of us is solely responsible for the career path we follow. That includes being aware of skills in demand within our industry. Even a beginner has the right to decline to invest time in something like NAV (whatever that is) and pursue a marketable path like .Net or whatever. It's also fair to decline to learn a software package or technology because its not interesting. Just choose wisely...
Old Ed wrote:
Just choose wisely...
I'm aware of that part and the choices that I make now, will last me a long time. That's why I want to make a balanced decision.
Old Ed wrote:
NAV (whatever that is)
Microsofts ERP packet: Dynamics NAV
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
KenBonny wrote:
What is your degree?
BS Math, MS Computer Science BS Computer Sciencse wasn't available when I got my BS
What do you do / did you do as a programmer? How did you get to this point in your career?
Anything they ask me to do. So far, test development, sensor correlation for multiple platforms, radio control systems for airborne surveillance systems, simulations and analysis for Space Shuttle flight design, commercial medical systems hardware interfaces and user interfaces, PDA/Phone software, simulations for battle command systems (game systems), and lots of other fun things. The reality is that prior work experience doesn't always get you the job. The ability to make a language work for you, interest in the project, and some knowledge of the domain are the important parts. I've gotten a couple of jobs because I could say that I had experience with a language/domain, but it was from personal projects I had worked on, not from a job. Another important piece is keeping up with technology from reading and just trying new things (have you played with F# yet?)
Do you think it's worth to obtain a masters degree?
That depends. I think it helped me immensely with some of the work I have done. For some people/work it would have no value at all. A lot of developers do very well with no formal education either because what they do doesn't require much complexity, or because they are able to teach themselves everything they need. I have learned an awful lot since my last classes and most people can learn outside the classroom, but my education opened up things to me that I may never have discovered otherwise. Who would have known that NASA could determine crop yields and optimal time to harvest from satellite imagery (colors and temperatures of the ground images), or who would have guessed that analysis of prostates from ultrasound output could detect cancer with about 95% accuracy. Remember, as we discover great things in this world, it is usually because we have been standing on the shoulders of giants who came before us.
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill "Real programmers can write FORTRAN in any language". Unknown
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
BSc Mathematics - 1983. Only computing component was 3 days of FORTRAN with punch cards (come back, vi, all is forgiven). Really got into computers 1983/4, while on a disastrous teacher training course. Joined IBM after the course, and didn't look back. I do not understand why people feel it necessary to learn programming on a degree course. Any intelligent and logically minded person can learn programming. In any case, in a profession that is as rapidly changing as ours, it is these personal qualities and a commitment to continual learning and development that really matter, not academic qualifications. I sympathise though. I was pulled off a Java system to return to work on an old COBOL/UNIX system because my employer could not find anyone else to hire to support it. So I am fighting back by pushing an aggressive agenda of modernisation of the app in question! And it is working. And both the users and the IT infrastructure people are delighted! Very few jobs involve doing exactly what it says on the tin. Make the best of where you are at, network, be a geek, learn a lot, and get yourself ready for your next position. And don't be afraid to learn skills you can use, even if they seem a little dated. Not every employer has the resources or need to use the latest technologies.
-
John C wrote:
A programmer is a programmer, it doesn't matter what language or run time they are using.
Right... it just seems to me that a decade is an awfully long time to get halfway decent at whatever one does... programming, or not. That's all. :)
It is a long time at the start but seems like nothing after you go through it. :) It's a good rule of thumb though and seems to apply to anything that requires skill. By halfway decent I was using a bit of understatement, what I mean is it takes that long to get good at something, but far short of mastery which of course takes a lifetime. I think you can become a good guitar player with a decade of practice or a good portrait artist with a decade of practice or a good potter with a decade of practice. Any software developer who thinks their some kind of expert with less than a decade of experience is full of shit. :)
Yesterday they said today was tomorrow but today they know better. - Poul Anderson
-
It is a long time at the start but seems like nothing after you go through it. :) It's a good rule of thumb though and seems to apply to anything that requires skill. By halfway decent I was using a bit of understatement, what I mean is it takes that long to get good at something, but far short of mastery which of course takes a lifetime. I think you can become a good guitar player with a decade of practice or a good portrait artist with a decade of practice or a good potter with a decade of practice. Any software developer who thinks their some kind of expert with less than a decade of experience is full of shit. :)
Yesterday they said today was tomorrow but today they know better. - Poul Anderson
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
That's why its important to start working while you're still in college, you get the experience that way. I'm still one year far from graduating in Computer Engineering (5 year degree) and started working on the middle of my first year. Beeing self-taught on .Net helped to get my first internship. The pay at first was low, but was increasing dramatically as I jumped through my first jobs to get a fair pay considering my knowlege. Now I'm about to start as a project leader and I still havent graduated. I'd say you should try getting lower pay jobs on the area you want to work. Prove your knowledge and build your career up while getting enough experience to get a job worth your degree, knlowledge and experience. Don't try to work on something you don't like. You will not be productive, it won't get you anywhere. The masters degree is always worth it in my point of view. But sometimes not necessary. Extra knowledge is always welcome. But I don't think it should be a reason to get a job.
-
I landed what I thought was a .net job. They lied, it was really VB6. I found another position within six weeks.
I didn't get any requirements for the signature
Yeah, I've hit a few bait-and-switches in my decades of programming. The most memorable was one hook that I never bit, but I knew a lot of people who did. There is a certain job niche that straddles the line between technical support and programming. It involves taking technical support problems that have worked their way past "Is the computer plugged in?" and "Did you try clicking the 'clear' key and retyping" and all the other operational causes and are now suspected of being gen-you-wine programming bugs. People in this position are supposed to figure out whether this is a bug, and if it is a simple one, fix it. If it's at all complicated it is sent on to one of the "real" programmers. Employers always want to hire programmers for this position, but no programmer (other than a really desperate one) would take the position. So employers often resort to practices that range from the slightly deceptive "this is a good foot-in-the-door position from which you can move into the programming department" (reality: when it snows downstairs, we'll call you) to the bald-faced lie "this is a programming position" (once a month they let you change the label on a control on one of the forms) Anyway, I was working for a company who had a huge application that was so old it had to be written in Kernighan Ritchie so that it could be compiled on all the different operating systems that their customers used. The decision was made to rewrite the code, and we were all excited about it, but then were were told that the actual rewrite was going to be outsourced to India, and that we would all be "promoted laterally" into this other "programming" position, which involved supporting the rewritten code. Talk about adding insult to injury. When I told them I had no interest in the position, HR asked me, in a condescending tone, if I understood that I would no longer be working for the company if I refused the "transfer". I assured them that I fully understood the consequences of my action. The company tried to prevent me from drawing unemployment by saying that I had "quit" the technical support position. Didn't work; the unemployment folks were onto them. Many kudos to them. A couple of years later, I was looking for another job and had a headhunter bring up a programming job with this same company. I asked her if she was often called to fill this position, and she confirmed, with surprise at my keen sense of insight :) that the turnover at this position was phenomenally high. Six months, on the average.
-
This has been discussed *many* times here before, if you do a search you'll find huge discussions on this in the past. If I recall correctly, about half of us think computer science degrees are a joke, the other half think they are essential. You have to ask yourself if you're the sort of person that is fascinated by the technology and tools themselves or more interested in what can be done with them. The people that like to GET THINGS DONE in the real world and don't care too much which tool they use and are not the sort of people who code for fun in their spare time tend to be the practical people that are running their own businesses or have a lot of freedom and independence in their job and very few of them have a degree or if they do see any real value in it in the real world. If, for you, the technology is what is bumming you out about your current job rather than the actual work itself, then it sounds like you fall on the ivory tower side of things in which case by all means go and get your master's degree as I'm sure there is a cubicle somewhere with your name on it just waiting for you where you can sit all day working on 1/9999th of a project in c# all day. ;)
Yesterday they said today was tomorrow but today they know better. - Poul Anderson
Not true. The technology *is* important. It's hard enough to get a job when your resume is packed with the latest and greatest. Many times in the past few years I've been told that if you don't have the technology that the job requires on your *last* job (who cares about the others, apparently) you can forget making it through the HR screening process. It used to be that you just had to be a good programmer. I took jobs doing languages that I had no experience in, learning on the job. You just can't do that any more. It has to be on your resume first. Leads to a lot of dishonesty in resumes, IMO.
-
Yeah, I've hit a few bait-and-switches in my decades of programming. The most memorable was one hook that I never bit, but I knew a lot of people who did. There is a certain job niche that straddles the line between technical support and programming. It involves taking technical support problems that have worked their way past "Is the computer plugged in?" and "Did you try clicking the 'clear' key and retyping" and all the other operational causes and are now suspected of being gen-you-wine programming bugs. People in this position are supposed to figure out whether this is a bug, and if it is a simple one, fix it. If it's at all complicated it is sent on to one of the "real" programmers. Employers always want to hire programmers for this position, but no programmer (other than a really desperate one) would take the position. So employers often resort to practices that range from the slightly deceptive "this is a good foot-in-the-door position from which you can move into the programming department" (reality: when it snows downstairs, we'll call you) to the bald-faced lie "this is a programming position" (once a month they let you change the label on a control on one of the forms) Anyway, I was working for a company who had a huge application that was so old it had to be written in Kernighan Ritchie so that it could be compiled on all the different operating systems that their customers used. The decision was made to rewrite the code, and we were all excited about it, but then were were told that the actual rewrite was going to be outsourced to India, and that we would all be "promoted laterally" into this other "programming" position, which involved supporting the rewritten code. Talk about adding insult to injury. When I told them I had no interest in the position, HR asked me, in a condescending tone, if I understood that I would no longer be working for the company if I refused the "transfer". I assured them that I fully understood the consequences of my action. The company tried to prevent me from drawing unemployment by saying that I had "quit" the technical support position. Didn't work; the unemployment folks were onto them. Many kudos to them. A couple of years later, I was looking for another job and had a headhunter bring up a programming job with this same company. I asked her if she was often called to fill this position, and she confirmed, with surprise at my keen sense of insight :) that the turnover at this position was phenomenally high. Six months, on the average.
Francine D. Taylor wrote:
I've also seen things go the other way, though not without effort and ambition. My first job out of college was data entry. The company president kept asking me to type out these confidential form reports that could not be saved on my computer, only to a disk that he kept. I told him I could write him a computer program that would allow him to input and store the report information on his personal computer, so that no unauthorized eyes would violate its sanctity (I phrased it more diplomatically, of course Smile Thus I worked my way into creating a PC programming department within the company (it was a mainframe only shop at the time) and ended up reporting directly to the company CEO.
That's a good story.
I didn't get any requirements for the signature
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
I never got a degree. Started programming back in the mid eighties, when programmers were a lot scarcer. Never had a single employer who cared whether I had a degree or not; it was always about the experience. Hopped through a long procession of companies (some contracts, some chapter 13s, some layoffs), operating systems (DOS, Unix, Windows, various miniframe ops), languages (too many to list), industries (lots). I take that back, there was one company that required all employees to have a degree. I didn't. They hired me anyway. Here's my suggestion. Stick with your current job, but take classes and do .NET programming on the side. It's important that you be able to list .NET on your resume if you want to get a job doing it. No, not important. Vital. Form your own "company". Volunteer to write programs for your church, charitable organizations, anybody who hasn't got a big budget for their needs. Then list your experience with your own company on your resume. Don't lie about the work, just don't mention that you didn't get paid for it. You get three benefits from this. One is the experience. Two is that it looks good on your resume. Last but not least, you get to feel good about helping out your community. If it isn't .NET that you want to move toward, that makes things harder. Other languages aren't as readily portable and easy to install onto PCs, which is all that most small organizations have. Still, you get the idea. Experience is the key, not education.
-
Not true. The technology *is* important. It's hard enough to get a job when your resume is packed with the latest and greatest. Many times in the past few years I've been told that if you don't have the technology that the job requires on your *last* job (who cares about the others, apparently) you can forget making it through the HR screening process. It used to be that you just had to be a good programmer. I took jobs doing languages that I had no experience in, learning on the job. You just can't do that any more. It has to be on your resume first. Leads to a lot of dishonesty in resumes, IMO.
If you are a developer with a decade of experience in the trenches with *any* programming technology I defy you to find it more than a couple of weekends challenge to pick up a new language / technology enough to work with it.
Francine D. Taylor wrote:
It used to be that you just had to be a good programmer.
Good shops still hire good programmers. Bad shops go through some silly hr or recruitment buzzword ticking process.
Yesterday they said today was tomorrow but today they know better. - Poul Anderson
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
My degree is in CS but I started developing at such a young age (12) that I was already experienced in many langs before I ever started school; I say that because I have no doubt I would have ended up doing the same kind of work with or without a formal degree, although I will say that much of the formal CS education (things like algorithms, data structures, operating system architecture, the more arcane theory behind relational databases) etc are extremely valuable, I'm not sure if I would have learned them had I not studied at a university. If your goal is to be a software developer as long as possible, then no a masters is probably not going to help your cause so I would not invest a great deal of time or money into that. However if you ever plan to teach or otherwise work in academic environments, publish books, etc it can definately help. It could potentially help at the mgmt level as well. I have toyed with the idea of getting a masters in software engineering, more or less for fun than any sort of career expectation, but I keep getting stalled by the realization that there is almost always something that I could be spending my time learning that is much more relevant to the kind of work I do. Does that make sense? I like all the academic stuff, but I don't think that graduate level classes tend to have that "indispensible" quality that some of the under grad classes like I listed earlier have. Regarding NAV, I've never worked with it but still can relate, I've often found myself in situations where I'm faced with a stodgy old technology which is uninteresting and hard to work with. I'm now in my 40's so for the most part if the job is not aligned with my own career plans I basically tell them how I feel and move on to something more aligned with my professional/personal goals. When you are first starting out you are building experience so that can be tougher -- yes you can expect that kind of thing for the first decade or so of your career. I remember working in proprietary languages that nobody else was using and hating it, and I still do lots of things that I don't really care to do, but I expect that I will be spending a certain percentage of time working on things that allow me to retain my passion for programming. If I am expected to do what "the man" wants 100% of the time and he's not showing any respect for my own career development, then I simply go elsewhere. Be sure and at least explain this to him before you take off, give him the chance to make it right. He might have thought t
-
If you are a developer with a decade of experience in the trenches with *any* programming technology I defy you to find it more than a couple of weekends challenge to pick up a new language / technology enough to work with it.
Francine D. Taylor wrote:
It used to be that you just had to be a good programmer.
Good shops still hire good programmers. Bad shops go through some silly hr or recruitment buzzword ticking process.
Yesterday they said today was tomorrow but today they know better. - Poul Anderson
Sorry to rain on your parade, but by that definition the programming market is full to bursting with "bad" shops. Your chances of actually finding a job available in one of the "good" ones is practically zippo, because those are the sort of shops who know the value of their programmers and are willing to work to keep them. Of *course* any good programmer can pick up new languages immediately. For my first real programming job after graduation I was hired to do C. I had never even heard of the language at the time. In six months I was the lead programmer. It doesn't *matter* what you can or can't do, when you are trying to get an interview. What matters is how well you match the requirements of the people screening the applications. When they're looking at a stack of resumes up past the brim of their thermal coffee mug, who are they going to weed out first? People with no experience. Who goes next? People without relevant experience. Then people without very *recent* relevant experience. Now they're down to just a few dozen. If they're lucky.
-
Old Ed wrote:
Just choose wisely...
I'm aware of that part and the choices that I make now, will last me a long time. That's why I want to make a balanced decision.
Old Ed wrote:
NAV (whatever that is)
Microsofts ERP packet: Dynamics NAV
Just one thing though... "Experience working on ERP systems" can have a high return on investment in your CV! For the records, here's my story! :) It begins with me running out of cash when I got out of college. Then I found a job ad for a project that was 3 months late to ship and they figured it could only help to throw me (fresh out of college) into the mix. Over the following 4 months, my two colleagues got fired and about 2 years later, I had built them two magnificent pieces of software I'm still maintaining on contract. Then I figured I had reached the top at that company and I couldn't learn anything else there so I left and went back to school to get my degree. I could have gotten another job, but I think it may remove the "glass ceiling" in my next jobs. I'm still there now working on lots of different projects (I joined a club working on an autonomous robot!) and having a lot of fun! In the end, having fun is all that really matters anyway.
-
DavidCrow wrote:
I really enjoy the new challenges
Good for you, you like coding in C++ and Java. I'm stuck in C/AL code. It has an IF, REPEAT and SWITCH statement, nothing else. I think it's boring and it's not teaching me anything new. You could say it's a lesson in humility, but basicly I'm just writing code that gets records, adds or multiplies something and then writes the result into another table.
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
My background is engineering. (PhD - Mechanical). Started coding in the 1970's. Mostly writing analysis and modelling code, but some machine interface and control stuff as well. I can't say I have a lot of sympathy for you. There are lots of development systems out there. C# is just the latest of a long list of system you will encounter in your career. Some are application specific, some are legacy. C#, or any .NET system, is a minority in the programming world. If you're aspiring to be a professional programmer, then part of what you will be paid for is deal with odd-ball, undocumented and buggy systems - there are lots of them - that were probably written with the best development environments of the time. Let's hope that you're C# programs stand the test of time as well. Lots of code dies an instant death as soon as a user sees it. About having to do hacks - at some point the limit of any system will be pushed. If you look at some of the C# articles on this site you'll see lots of hacks that the authors though were good solutions but ended up having some unintended consequences (a euphemism for bugs), as pointed out in the replies. Being a programmer is not about the languages you know. It's about organizing the project correctly and expressing it in the clearest (meaning most reliable) code you can wrangle up. As a NAV programmer, trying to accurately interpret the needs of accountants and managers ("the clients") without going over-budget is good experience. Good luck on your career, whichever way you go.
-
Jim Crafton wrote:
Of course it sucks. You just graduated. Everyone starts on the bottom. Welcome to Reality 101. Not to sound overly harsh or nasty, but that's the norm.
I don't want to come over as a know it all, but I knew that. :) That's also the reason I don't just quit and go back to living it up at home and look for another job full time.
Jim Crafton wrote:
It takes time to get good. Time, effort and patience.
This raises another question: How do you know you're good? You've been coding stuff that works for 10 years now, ok. But who tells you your code is good? I was thinking that more education would give me better skills (cause my code would literally be reviewed and my flaws would be pointed out to me, thus learning from my mistakes).
I've worked in the field before and I'm doing said degree right now and believe me, if you're talking "getting things done", you'll learn much faster if you just get a job in the desired field. And read some good books like code complete. I'm getting that degree for many reasons including that I would love a job in programming language research (my final project is going to be awesome!), etc. Anyway, if you don't like it there, it's a good enough reason to leave. All that really matters if that you enjoy yourself. If you start compromising on that, you'll be doing compromises all your life. The simplest rules make the most efficient algorithms ;)
-
Hello, fellow Projecteers. I've been lurking on here some time now and I think this is the best place to ask my question. I graduated last June and started working a couple of months later. I'm working 4-5 months now as a Dynamics NAV (a.k.a. Navision) developer. Got hired to work out a .NET project, but two weeks into the job my boss says to drop it because it's too expensive for me to work out. He gives me several NAV assignments and wants me to specialize in NAV. Personally, I hate NAV. It's old, it's clunky, it won't work without a dozen hacks, the development language (C/AL) is limited and frustrating (I'm used to C# from school and personal projects). Now I'm looking for another job, but every interesting job I encounter asks for a masters degree or experience as a programmer. My question to you: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree?
Your questions were: What is your degree? What do you do / did you do as a programmer? How did you get to this point in your career? Do you think it's worth to obtain a masters degree? Not one responder answered your questions, so I will. I have a degree in History and a Masters in Finance. Primarily writing sql code for financial institutions, banks and insurance companies. Studying, studying, studying and networking. An advanced degree matters when you want to move up or consult. I chose consulting.