My biggest struggle is to start doing something. I get 'blank page syndrome' every time I try to start a new personal project.
I've only been studying programming for around 1,5 years so I know that I'm still fairly new and shouldn't beat myself up but I hate that I still can't figure out how to "just start".
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Best thing you can do from my experience is to create a repo, then the server folder, then the CI script, then adding a bundler like Parcel.js, create an index.html (or index.js), adding the watch/serve custom script to your package.json file, and writing a quick read me like (yarn install, yarn serve) and so. Then the .gitignore to not push node_modules, IDE files (like .idea from jetbrains or another) and .cache folder.
At this point you should push the package.json and readme.md to your repo and test the pipeline.
You'll need all those steps if you want to create a project from scratch anyway and you'll have the structure ready to begin. At this point is easier to follow next steps like thinking on the shape you want for your project (backend and frontend techs, DB and so).
The easy path to follow is having a cheap hosting which usually runs PHP and MySQL so you only have to concern about frontend.
You can check this article for a full project workaround (where I explain all the steps for a static site, but you can extrapolate it to whatever you want).
If you want or need a tutorial for a full stack project tell me and i'm doing it when I can =D
At this point you'll have too much done to retreat. With experience all those steps could take you only 30min but even then, you'll always see the repo everytime you enter your gitlab, github or whatever, and same for the project directory inside your hosting so it's a nice motivation to keep on!
If you want to do something but don't know why, simply check internet for ideas and build your own version of something you like
Ah yeah. Have you thought about why that is? Sometimes, it helps to understand the why and you can then address that to help you get started?
Personally, I've started personal projects because I had a problem I couldn't just google a solution for.
A lot of times, I get daunted at the size of potential projects, but I found that it helps to start very small. Like, just get the project created. And add one tiny feature. And if that feature is turning into hours, I break it down into smaller chunks further.
I think it's because I'm still scared to fail. I've always been a perfectionist and if I fail I just MUST fix it right away, and since I'm still quite new it's hard to find the resources and help that I might need to make something work as I envisioned it from the beginning
I'm trying to do like you do, to break it down into smaller pieces but it's hard as I can only see the big picture :P
It's very hard to let go. But it's good that you realize this.
I've learned to cope with this by not saying no, but by saying yes, LATER (and writing this down as an issue in github). Maybe this can help you too? :) Something like...
X is not working right. Research and look into this.
And then add a TODO note in your app.
It really is quite difficult looking into things as you encounter them, especially with new stuff. I struggle with this a lot when I play with new technologies I'm not familiar with. Takes a lot of brain power.
That's actually a really good idea! I've never been able to say no when I start to write some code, but I've never tried yes, LATER approach. I will definitely try this for my upcoming project.
The TODO might also be of help, then I have a "list" of things I WANT to do, but later
I agree with you, since everything is kind of new to me right now it REALLY takes a lot of brain power.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
And think that you need to set steps to yourself (and your learning curve).
I mean, if you are not a deep professional on something, how do you manage to know if it's perfect, good or bad?
First center yourself on a "If it works, it's perfect" situation, when you are used to this and get more experience, you'll see your own code from 6 months ago and think "what a shit I coded", which is totally natural, specially on the first 3-4 years of coding so you can refactor it to a newer version with your current knowledge.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My biggest struggle is to start doing something. I get 'blank page syndrome' every time I try to start a new personal project.
I've only been studying programming for around 1,5 years so I know that I'm still fairly new and shouldn't beat myself up but I hate that I still can't figure out how to "just start".
Best thing you can do from my experience is to create a repo, then the server folder, then the CI script, then adding a bundler like Parcel.js, create an index.html (or index.js), adding the watch/serve custom script to your package.json file, and writing a quick read me like (yarn install, yarn serve) and so. Then the .gitignore to not push node_modules, IDE files (like .idea from jetbrains or another) and .cache folder.
At this point you should push the package.json and readme.md to your repo and test the pipeline.
You'll need all those steps if you want to create a project from scratch anyway and you'll have the structure ready to begin. At this point is easier to follow next steps like thinking on the shape you want for your project (backend and frontend techs, DB and so).
The easy path to follow is having a cheap hosting which usually runs PHP and MySQL so you only have to concern about frontend.
You can check this article for a full project workaround (where I explain all the steps for a static site, but you can extrapolate it to whatever you want).
If you want or need a tutorial for a full stack project tell me and i'm doing it when I can =D
At this point you'll have too much done to retreat. With experience all those steps could take you only 30min but even then, you'll always see the repo everytime you enter your gitlab, github or whatever, and same for the project directory inside your hosting so it's a nice motivation to keep on!
If you want to do something but don't know why, simply check internet for ideas and build your own version of something you like
I've been toying with programming since 1984, since 1988 professionally. I still draw a blank when I want to start something new.
That was actually a big relief to read. It took some of the stress of my shoulders! Thank you!
Ah yeah. Have you thought about why that is? Sometimes, it helps to understand the why and you can then address that to help you get started?
Personally, I've started personal projects because I had a problem I couldn't just google a solution for.
A lot of times, I get daunted at the size of potential projects, but I found that it helps to start very small. Like, just get the project created. And add one tiny feature. And if that feature is turning into hours, I break it down into smaller chunks further.
I think it's because I'm still scared to fail. I've always been a perfectionist and if I fail I just MUST fix it right away, and since I'm still quite new it's hard to find the resources and help that I might need to make something work as I envisioned it from the beginning
I'm trying to do like you do, to break it down into smaller pieces but it's hard as I can only see the big picture :P
Ah! I struggle with being a perfectionist too!
It's very hard to let go. But it's good that you realize this.
I've learned to cope with this by not saying no, but by saying yes, LATER (and writing this down as an issue in github). Maybe this can help you too? :) Something like...
And then add a
TODOnote in your app.It really is quite difficult looking into things as you encounter them, especially with new stuff. I struggle with this a lot when I play with new technologies I'm not familiar with. Takes a lot of brain power.
That's actually a really good idea! I've never been able to say no when I start to write some code, but I've never tried yes, LATER approach. I will definitely try this for my upcoming project.
The
TODOmight also be of help, then I have a "list" of things I WANT to do, but laterI agree with you, since everything is kind of new to me right now it REALLY takes a lot of brain power.
Thank you for great advice!
And think that you need to set steps to yourself (and your learning curve).
I mean, if you are not a deep professional on something, how do you manage to know if it's perfect, good or bad?
First center yourself on a "If it works, it's perfect" situation, when you are used to this and get more experience, you'll see your own code from 6 months ago and think "what a shit I coded", which is totally natural, specially on the first 3-4 years of coding so you can refactor it to a newer version with your current knowledge.