Best advice is just build stuff, and always work on your portfolio and resume. The more you can showcase that you've accomplished the better.
Ask HN: Where should I start as a 34-year-old switching to software as a career?
61–70 of 132 posts
Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#62If it’s any encouragement, I started cold with iOS at age 40. I knew nothing but a little bit of C.
If you learn the program, there will be people who need your skills.
Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#63Develop any software for your domain (lab technician or microbiology) that solves a simple problem you see or encounter daily. Identify a problem in your current day job that can be solved with software like recording data in the lab, tracking supplies, etc. (nothing too complex) and come up with a solution (website to check-in/check-out, mobile app (?), etc.) and learn how to build it. It will not be perfect but you…
Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#64Develop any software for your domain (lab technician or microbiology) that solves a simple problem you see or encounter daily. Identify a problem in your current day job that can be solved with software like recording data in the lab, tracking supplies, etc. (nothing too complex) and come up with a solution (website to check-in/check-out, mobile app (?), etc.) and learn how to build it. It will not be perfect but you…
The son of a friend graduated from a CS degree last year and still doesn’t have a job. I told him if he wants to be a software developer, then he should just develop software, and showed him some scripts and games i’d written in Pythonista on my phone. Nobody has to give you permission. High quality dev frameworks can be got for free. You can run web apps on a free tier on Google or AWS web hosting. Developing mobile apps is easy these days and dev accounts with Google or Apple are very affordable. Get a GitHub account for your projects and build up some rep on Stack Overflow. You don’t even need to do anything super fancy or commercial, just interesting or fun or novel and demonstrate an understanding of a range of technologies. Put links to all of these on your resume.
Set yourself objectives. 4 months to get a web app running on Google App Engine (you can get a tutorial app working in an afternoon!). A month to figure out Github and upload it, and do this for future projects. 2 months to port it to AWS. 4 months to get an app into the Play Store, or App Store. All this can be done in spare time, half the time following tutorials and the rest on whatever your apps do.
Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#65Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#66Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#67I did the same thing when I was 28. I had some prior exposure to Java at university but that's about it. I took a year off from work to teach myself to become a software engineer. It takes hard work and you will doubt yourself while you're doing it. My advice is to get your fundamentals right, everything else depends on it. With fundamentals I mean, learn your algorithms, understand how a program actually runs by wri…
Tell me why someone picking up Python/JS should learn the above mentioned things, rather than learn basic security principles and not pip/npm install blindly all the packages without checking the source? Change my mind.
Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#68Re: Ask HN: Where should I start as a 34-year-old switching to software as a career?
#69I did the same thing when I was 28. I had some prior exposure to Java at university but that's about it. I took a year off from work to teach myself to become a software engineer. It takes hard work and you will doubt yourself while you're doing it. My advice is to get your fundamentals right, everything else depends on it. With fundamentals I mean, learn your algorithms, understand how a program actually runs by wri…
>interpreters, compilers, memory hierarchy Those are nice if you want to do embedded and C. A complete waste of time for Frontend/Backend, mobile and desktop people in the beginnings. Tell me why someone picking up Python/JS should learn the above mentioned things, rather than learn basic security principles and not pip/npm install blindly all the packages without checking the source? Change my mind.
The generalisability is more obvious in something like physics where the same physical laws apply in different domains.
Computer science doesn't have axiomatic physical laws, but it does have recurring concepts. If you learn about memory hierarchies in computer architecture, you can apply similar principles in dealing with caching systems in web-applications.