Your opinions of those concepts will gain even more respect as the knowledge of your alternatives multiply. Back end engineers add utility to everything the front end engineer creates, in a combination of database and software written in a server-side language. Where do you live?
Trending News
By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Stack Overflow for Teams male a private, secure spot for you and your coworkers to find and share information. Currently, however, I am a software engineer, sogtware sounds more prestigious to me. More money also sounds nice, though, but at what point is it worth it? Prestige is irrelevant, in my opinion. I suggest you do a cost benefit analysis of doing the work you enjoy against earning more money.
24. Broadcom pays its software engineers an average base salary of $101,808
Nuclear Engineers are in short supply so should be able to command a higher salary, especially if the UK embarks on a new phase of building nuclear power stations. If it doesn’t, there are sure to be lucrative opportunities in Iran, for example. Software Engineers are ten a penny, but if you have the entrepreneurial skills, you have more opportunity to be your own boss and, if your lucky, strike it rich with the next killer app. Company’s under central government pays less to their staff. Official salary of our President is less than a lac. So anytime the software company’s pay better.
1. Full stack generalist software engineer
By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.
Currently, however, I am a software engineer, which sounds more prestigious to me. More money also sounds nice, though, but at what point is it worth it? Prestige is irrelevant, in my opinion. I suggest you do a cost benefit analysis of doing the work you enjoy against earning more money.
It may be you don’t mind QA that much software engineer who make more money which case go for the extra money. If you think it would be horrible, don’t do it unless there’s absolute bucket-loads of money changing hands. I’m now back in a tech role and enjoying it a lot. I wouldn’t do PM work now unless they doubled my salary and even then, I’d think twice about it. My advice is to do what you enjoy first and foremost.
You only get one shot at life and, even if you make a fortune, you’ll still be dead in years. One of my favorite quotes is: «the trouble with the rat race is, even if you win, you’re still a rat». Do you enjoy figuring out how to break things?
Are you good at it? Being good at QA and good at software development is an excellent niche — being able to think like a programmer makes your testing more comprehensive and your debugging more productive, while being able to think like a tester makes your code more reliable. Regarding prestige: The fact that this job pays better than dev is one indication that the company values QA, which is excellent.
Additionally, there are several advantages to being a programmer in QA rather than a straight software developer that you might not have considered. One is that QA engineers tend to have a wider scope than developers. Rather than spending all your time on one narrow area, you can be a little more high level and look at how the different components fit together and how small pieces of code fit into the larger picture.
Another is that QA engineers — in a company that values them — have more power to get things fixed than almost anyone else in the company. As a QA programmer you write code to test code; doing so often reveals that the specifications are unclear. You will often find yourself effectively defining what the proper behavior should be because the definition of proper behavior is essentially whatever passes your test code.
So you have the power to fix things by declaring broken behavior «a bug», you have a wide scope, and you have the ability to become a true expert in how the software as a whole is supposed to work, even more so than the developers who understand in depth only their tiny piece of it. And it’s more of a «people» job — you get to work closely with the developers and project managers rather than having your head down in code quite so much. Lastly, the work tends to be less stressful than software development.
When horrible bugs crop up you find them but get to pass the work of actually fixing them to somebody. The more problems there are in the code, the better you look and the more it feels like you’re making progress at the same time the developers are all tearing their hair.
If you do so, you can call yourself a Software Developer in Test or a QA Software Tools Engineer and think of yourself as producing testware — code and documents that make the code better — in lieu of software.
My wife told me she liked me better when I was doing QA instead of software development. I’d be more relaxed. There were advantages. I found a frightening bug one Friday afternoon, and went home immediately after documenting it and had a very nice, relaxed, weekend. The same was not true for the woman who had to fix it.
Working in QA doesn’t stop you being a software engineer. Or, more precisely, it darn well ought not to! If it does stop you being a software engineer, then there is something seriously amiss; writing good unit tests will require good software engineering skills.
Don’t get hung up on job titles — there’s a process I call ‘job title inflation’ which means that increasingly grandiose job titles are provided to or used by individuals for the same work that previously had a less grandiose.
Also, job titles don’t translate reliably across different companies. I don’t think doing QA engineering writing tests or frameworks for testing is worse than doing development. When I was younger, I thought QA is more boring.
But from practice, it isn’t. When writing the real program the productyou often need to be more careful about the coding conventions, security, error handling and documentation. That can make very simple tasks complex and boring. On the other hand, if you are writing for QA, you can just forget all that and cowboy-code everything, because it’s all just a scaffolding to get the testing. This can be very refreshing. Also, if your job is boring and you are a programmer using computer, then you are doing something wrong.
Leave the boring part to the computers, that’s the point! And if you don’t know how, start inventing how just now, and suddenly it all will be much less boring. I was in the same situation as Pax and my advise is the very same: don’t do anything you expect you don’t like, or rather, love doing.
People who can do what they love doing for a living are priviledged. That privilege should not be easily discarded. Sometimes you need to do sacrifices. You may need the extra cash for something that brings you more pleasure or comfort in the long run that the sacrifice you make by taking the «wrong» job, ie. I’m guessing that you are working with people that are a bit older and more experienced than you. Maybe some time in QA would give you valuable experience.
Career advancement is not often linear. Would you just be setting up and running tests, or would you also do code reviewing? Don’t worry so much about prestige. There’s plenty of life left in you. Albert Einstein did his best work when he was a patent clerk. Also, money is not a great motivator in the long run.
If you can’t make ends meet on your current salary, a raise will make life more comfortable, but you won’t get filthy rich as an employee. You need to be happy with what you. My experience is that we decide unconsciously very early in the decision process and then spend most of our energy rationalizing the choice.
So you probably already know what you’re going to do. Why let an old fart like me tell you what to do? It’s your life. I don’t think you need to worry about your designations too.
Do what you like the most and enjoy working on and yes money does matter sometimes I know you may have made your decisions by now but for anyone who finds themselves in a similar situation:.
Consider the long term affect on your career. The position you hold right now, changes your career path. Learn. QA engineer and more money or software engineer with less [closed] Ask Question. Asked 11 years, 1 month ago. Active 8 years ago. Viewed 16k times. Bobrovsky Sydius Sydius No one can answer a question like this for you. You are the only one that knows how much you value money vs. Even looking at this solely from a career advancement viewpoint, the question should not be «what gets me more right now» but «what gets me where I want to be in 5 years?
It’s been some time since you asked. What did you decide, and what happened? This question was fine when it was asked. I don’t think it is a good fit for the current purpose of Stack Overflow. I believe it should be closed, though I don’t think it should be removed — it should just be marked as of historic. I took a role as a PM for about 18 months for extra pay and hated it after about 6 months.
Your advice was and still is my guideline in life when deciding such questions. One needs to simply see the bigger picture. So, what the heck do you want to do? David Thornley David Thornley Jonathan Leffler Jonathan Leffler k gold badges silver badges bronze badges. My 2 cents: Don’t pay attention to the title that goes with the job. Look at the work that comes with it.
Would you like it? Ask yourself: Could working in QA help you become a better software engineer? If you like what you are doing now, think twice before giving it up for a higher salary.
QUUBE’S ecosystem consists of three key elements, adopting quantum cryptography at all stages. They are a crypto trading platform, STO blockchain protocol, IEO launchpad.
Discover more about us on https://t.co/yLHPIoddpc pic.twitter.com/fZnjtLCpaA
— QUUBE Exchange (@QUUBE_Exchange) October 20, 2019
Good possibilities to make a difference in a competitive market. Entineer more of the stuff you’ll wish you’d done more of once you get older. Have you done Earn1k? As one commenter advised to younger programmers: Do more of the enginwer you’ll wish you’d done more of once you get older. I realized when I started developing software that I will not be happy if I get put in a position where I am no longer programming.
Comments
Post a Comment