Read the documentation. Aggressively pursue opportunities to learn new skills.
Asklemmy
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
I feel like your advice is not emphasized enough in tech circles. Our field is constantly changing and evolving so success is often predicated on willingness and eagerness to learn.
That said, also recognize that not every new skill or tool is necessarily appropriate for a particular task. You should still learn them, though, otherwise when they are appropriate, you may not even recognize it.
Get a better paying job once you've got some experience. Raises won't keep up with your value.
Don't work yourself to the bone. There really are plenty of jobs that only require 40hrs/wk and pay the same or better.
Work somewhere with a good culture.
This is extremely important. Your best raises and title changes will come from changing companies, not internally.
3 and leave is the general rule of thumb till youβre at the most senior levels. Never move laterally if it can be avoided, know what the resume and experience looks like for the next level and always be working towards that.
Don't burn out! Ask for help and guidance when needed, and take care of your mental and physical health (get a hobby, go out with friends, go to the gym, etc.)
I've seen brilliant people burn out and end up leaving/missing out growth opportunities because of it. Now that I manage people, it is my biggest area of focus because many times the best employees are the most at risk. They keep getting praise and asked to be involved in more and more and it becomes hard to say 'no' to new projects, responsibilities, etc... Until it is to much.
When it happens everyone looses, your boss, your team, the company, and especially you.
a million times this, so many young people overwork themselves and burn out quickly
I cringe whenever a see someone has checked in code at 1am on a weekend, and these people are also working normal business hours so itβs not like they are only working at night
sadly itβs usually the same people who never take PTO either
You're not responsible for the bad decisions made by the people who have positional authority over you. Do your best. Warn them about the risks. Let yourself feel disappointed by their decisions, but don't ever accept responsibility for them. If you did your best to warn them, then you took your responsibility seriously. That's enough.
CYA in a nutshell
UPDATE: I added some clarifying points in light of getting some of this wrong. I believe the underlying point still stands.
No. I believe I understand why you think so, but just no.
At best, covering your ass means gathering evidence about how much you tried to warn the people making decisions, in order to avoid or deflect blame when things go wrong and someone starts wandering the countryside looking for people to blame. I'm not suggesting that. I'm not even suggesting saying "I told you so." when things go wrong.
Quite often, at least how I've seen it, covering your ass involves not even trying to do the right thing or, perhaps, pretending in public to do the right thing in order to have a plausible excuse when things go wrong. That's also not what I'm advising.
I'm advising not to accept responsibility for other people's bad decisions. If you genuinely did your best to influence their decision and they chose poorly anyway, don't take responsibility for that choice. The responsibly remains with the person who had the authority to decide.
For example, if the OP decides to listen to you instead of to me, that's not my responsibility. I've tried to explain my position, but the responsibility for choosing what to believe belongs with them. I'm most definitely not covering my ass; I'm recognizing that I'm not responsible for replacing OP's judgment with mine. If they ask me for more information, I have the responsibility to provide it. If they ask me to clarify my position, I have the responsibility to do that. But I am not responsible for convincing them nor for their final decision.
Covering your ass typically involves not trying to do the right thing or, perhaps, pretending to do the right thing in public in order to have a plausible excuse when things go wrong
You have a very different idea of CYA than I (or the other poster). To me, CYA means ensuing you have evidence that tried to do the right thing and were overruled, so that you will can (justifiably) avoid repercussions when the failures you warned about come to pass.
If you're a developer, read the source code. People will tell you how they remember things working, or how they think they should work. The code is what it is.
Exercise regularly. Maintain good posture. Stretch. It kills your body, working at a computer all day.
Understand that technology cannot fix people problems. Always remember that. If you're asked to solve a people problem and you don't understand it, you will suffer. Only management can fix people problems.
Also, it may not seem like it, but software is almost entirely about people. Everything comes down to the users. You need people to use your software. You need people to want to use your software. Even if your users are other engineers, you still need users. You could build the best piece of software ever made, but it's nothing without usage.
Things like marketing, product, and design are usually equal parts of building software.
This is something that took me a long time to come to terms with.
Yup. It's definitely always about people. The people using it.
I've worked in software support, QA, and technical writing.
A LOT of developers who come in as devs from the very start of their careers know very little about how the average person might interact with the software they are creating. And what they know of, they can (sometimes) be so sneering and dismissive of that it actually impacts their design decisions. Like, "I don't care, the user is stupid, I'm doing it the RIGHT way." Even when the "stupid user" is like 90% of the population that'll use your widget.
A new (and old) dev should read past customer tickets and talk to your customer support people, as they'll have the actual real-world experience and examples with non-technical users that can give you insight into how to better create the thing that you are creating.
To make a comparison...say you were a furniture designer making chairs, and you're 6'3". Sitting in the chair yourself and proclaiming it's fine isn't enough if your users are children, women, guys shorter than you, people lighter than you, people heavier than you, and the disabled. You need to actually understand how people who navigate the world in a different way than you do interact with the thing you're making. A chair that works fine for someone who is 6'3" with two working legs might be unusable for a 11 year old who broke their foot, or a 4'11" grandmother who can no longer move heavy things around (say if the chair is solid and heavy and something a 6'3" dude could easily move).
With technology, it means average non-tech users will flow through menus differently than you, might have vision or hearing problems that you don't have that make signals from the widget difficult to decipher, and people in general who are non-techie can also be more risk-adverse when it comes to things like clicking strange buttons. And that's just the tip of the iceberg.
Everyone else here who said, "Keep learning" is right on, but don't forget to work on your soft people skills along with your tech skills. Whether your long term goal is to stay in development or some other aspect of the industry, you should be comfortable talking to all sorts of people (management, sales, customers, etc...), making presentations, being social at conferences and so on. We (techies like me) tend to forget this, but it's really important.
Imagine yourself starting your own company in five years or being the senior manager of a large group. How are you going to like meeting new people every day, selling or at least explaining your product or service to them? If the answer is "not very", then start working on that now.
Ask questions, don't assume. Keep notes of meetings, and notes of your work, little bits. Always have a good rollback plan.
Ask the experts from help, and learn from them. Don't ask things you can legitimately learn really easily on your own by just doing a quick read of the code, but the bar for questions to not be stupid is pretty low. In most projects with any complexity, it's probably overall saving the company money if you ask someone who knows and can save you time, instead of wasting a ton of your time reaching the same conclusion. But next time that problem comes up, you should know how to solve it, so it saves everyone time.
I can think of three big pieces of advice:
-
Are you sure? I think the golden age of the magic tech jobs is nearing its end. If you want to join the tech industry because it's an easy ticket for a successful life then you might wanna rethink that. If you want to join the tech industry because engineering is pure magic and you want to be a part of that, then by all means, you do you. Just be ready for it to be a bumpy road if you aren't able to adapt to whatever AI does to the industry over the lifetime of your career.
-
Find companies who will treat you right, and where people are real and do real shit. When I was first starting out, a project I was working on was behind. I stayed over the weekend, even though people told me not to. I finished, I was proud of myself. Then I came in on Monday and everyone else's stuff was behind anyway, so we missed our deadline regardless, and in the end it didn't matter. Right around that time was when I decided, more or less, to hell with this. At the company I eventually jumped ship to, my boss would regularly push back on clients who wanted us to work weekends, come by and encourage people to live a normal life instead of just a working-to-death life. Basically, he looked out for people. So I stayed there for quite a while. Basically, after that experience, if the boss wasn't looking out for me or the tech was shoddy, I bailed instantly. You gotta have a good human life and take pride in what you do.
-
Own up to your fuck-ups. You'll make some. I've destroyed important hardware, made massive architecture mistakes on client work which the clients then identified and talked to us about, deleted the partition table on an important public-facing server, you name it. When I did something like this, I would be 100% upfront about what happened. In good working environments, people would recognize and give respect for that, because nobody's perfect. In bad working environments, being upfront about mistakes would somehow be a bad thing (see point #2). The answer is not to become sneaky. The answer is to leave and go somewhere where people respect honesty. Those places do exist.
That third one can be tough, but I think itβs super important, and, not just in tech.
An easy way to confirm your first point: would you still want to do it if you were paid significantly less? If so, then yeah, you're in the right place.
Ultimately tech is a tool to help automate and solve peopleβs problems. You want to get close to the people your solving problems for so you can get feedback and figure out how to do your job. Your organization may not do this for you. I spend a lot of time on forums listening to my users, and do a lot of extra testing to make sure Iβm solving there problems and not making new ones.
If you're offered a job with more money/benefits or whatever, take it. Don't give your employer the option to counter. And if you ever do let them counter out of curiosity, don't take it... Leave.
There's too many horror stories of people basically staying on after a counter-offer, only to train their replacement and end up tossed out anyways.
Loyalty doesn't mean shit in tech; any promotion you get internally at a job will be pennies compared to what you're able to get by shopping around; so do yourself a favor and run whenever the opportunity arises.
YMMV; staying can work well but you really have to know your employer, and be able to roll with the punches either way. It can be equally risky to be the new guy again. Always have an honest understanding of your replaceability.
If you have an opportunity to learn a new platform or technology, take it. Every environment has a different way of organizing, implementing, troubleshooting, etc. Each one you learn gives you a new way to look at a project, and teaches you something about how other people may think about projects, problems, and solutions.
People who stick with the same tech for decades are also stuck with the same approach to new projects. When the only tool you have is a hammer, every problem looks like a nail, and all that. Get more tools in your tool belt.
Remember tech-companies exist to make money, not to "do good." Whatever problem they are supposedly working on, they are only doing it because someone thinks they can eventually turn it into a revenue stream. Don't drink the kool-aid, be a mercenary and get as much out of it that you can until you can leave for good. Dont' be the like the smuck's that are still working at twitter.
Yup, and this applies to any company. If you don't own the business, you are a line item, not "family". Always be ready to jump ship for a better opportunity, because they will do the same.
Don't burn yourself out, document everything.
What area of the tech industry are you starting in? It would help to know so we could tailor the advice to you.
Never stop learning. Most important advice IMO.
Tech is a field that is constantly evolving, whether you're a developer or IT service desk, the tools you use today will probably be very different 5 or 10 years from now. Never get stuck in a rut, it'll burn you later in life. Remain curious and keep learning the new things coming out.
Set boundaries.
At my first professional job, there was one guy who always came in at exactly on time and never stayed late. I always thought it was weird, I'd typically stay at least long enough to finish whatever thought I was working on, and sometimes later just because I had nothing important to get to. Eventually I became one of the guys to go to when you needed someone to stay late. I didn't mind, in fact I like being helpful. Looking back, I realized that I gave the company a lot of free work and didn't get anything for it. It seems obvious but important to realize from day one, you are setting expectations. A "good" manager will figure out pretty quickly which employees they can exploit and how.
you will end up bringing down production or make a however many tens of thousands of dollar mistake. Don't worry about it too much when it happens. That sort of thing doesn't usually get you fired the first time.
Be transparent about your mistakes and learn from them - better yet, help make sure others won't make the same mistake.
When interviewing, if a company gives you the "We work hard and we play hard" line, run. It actually means tons of unpaid overtime in exchange for some snacks and a broken ping-pong table.
Be hard-working but loyalty will take you almost no where. Every 2 years you should start looking for a new job with better pay and less hats. If you are a year in and hate it just switch to somewhere new. I got 2% raises at jobs year to year but switching jobs for me got 20% - 40% more.
No more than 2 years in a same company and always be interview ready. Keep regular contact with recruiters. Thereβs always a better opportunity.
This is exactly what my friend did. He earns double my salary even though I work in one of those big companies and do more than just development.
Make things just complex enough that others donβt want to learn it but not so complex anyone can say it is too complex.
Also pick up tasks others donβt want to and make yourself hard to get rid of.
Then quit and get hired back as a consultant/contractor and work your own hours and how much you want to.
It can depend on the area you're going into, but things like continuous learning of new skills, as well as keeping up-to-date with the latest happenings in that field, are always good ones to do.
Don't work in the service desk department. Worst job in the world of IT.
All other comments in the post are gold.
Always stay relevant with skills and knowledge relevant to the market - one day you work for papa Google and everything is great, another day you'll get fired without you seeing it coming - job is not a family.
It's fun and games to master a skill/technology, but if there are no jobs for that, that is a red flag.
Generally it's important to keep the hobby-job balance, and to understand that sometimes your hobby specifically won't be your job, and that is OK because most of the people are like that.
Iβm looking to change careers into tech at 43. Iβve been a teacher my whole life but education isβ¦just not a good job anymore. Iβm very interested in data science and would love to end up working on climate modeling but Iβm practical and understand that I should take what I can get. Anyone have some career wisdom theyβd be willing to share?
Afaik (I'm an environmental geologist) Climate Modeling isn't really tech, or the tech industry, it's more academia. Most climate modelers I know of are working off grants in university labs. That may/may not help you get into it, but if you're seeking something that is a deviation from teaching/education, academia isn't much better for all the same reasons really.
Do you have a background in climate science or environmental science? Or modelling for that matter?