It sounds like you might be stuck in a "tutorial loop". Put them aside for now, and try building a tiny project for yourself. It could be anything that interests you; scratch whatever itch you may have right now no matter how silly/useless it seems. The goal is to start writing code for something tangible (instead of learning the basic mechanics of whatever language for the nth time as you aimlessly cycle through tut…
Ask HN: Becoming a Software Engineer?
11–20 of 21 posts
Re: Ask HN: Becoming a Software Engineer?
#12Welcome! I definitively feel your struggle because I was there a few years ago. When I started this journey a few years ago it just seemed daunting and impossible but I remember telling myself: "people do this and I am 'people' so I do meet the minimum requirements!" I agree with other comments here that it seems like you might be stuck in a tutorial loop. Do start building something, a small project for yourself. I'…
I never considered this, so this is appreciated, and so is the help. I will send you an email for sure.
>You mentioned that you have done some R and Python, and your comment about math seems to suggest that the use of those might have been in data science-y fashion?
Yes, it was and I actually enjoyed it a lot.
Re: Ask HN: Becoming a Software Engineer?
#13I had a similar problem to you. While it was easy for me to complete assignments on Udemy or similar, I didn't develop a deep understanding of anything I am doing. What finally helped was doing the free Java course from the University of Helsinki (mooc.fi/en). What set it apart from the other courses is, that for each topic they are introducing, they have multiple, involved coding assignments and provide good automat…
Re: Ask HN: Becoming a Software Engineer?
#14Sorry to spam another course at you but if: >Resources I've tried: Codecademy, Datacamp, Udemy (automate the boring stuff, Python Bootcamp: Zero to Hero, etc), FreeCodeCamp, TheOdinProject, FutureCoder, Python.org, LearnPython.org, learncpp.com, C# for Beginners, leetcode, edabit, exercism.io, Code Wars, Code Abbey, Project Euler, Codinggame.com, books from NoStarchPress and various other books and youtube videos (e.…
Which would you reccomend?
Re: Ask HN: Becoming a Software Engineer?
#15> Am I capable of learning these things even if I find them overwhelming? Yes! Especially if you find them overwhelming - that means you've taken the first step of treading into new territory and trying to make sense of what you see. "Beginners mind" is a fantastic resource. The key is to stay in that mindset, explore, iterate, stay curious about what you observe. The only way to do that effectively (besides sheer st…
Re: Ask HN: Becoming a Software Engineer?
#16Try this: https://github.com/woadray/cs-bootcamp , it's my self made bootcamp. I came up with it as I'm 32 and attempting to switch career, even thinking about going back to university. It's hard but you will learn a lot. Take your time, there is no shortcut to studying. And YES YOU CAN.
Do you have any other 'intro' links?
Re: Ask HN: Becoming a Software Engineer?
#17This series is excellent on crossing the chasm from interested to effective: https://lowlyswe.substack.com . Code (not study, code ) 50+ hours/week for a couple years.
Re: Ask HN: Becoming a Software Engineer?
#18It sounds like you might be stuck in a "tutorial loop". Put them aside for now, and try building a tiny project for yourself. It could be anything that interests you; scratch whatever itch you may have right now no matter how silly/useless it seems. The goal is to start writing code for something tangible (instead of learning the basic mechanics of whatever language for the nth time as you aimlessly cycle through tut…
Thanks mgomez, I think you're onto something. My only difficulty with this would be the concept of 'you don't know what you don't know.
Pick a small project that you care about.
It has to be something you care about because you will pay attention to whether the results do something meaningful, which is the key to guiding you toward actually learning what you need to learn. For me, this meant making video games. For my friend a physics educator, it might mean generating random quiz questions with meaningful or realistic numbers.
It also has to be simple. For me, I started a long time ago with a text based game where you fight a sequence of monsters by basically rolling dice with tweaks and theme that mattered to me. For my friend, it might be literally randomly generating 3 random numbers and putting them into a pre-written physics problem.
There is always a way to add on to a project you care about, so start super simple and make it work really well (just meaning, to your satisfaction). Then add on another thing and try to integrate it, and so on.
My CS students when I was TAing always learned the most from long term projects that had enough freedom for them to make it fun for themselves. This is in contrast to curated sequences of academic exercises and expository text.
Re: Ask HN: Becoming a Software Engineer?
#19Earlier quoted context omitted.
Thanks mgomez, I think you're onto something. My only difficulty with this would be the concept of 'you don't know what you don't know.
I just want to second this suggestion. Pick a small project that you care about. It has to be something you care about because you will pay attention to whether the results do something meaningful, which is the key to guiding you toward actually learning what you need to learn. For me, this meant making video games. For my friend a physics educator, it might mean generating random quiz questions with meaningful or re…
Re: Ask HN: Becoming a Software Engineer?
#20It sounds like you might be stuck in a "tutorial loop". Put them aside for now, and try building a tiny project for yourself. It could be anything that interests you; scratch whatever itch you may have right now no matter how silly/useless it seems. The goal is to start writing code for something tangible (instead of learning the basic mechanics of whatever language for the nth time as you aimlessly cycle through tut…
Thanks mgomez, I think you're onto something. My only difficulty with this would be the concept of 'you don't know what you don't know.
Some people love this phase of learning the best because it can be the most exciting part ("I hadn't even heard of topic X this morning but now I know enough to be dangerous"), and some just accept this as the slog that's required to get you up to speed enough to build useful things which is the part they enjoy the most. (I'm the latter.) But either way, that's how all of us start.