I manage Operations at Chingu, Inc. We help bridge the knowledge you have gained via your learning activities and the experience employers seek through global remote team projects. Come join us.
Location
St. Louis
Education
Southeast Missouri State University, Webster University
Both! I get a lot of satisfaction working on existing project that I believe in and am passionate about. But, I also work on new projects because our growth is limited if we don't broaden our horizons.
A little of newbie Syndrome ? Like having to learn and understand what the other people done to the project and how I make meaningful contributions.
It is probably fear tbh
This is all pretty normal. Ideally people involved in the project can provide as much guidance and empathy as possible. And otherwise merely hanging around where discussions happen goes a long way.
Relatable! I get stuck at understanding the logic, the code practices followed and end-up asking so many questions to fellow devs. This initial phase makes you a little uncomfortable and you start getting into the imposter syndrome zone but once you pass this, every time you get to learn so much out of this.
I personally prefer starting projects from scratch but I have started to contribute to the existing projects whenever possible.
Depends. If I get better experience and meet new people on working on existing ones or make something on my own to not have built on not making anything myself.
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
I really like seeing a project come together. I like the feeling of taking it to the next level. Starting new things all the time seems like you never get anything too far along.
My /temp directory disagrees. There are 100s of quick projects left here to be forgotten forever. Really though I like to start simple new projects to shake out new ideas that I intend to implement on existing projects. Sometimes I come up with good ideas. Many times I am glad that I tried it in a toy project, learn from it, and move on.
I love the planning and design so green field is exciting (not that it often happens), BUT working in legacy code is more satisfying when you can bend old spaghetti to your will.
Both! Coz, I like reading code is written by another developer, so I can learn their logic and their structure "how", "why", "what", "who", and "where" they go first and make the plot and twist in the app they have work with.
In the new project, on my own; it's nice to go and make something good and make the client happy with their hope and goals.
Oldest comments (29)
Both! I get a lot of satisfaction working on existing project that I believe in and am passionate about. But, I also work on new projects because our growth is limited if we don't broaden our horizons.
I like starting things but mostly because I always feel lost jumping into something already going on.
What makes you feel lost?
A little of newbie Syndrome ? Like having to learn and understand what the other people done to the project and how I make meaningful contributions.
It is probably fear tbh
This is all pretty normal. Ideally people involved in the project can provide as much guidance and empathy as possible. And otherwise merely hanging around where discussions happen goes a long way.
Guess I got a find a project!!!
thepracticaldev/dev.to 😉
Relatable! I get stuck at understanding the logic, the code practices followed and end-up asking so many questions to fellow devs. This initial phase makes you a little uncomfortable and you start getting into the imposter syndrome zone but once you pass this, every time you get to learn so much out of this.
I personally prefer starting projects from scratch but I have started to contribute to the existing projects whenever possible.
Depends. If I get better experience and meet new people on working on existing ones or make something on my own to not have built on not making anything myself.
No matter the project is new or existing one development challenges are always there. So I would prefer working on both.
I used to like starting things but I think I've swung hard in the other direction being years into something I once started.
I have a hard time sitting down and doing all the base work for brand new things.
There are few things more satisfying than turning an old convoluted mess of code into something clean, organized, and maintainable.
...why my GitHub is packed full of quarter-baked messy unfinished ideas is beyond me.
Absolutely -- refactoring is good for the soul.
I really like seeing a project come together. I like the feeling of taking it to the next level. Starting new things all the time seems like you never get anything too far along.
My
/tempdirectory disagrees. There are 100s of quick projects left here to be forgotten forever. Really though I like to start simple new projects to shake out new ideas that I intend to implement on existing projects. Sometimes I come up with good ideas. Many times I am glad that I tried it in a toy project, learn from it, and move on.I love the planning and design so green field is exciting (not that it often happens), BUT working in legacy code is more satisfying when you can bend old spaghetti to your will.
Preferably new, but I don't mind existing as long as it's not spaghetti code with a best before date of ~2009...
Nice maintainable code base, with proper documentation and tests? Don't mind working on that one bit.
Both! Coz, I like reading code is written by another developer, so I can learn their logic and their structure "how", "why", "what", "who", and "where" they go first and make the plot and twist in the app they have work with.
In the new project, on my own; it's nice to go and make something good and make the client happy with their hope and goals.