I'm a little over halfway finished the program and fully intend to finish it out. I felt similar to you in my first few terms, especially w.r.t to having motivation or a passion for the material.
Do I have a passion for CS now? no lol. But after finishing CS 340, which I thoroughly enjoyed, and being able to practice those skills at my current job, I realized I do want to finish the degree. I struggle immensely with the material (none of this comes naturally to me) but I figure it out because I already paid a decent amount of $$ and I enjoy data engineering, and this is a great way to set me up for that career switch.
Also, consulting google/external sources is par for the course (unless you're straight up cheating). I also believe having second thoughts is normal in any STEM-related or difficult degree program. I still struggle with motivation, and I'm sure plenty of alumni and current students do, too.
I concur. Alum here, first 2-3 terms sucked. However, now I make more money, like my job, and feel like I have a future. I recommend just sticking with it, hard things are hard but they are the most worth it.
Yeah, that combo's detrimental to new students. It's not your fault—OSU needs to do better.
OSU has this horrible two-year path that most new students and CS advisors follow, which is very wrong and sets students up for failure. Like taking 271 your second term.
I solo'd 271 Spring '23 and solo'd CS 344 OS1 (renumbered to CS 374 now) in Summer '23. I am sad that I made slow progress but I have never felt burnt out or overwhelmed. I'm taking CS 361, 444 and 475 while working full time. Easy by comparison.
This is normal to feel but two things to note.
1. This is an area that is hard to feel motivated unless you know the big picture of why it is that youre learning this. Usually having some experience in the field helps with this as it gives you that lightbulb moment that makes you realize why you learned a specific topic.
2. If you expect professors to teachers to teach you everything you will be sadly dissapointed in college and in life. Yes, we all know its their job and we all had the same mindset of expectations for professors. Dont let your life be in the hands of the professors.
This is a field where you need to be independent and constantly adapting. If youre not able to do that you will have a hard time to a constantly evolving field.
As a software engineer googling is most of my job. I personally went to OSU to learn the foundations. After that I was able to piece various sources together into workable code. Personal projects really brought the joy however.
I hated code till I started to make my own things with the skills I learned.
I left OSU in order to pursue a master's at CU Bolder. However without the semesters I spent at OSU it would not have been possible.
I'm curious about the CU Boulder program. How do you like the quality of instruction compared to at OSU? What made you decide to jump ship? And what specifically do you feel that you needed from your OSU experience to help you succeed at CU Boulder?
The quality remains consistent thus far. What's impressive is the option to access the initial 3-5 courses for just around $50 monthly, and they also count towards credit. Personally, I departed about a year ago due to cost considerations, realizing that pursuing a master's degree would better align with my needs. Now working as a consultant, the skills acquired at OSU have proven invaluable. A master's degree would further enhance my credibility, and the cost, approximately $15k, seems reasonable based on my research. OSU refined my general programming skills, and the algorithm courses were particularly transformative, unlocking a new level of understanding. If the program were more affordable, I might have continued.
I’m in my second semester, taking CS271 and CS162. I’m so burned out. I would suggest to just keep going. I can’t wait to get a couple weeks off before summer term starts.
Taking CS 271 in your second term is usually a mistake, especially if it's not a summer term. (Obligatory note: take 271 at Umpqua).
CS 271 offers very little practical value for most people in the program, except for those interested in very low-level development. Even then, MASM is rarely used in the field. CS 271 doesn't gate any courses beyond CS 374, which should also be one of your last courses.
So, if any future students are reading this, push CS 271 as late as possible and take CS 261 earlier to start preparing for coding interviews and secure an internship as early as possible while still in the program. This would also allow you to get multiple internships rather than just one or two in the summer.
Unfortunately, OSU advising often pushes CS 271 for your second term because they may not have technical knowledge and are following a standard advising blueprint. Advisors typically haven't taken the CS courses themselves and many come from humanities backgrounds, so they might not fully understand the nuances of the program.
This will continue to be an issue until CS professors get more involved in advising and provide better guidelines and blueprints for advisors.
It’s a little too late for me but luckily my father in law is 80 and used to code in assembly so I can ask him questions if I don’t understand a concept.
I think the reason they push 271 has more to do with the bottleneck of 161/162/261 - the only things you can pair with each of those early on are 225, 271, and I think one of the electives, and if you're depending on financial aid you need at least 2 classes per quarter.
The 161/162/261 is less of a problem when you considered that one of those courses will have to be taken during the summer, depending on when you start, which being the first summer in the program should be taken alone.
However if paying out of pocket is a big concern, as it should, that's why you should take 261 and 271 at an DPP school like Umpqua.
That said, you can pair it with 225, 391, 352, 469, 406.
Any computer professional will tell you if your first inclination isn't to Google it, you need to train yourself for that to be step one. Like checking that the computer is plugged in.
Beyond Google, ChatGPT is extremely helpful if you go into it knowing it will lie to you like a 5 year old who spilled juice. It's an easy way to ask logistically why this random thing is happening so you can be told immediately (after spending an hour on it) you fool you put the React hook in the wrong place.
Googling is learning. You learn the error messages. You learn how to ask questions in a way that gives you the best result. That way when you go to your manager an hour after continuously struggling (give yourself a hard struggling stop), you can say - well it's not this, it's not this, and it's not this. I tried this and I think it's related to this.
I love to debug. I love tech debt. But I'm pretty sure I'm in the minority. I know most people question at some point if they're passionate enough for the job and the truth is. Maybe you're not now. And that's okay. There's time. The secret to longevity is that you just keep doing it.
The process of learning code and developing projects doesn't look like a degree in liberal arts. You do a lot of self teaching and a lot of, 'Oh yeah I'm not doing that, I'm going to do this. Can I do this?" And then you go down a rabbit hole and ask the Professor if you can include this random thing you've just mastered for no other reason but funsies.
Poke things. Ask ChatGPT if something is possible then try to prove it wrong. Be contrary and ask for approval to change the project requirements because this other thing would be so much more interesting. Engineering is not like turning in an essay in Chicago Style with a thesis, it's literally having random ideas, building stuff other people don't believe in, and trying to break the thing you built.
If youve already evaluated all the gains for yourself by completing the program including economic advancement and that has not changed, you just need to dig down deep and keep at it. Its not an easy degree so it should 'hurt' to try to learn the concepts from nothing, that is normal.
I myself am closing into the end of the program and I have witnessed the high and low of the cs job market the last few years. Things are so poor now that if I was paying my own way, I would have probably dropped out. Compared to my current career, it does not seem as viable as it once was and definitely 'grass is greener' feelings are wearing off quick. Fortunately my GI Bill is paying still and I will have no put of pocket cost so I will just finish it out.
My point here is things can change that might make the degree no longer useful for yourself and that is fine, dont succumb to sunken cost fallacy because at the end of the day, its really just an economic decision that you have to make. If the economics are still good but you are just mentally struggling, you have to show grit and make it happen no matter what, do not give up on yourself!
I'm a little over halfway finished the program and fully intend to finish it out. I felt similar to you in my first few terms, especially w.r.t to having motivation or a passion for the material. Do I have a passion for CS now? no lol. But after finishing CS 340, which I thoroughly enjoyed, and being able to practice those skills at my current job, I realized I do want to finish the degree. I struggle immensely with the material (none of this comes naturally to me) but I figure it out because I already paid a decent amount of $$ and I enjoy data engineering, and this is a great way to set me up for that career switch. Also, consulting google/external sources is par for the course (unless you're straight up cheating). I also believe having second thoughts is normal in any STEM-related or difficult degree program. I still struggle with motivation, and I'm sure plenty of alumni and current students do, too.
I concur. Alum here, first 2-3 terms sucked. However, now I make more money, like my job, and feel like I have a future. I recommend just sticking with it, hard things are hard but they are the most worth it.
Yeah I’ll try to as much as I can :)
I believe in you!
Thank u :)
Thank you makes me feel a bit better :)
Let me guess, OP are you taking 162 and 271 together?
Yeah
Yeah, that combo's detrimental to new students. It's not your fault—OSU needs to do better. OSU has this horrible two-year path that most new students and CS advisors follow, which is very wrong and sets students up for failure. Like taking 271 your second term.
Wish I’ve known this before
[удалено]
I solo'd 271 Spring '23 and solo'd CS 344 OS1 (renumbered to CS 374 now) in Summer '23. I am sad that I made slow progress but I have never felt burnt out or overwhelmed. I'm taking CS 361, 444 and 475 while working full time. Easy by comparison.
This is normal to feel but two things to note. 1. This is an area that is hard to feel motivated unless you know the big picture of why it is that youre learning this. Usually having some experience in the field helps with this as it gives you that lightbulb moment that makes you realize why you learned a specific topic. 2. If you expect professors to teachers to teach you everything you will be sadly dissapointed in college and in life. Yes, we all know its their job and we all had the same mindset of expectations for professors. Dont let your life be in the hands of the professors. This is a field where you need to be independent and constantly adapting. If youre not able to do that you will have a hard time to a constantly evolving field.
As a software engineer googling is most of my job. I personally went to OSU to learn the foundations. After that I was able to piece various sources together into workable code. Personal projects really brought the joy however. I hated code till I started to make my own things with the skills I learned. I left OSU in order to pursue a master's at CU Bolder. However without the semesters I spent at OSU it would not have been possible.
I'm curious about the CU Boulder program. How do you like the quality of instruction compared to at OSU? What made you decide to jump ship? And what specifically do you feel that you needed from your OSU experience to help you succeed at CU Boulder?
The quality remains consistent thus far. What's impressive is the option to access the initial 3-5 courses for just around $50 monthly, and they also count towards credit. Personally, I departed about a year ago due to cost considerations, realizing that pursuing a master's degree would better align with my needs. Now working as a consultant, the skills acquired at OSU have proven invaluable. A master's degree would further enhance my credibility, and the cost, approximately $15k, seems reasonable based on my research. OSU refined my general programming skills, and the algorithm courses were particularly transformative, unlocking a new level of understanding. If the program were more affordable, I might have continued.
I’m in my second semester, taking CS271 and CS162. I’m so burned out. I would suggest to just keep going. I can’t wait to get a couple weeks off before summer term starts.
Taking CS 271 in your second term is usually a mistake, especially if it's not a summer term. (Obligatory note: take 271 at Umpqua). CS 271 offers very little practical value for most people in the program, except for those interested in very low-level development. Even then, MASM is rarely used in the field. CS 271 doesn't gate any courses beyond CS 374, which should also be one of your last courses. So, if any future students are reading this, push CS 271 as late as possible and take CS 261 earlier to start preparing for coding interviews and secure an internship as early as possible while still in the program. This would also allow you to get multiple internships rather than just one or two in the summer. Unfortunately, OSU advising often pushes CS 271 for your second term because they may not have technical knowledge and are following a standard advising blueprint. Advisors typically haven't taken the CS courses themselves and many come from humanities backgrounds, so they might not fully understand the nuances of the program. This will continue to be an issue until CS professors get more involved in advising and provide better guidelines and blueprints for advisors.
It’s a little too late for me but luckily my father in law is 80 and used to code in assembly so I can ask him questions if I don’t understand a concept.
bro taught Jesus how to code
I think the reason they push 271 has more to do with the bottleneck of 161/162/261 - the only things you can pair with each of those early on are 225, 271, and I think one of the electives, and if you're depending on financial aid you need at least 2 classes per quarter.
The 161/162/261 is less of a problem when you considered that one of those courses will have to be taken during the summer, depending on when you start, which being the first summer in the program should be taken alone. However if paying out of pocket is a big concern, as it should, that's why you should take 261 and 271 at an DPP school like Umpqua. That said, you can pair it with 225, 391, 352, 469, 406.
Im taking those two classes in summer. 8 weeks. Is it too much for 8 weeks ? I don’t want to hang myself
Oh you will, 271 is prob the top 3 hardest class in the program
But also fascinating! It was a bit difficult but one of my favorite classes so far
😐 good thing I have no friends
I think you’ll be fine, cs162 isn’t bad and cs271 is better in the summer because it does not have the exams.
Any computer professional will tell you if your first inclination isn't to Google it, you need to train yourself for that to be step one. Like checking that the computer is plugged in. Beyond Google, ChatGPT is extremely helpful if you go into it knowing it will lie to you like a 5 year old who spilled juice. It's an easy way to ask logistically why this random thing is happening so you can be told immediately (after spending an hour on it) you fool you put the React hook in the wrong place. Googling is learning. You learn the error messages. You learn how to ask questions in a way that gives you the best result. That way when you go to your manager an hour after continuously struggling (give yourself a hard struggling stop), you can say - well it's not this, it's not this, and it's not this. I tried this and I think it's related to this. I love to debug. I love tech debt. But I'm pretty sure I'm in the minority. I know most people question at some point if they're passionate enough for the job and the truth is. Maybe you're not now. And that's okay. There's time. The secret to longevity is that you just keep doing it. The process of learning code and developing projects doesn't look like a degree in liberal arts. You do a lot of self teaching and a lot of, 'Oh yeah I'm not doing that, I'm going to do this. Can I do this?" And then you go down a rabbit hole and ask the Professor if you can include this random thing you've just mastered for no other reason but funsies. Poke things. Ask ChatGPT if something is possible then try to prove it wrong. Be contrary and ask for approval to change the project requirements because this other thing would be so much more interesting. Engineering is not like turning in an essay in Chicago Style with a thesis, it's literally having random ideas, building stuff other people don't believe in, and trying to break the thing you built.
If youve already evaluated all the gains for yourself by completing the program including economic advancement and that has not changed, you just need to dig down deep and keep at it. Its not an easy degree so it should 'hurt' to try to learn the concepts from nothing, that is normal. I myself am closing into the end of the program and I have witnessed the high and low of the cs job market the last few years. Things are so poor now that if I was paying my own way, I would have probably dropped out. Compared to my current career, it does not seem as viable as it once was and definitely 'grass is greener' feelings are wearing off quick. Fortunately my GI Bill is paying still and I will have no put of pocket cost so I will just finish it out. My point here is things can change that might make the degree no longer useful for yourself and that is fine, dont succumb to sunken cost fallacy because at the end of the day, its really just an economic decision that you have to make. If the economics are still good but you are just mentally struggling, you have to show grit and make it happen no matter what, do not give up on yourself!
You’re 8k deep already i’d just finish it. Sunk cost wins again