Cole Turner is a senior software engineer, based in the Bay Area (CA), who specializes in: developing web application products, seamless user experience, and cross-functional communications.
Hey Nokol, that is a great question. Could you elaborate on what you mean by "Private" and "Job"? Are you asking more about how I would organize the code, or how to build it on a team?
Cole Turner is a senior software engineer, based in the Bay Area (CA), who specializes in: developing web application products, seamless user experience, and cross-functional communications.
That's a great question, it will definitely depend on whether there is a team working on the project or not. When I work privately, I tend to experiment more and follow the least path of resistance. This will mean that I am okay with some sloppy code because nobody else will have to share the ownership.
When working in a job or a team, I will structure my code differently to make it easier to maintain and update. This means that if someone else is looking at my code, it's clearer to understand what is going on, it's documented, and even easy to delete. After I check in my code, it's no longer "my" code it becomes "our" code.
Cole Turner is a senior software engineer, based in the Bay Area (CA), who specializes in: developing web application products, seamless user experience, and cross-functional communications.
Which ES6 Javascript design pattern do you prefer for a small-medium sized project :
1 Private
2 Job
Hey Nokol, that is a great question. Could you elaborate on what you mean by "Private" and "Job"? Are you asking more about how I would organize the code, or how to build it on a team?
Private - Projects that should not bring profit in the first sense, just for fun or out of interest. Not meant for others to maintain the code
Job - Working together with other developers.
I'm interested how you would organize the code, maybe you have good github repo links.
Thanks you! :)
That's a great question, it will definitely depend on whether there is a team working on the project or not. When I work privately, I tend to experiment more and follow the least path of resistance. This will mean that I am okay with some sloppy code because nobody else will have to share the ownership.
When working in a job or a team, I will structure my code differently to make it easier to maintain and update. This means that if someone else is looking at my code, it's clearer to understand what is going on, it's documented, and even easy to delete. After I check in my code, it's no longer "my" code it becomes "our" code.
I added more information and detailed my preferred private stack here:
cole.codes/posts/ask-me-anything-c...
very very cool of you, thank you for detailed answer. Glad to hear that not everyone works "clean" private :-)