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.
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.
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.
👋 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've never heard the term "brown-field" before but I love it.
It sounds a little woo-woo, but once I took a personality test, and one of the results said something that resonated with me:
"You don't excel at starting new things, but your biggest strength is making good things better."
So for that reason, I'll say "brown-field." I struggle with creating from scratch, but I enjoy refactoring, optimizing, and building on work that is already solid.
As a counterpoint, My favorite way to test and learn new things has been in the green field space. Create a new project, mess around, take notes, delete it at the end of the day. Sometimes when you want to plant a tree you don't want to do it in the middle of a forest.
I'm a developer-turned-business owner who loves to explore the right tools for the job. I enjoy writing and documenting my journey. I use code as one of the tools to solve real problems.
Both! Brown field because I love shaping projects to serve a (new) purpose. Green field for the same reason, but also exploration of new techniques and being able to change a lot of stuff in a short period of time. The endurance I get from brown field is important for me as well as the new and shiny stuff.
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.
Software engineer specializing in backend solutions. I collaborate with stakeholders to deliver tailored results through staff augmentation or fixed-price projects, bridging tech and business goals se
If you are a newbie and want to learn new stuff then go for existing ones because you will have to improve your analytical skills and you have to improve debugging skills ones that is done you will feel more satisfied.
Top comments (29)
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.
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 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.
I like starting things but mostly because I always feel lost jumping into something already going on.
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.
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 😉
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've never heard the term "brown-field" before but I love it.
It sounds a little woo-woo, but once I took a personality test, and one of the results said something that resonated with me:
"You don't excel at starting new things, but your biggest strength is making good things better."
So for that reason, I'll say "brown-field." I struggle with creating from scratch, but I enjoy refactoring, optimizing, and building on work that is already solid.
As a counterpoint, My favorite way to test and learn new things has been in the green field space. Create a new project, mess around, take notes, delete it at the end of the day. Sometimes when you want to plant a tree you don't want to do it in the middle of a forest.
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! Brown field because I love shaping projects to serve a (new) purpose. Green field for the same reason, but also exploration of new techniques and being able to change a lot of stuff in a short period of time. The endurance I get from brown field is important for me as well as the new and shiny stuff.
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.
If you are a newbie and want to learn new stuff then go for existing ones because you will have to improve your analytical skills and you have to improve debugging skills ones that is done you will feel more satisfied.