Not even close. Started a CS degree 7 years ago at 28 and am a director of engineering now, if it’s what you wan to do go for it. I will give a warning that the market isn’t amazing right now, and people getting into it just because they see the salaries is flooding the entry level positions. If you’re motivated and excited about building software you’ll be fine, but something to be aware of.
Enders game is a book/movie about a future human civilitation that is under attack of an alien species. To ensure survival they train children as strategists because they take more risk and use unconventional tactics. They are basically saying “nobody requires you to be young here”.
The thing with computer science is that it’s always changing, so everyone has to keep learning it regardless of age or prior experience, or they’ll risk getting left behind.
I’ve been a professional software engineer for over ten years now. I didn’t study anything to do with computers until I was 20; I’d been aiming for a different career and was halfway through a degree before I discovered I didn’t enjoy it and wasn’t getting very good grades, so I swapped.
While at uni, I was part of the student mentor program where I did teaching assistant work for the lower years. One of the students in the lab group I assisted was a guy in his forties who’d seen his factory job automated away and decided if computers were going to take his job, he’d go learn how to work with computers and move into the sector that was creating jobs rather than removing them. He was a good student and picked things up quickly. I have every confidence he’s still out there doing well as an engineer.
22 is a perfectly fine age to start. If you’ve got the right attitude - the desire and motivation to focus on your studies and put in the work - you’ll do great.
One thing worth being aware of beforehand though is how a lot of your studying might go. The professor I assisted in those labs told me about an observation that’s been made in the teaching profession, and I saw it in action myself. A lot of computer science and programming is about finding the mental model that helps you understand what’s happening, how the computers work. Until you find it, you’ll be stuck. Then, something will click, and it’ll make sense. The professor told me they don’t see the usual bell curve of grades - they see two. One cluster of students at the bottom who don’t get it, and one higher up who understand. A lot of learning computing is less of a linear progression and more a process of running into the wall until you chance upon the particular explanation or analogy or perspective that works for the way you think, and then suddenly that particular concept is easy, and it’s onto the next one. This series of little clicks is how you progress.
Once you’ve got a few core concepts down it’s easier to work out how new things fit into the mental model you’re constructing, but be prepared for the early bits to have some frustrating periods where it feels like you aren’t getting anywhere. Stick at it, and look around for other resources, other books or tutorials, other people to explain it their way. I frequently saw a student look totally clueless at my explanation, but another student who’d understood what I said would paraphrase it slightly differently, and that was all it took for the clueless student to suddenly understand and pass the exercise. That lightbulb moment is as fun to experience yourself as it is to bring about in others. You just have to hang in there until it happens.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
No such thing. Ask away!
!nostupidquestions is a community space dedicated to being helpful and answering each others’ questions on various topics.
Rule 1- All posts must be legitimate questions. All posts titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That’s it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it’s in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't harass or disturb other members.
If you vocally harass or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content. Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Partnered Communities
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Matrix Chat Room
To find & join our chat room, log into fluffychat.im(or any other matrix client) and put #nostupidquestions:matrix.org on the search bar.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
Not even close. Started a CS degree 7 years ago at 28 and am a director of engineering now, if it’s what you wan to do go for it. I will give a warning that the market isn’t amazing right now, and people getting into it just because they see the salaries is flooding the entry level positions. If you’re motivated and excited about building software you’ll be fine, but something to be aware of.
Yo man this isn’t enders game
Hmm… You got me curious, context?
Enders game is a book/movie about a future human civilitation that is under attack of an alien species. To ensure survival they train children as strategists because they take more risk and use unconventional tactics. They are basically saying “nobody requires you to be young here”.
no, but at 23 you’d wish you started at 22
as the saying goes the best time to start was when you were 6 the second best time is now
The thing with computer science is that it’s always changing, so everyone has to keep learning it regardless of age or prior experience, or they’ll risk getting left behind.
deleted by creator
I’m in my late 40s and I just got a bachelor’s degree. I just started a masters program. It’s never too late.
I’ve been a professional software engineer for over ten years now. I didn’t study anything to do with computers until I was 20; I’d been aiming for a different career and was halfway through a degree before I discovered I didn’t enjoy it and wasn’t getting very good grades, so I swapped.
While at uni, I was part of the student mentor program where I did teaching assistant work for the lower years. One of the students in the lab group I assisted was a guy in his forties who’d seen his factory job automated away and decided if computers were going to take his job, he’d go learn how to work with computers and move into the sector that was creating jobs rather than removing them. He was a good student and picked things up quickly. I have every confidence he’s still out there doing well as an engineer.
22 is a perfectly fine age to start. If you’ve got the right attitude - the desire and motivation to focus on your studies and put in the work - you’ll do great.
One thing worth being aware of beforehand though is how a lot of your studying might go. The professor I assisted in those labs told me about an observation that’s been made in the teaching profession, and I saw it in action myself. A lot of computer science and programming is about finding the mental model that helps you understand what’s happening, how the computers work. Until you find it, you’ll be stuck. Then, something will click, and it’ll make sense. The professor told me they don’t see the usual bell curve of grades - they see two. One cluster of students at the bottom who don’t get it, and one higher up who understand. A lot of learning computing is less of a linear progression and more a process of running into the wall until you chance upon the particular explanation or analogy or perspective that works for the way you think, and then suddenly that particular concept is easy, and it’s onto the next one. This series of little clicks is how you progress.
Once you’ve got a few core concepts down it’s easier to work out how new things fit into the mental model you’re constructing, but be prepared for the early bits to have some frustrating periods where it feels like you aren’t getting anywhere. Stick at it, and look around for other resources, other books or tutorials, other people to explain it their way. I frequently saw a student look totally clueless at my explanation, but another student who’d understood what I said would paraphrase it slightly differently, and that was all it took for the clueless student to suddenly understand and pass the exercise. That lightbulb moment is as fun to experience yourself as it is to bring about in others. You just have to hang in there until it happens.
Absolutely not.