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.
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.