I just spent 1 Year learning code and I'm not sure of what I should do next
Around 1 year ago, I started learning how to code to be able to build SaaS apps, and to be more fulfilled in my career. (in the future, I would like to own & manage a portfolio of SaaS apps)
I learned while having a part-time job in Marketing, and part-time School. Some moments were hard, I also lost motivation a few tiles, but I still ended up learning what I wanted.
If you want to see what I've done for more context, you can check my portfolio with all the projects I made: https://web-dev-timeline.vercel.app/
(There's also a video with that talks about my experience more in depth if you want more context)
I'm now hesitating between 2 things I could do because I'm going to finish college in a few months, and I'll have some free time:
-
Start doing a bit of freelance with small short projects to be able to gain experience on real projects, and also learn from people more experienced than me
-
Start building SaaS apps by myself and try to monetize them, it is closer to my end goal, but could backfire because I'm not experienced enough
What do you guys think? Should I go for solution 1, or 2, or maybe start with 1, and then 2?
Any tips or feedback highly appreciated!
I've been building websites for 20 years and if I had to give one advice to someone who just started coding it would be: start small.
When I learned to code I felt like I can build anything. And technically nowadays you CAN build anything with just JavaScript. Facebook? Instagram? They're just React apps.
I spent many years building endgame projects that could potentially make me millions and none of them worked. What worked were the tiny websites that I built for fun on a weekend and then slowly but consistently updated for years.
So start building small saases right now. You don't need "real job" experience. The coding part is not the hardest. The hardest thing is being your own boss and maintaining focus and consistency. And you won't learn that from a monthly paycheck.
I see, so it would be interesting to ship often then, and focus on marketing, thank you sir!
A lot of the previous comments have told you to skip experience and jump right into product development. That's easy for them, because you're taking the risks.
I suspect you'd get a lot out of working for a dev team, especially if you've only been doing this for a year. Mentorship is amazing, but so is learning to work with people.
Also, you have to make sure you have enough saved to live without panic for at least a year to try your hand at building a product development.
Once you are ready to build your own products, make sure that it's something people actually want.
These are the main reasons why I'm thinking of working for other people first as a dev, or helping out at my company.
Absolutely! Working with and getting mentored by people who are 20 years more experienced than me is very valuable!
I'm thinking of building side-projects without leaving my job, I always created stuff with a job or school on the side and I like this balance :)
Thank you for your feedback!
#1 if you are in need for money , #2 if you dont need money right now, as bober noted, you want to start small scale and add on
Ok, I make an okay income with my job for a 21-Year old and I like it, so I guess #2 is better, thank you!
I second this. As a late 30-something, one of my biggest regrets is not spending using my 20s to take more risk. If you can handle it, go for it.
My recommendation is a bit less technical. You spent a year learning to code now spend the next year learning to marketing
Your point 2 : "Start building SaaS apps by myself and try to monetize them"
If I break your sentence down
Building = coding
Monetise = marketing
Marketing is a skill also
I've been doing digital marketing since a few years, I started doing FB ads when I was 16, and then got jobs as a media buyer, community manager, and video editor, and I'm learning about SEO at the moment, I'm a marketer first haha! :)
I learned how to code to be able to build my ideas + because it seemed fun
First of all excellent work you have made good progress. Now the real work begins - experience building. This is painful - you will make many mistakes - and this is all part of learning :) From 20 years + as a developer I would say :-
Golden Rules :-
Dont ever work long hours EVER - stick strictly to the core hours. If the work isnt done on time, it wasnt properly scoped. Managers dont admire juniors working long hours - they flag them as people that can easily be exploited when their deadline is looming. Being clear of what you can deliver and when you can do it by and managing expectations gives you much more respect than burning the candle at both ends !
Its difficult (read impossible) to learn, have a full time job and working on a SAAS at the same time. If you can combine the skills / technology you need in your job for your SAAS you will be making headway - even if you have time just for your full time job.
Wow, thank you for the detailed answer!
I've tried building a few projects during the last few years (https://www.alexglv.com/projects), and they were not successful, but I learned a lot about marketing, and I know I probably won't succeed from the first try with SaaS projects :)
I'm friends with the CTO at my remote job (a profitable bootstrapped ed tech SaaS app), so I could eventually ask to help to implement the Frontend of the app, it uses a very similar stack to the one I learned. :)
I won't need to do support, and the people at my company know that I'm working on projects on the side and are supportive about it as long as doesn't take too much time from work (totally understandable)
Thank you for the Golden rules you gave! I'm young, so I can overwork myself sometimes 😅
Honestly, I would find a paid job in a start-up because this is what I did.
I'm a self-taught developer since I was 13 yo.
Before my first job, I did know of to do things but I felt like I'm missing a lot of parts and it was hard for me to start freelance or do something on my own.
After 2 years working in a startup (I was the 6th employee, now we are 20) I could get many insights to complete the puzzle for me.
Now for sure I don't know everything but I understand how a small business work and what's important to a point I can do it on my own
I'm actually working at a startup where i'm an early employee as well! :)
I work here as a marketer, but I think the CTO & CEO would be ok if I took some time to help on dev tasks. I could gain experience by doing that :)
That's awesome!
You can create a side project to automate something in the business, then pitch yourself and make the transition to become a dev
Feedback to "Lofi Productivity":
Don't force people to create an account. I don't see a reason why an account should be used. Just allow usage without. The main concept is pretty nice though.
I know that this is not the best UX, but it wasn't my goal with this project.
My goal was to learn about databases, and to understand how account creation works, so I built it in this project.
But I agree with you, thanks ! :)
#2. Coding skills are important but seeing a product through from inception to gaining users and then becoming profitable requires business skills. Jump into it as fast as possible and learn from your mistakes if you make any. The sooner the better. Don't worry about messing up, it's part of the journey and hard lessons stick so you won't make them again.
It also looks like the more fun option, thank you for your feedback, Ryan ! :)
I've never been a fulltime dev. Although I have done a few dev things at my networking day job.
Been learning when I can, and building things here and there the last year. Nothing which makes me money yet.
Sorry to burst your bubble, but nobody hires inexperienced freelancers. The reason freelancers are paid so well is that they know how to do the job.
Shadowing somebody will more likely work if you just get an employed junior position or an internship somewhere.
I've already gotten a few freelance clients before getting my first job a few years ago doing simple WordPress websites, so it's possible even if I won't be as well paid as a top freelancer at the beginning.
But it's true that people would take the time to teach me more about development at a job, I actually am probably going to help the devs in the company I work at when I have free time.
Thanks for the feedback Niko!