I finished up my first workflow prototype yesterday. I took the best of from a variety of sources I accumulated over a long period of time, and created what works for me 0n very small projects that have no hope of expansion/scale. I used a completed project to implement the workflow, and pushed the new additions to Github. Link to the repo:
To see how it looks live (this was done before I added the workflow, but I did add everything to this branch as well and then igored it in my .gitignore file, which is included in the remote branch), please visit:
Note: After I finished this workflow, I decided to take another much larger project and implement a new workflow setup. When I first created this next project, I knew nothing of modularizing workflows, modularization, very little of Angularjs, and nothing about Reactjs. will soon be delving into React.js on Free Code Camp, further modularizing my code with various npm tools, implementing Sass on a larger scale, and developing workflows for these given situations. In my search for great workflow documentation regarding Gulpjs (which I totally love), I came across this fabulous website by a German Front End Developer:
Not only is he a great Front End Developer, but he is also a great writer. His documentation is amazing. I’m sure he initially created it as a reference for himself and then posting it made it available to everyone else. He was so smart to take the time to do it.
That’s what I am trying to achieve with this website, and why I changed the tagline to “My Developer Notebook”.
I encourage people to leave comments, suggestions, questions here. Looking forward to hearing from you! And thanks to those who have already given me comments on Facebook. One comment inspired me to immediately go onto my next developer workflow following Stefan’s lead with Gulp in the center of it all.
If you are pursuing web development as a “second” career (or third or fourth, and so on) as I am, don’t be discouraged. It’s always very hard starting out. But if you work hard, focus, and don’t give up, you will eventually catch on. Sticking to it is half the battle! Giving up won’t get you anywhere. And these days, many of those skills are becoming more and more important for non-developers as well. It’s a brand new world!
Why Developers Write Horrible Documentation and How to Solve It: I personally am more for great written documentation. It’s easier to follow than a video, though video has its purpose in other ways. Good documentation isn’t just for clients. It’s also for other developers, like those you work with. That’s especially what the post talks about. Not clients. Although, that’s a fair point too. My point is that it should be a part of the normal workflow. Having the attitude “the client does not want to pay for it” will come back to haunt the developer who created the bad documentation. That is not a good attitude to take on. And, I am more for written documentation within the project as per usual rather than video.
Automate Your Tasks Easily with Gulpjs: The thing that I took away from this was adding JSHint to my workflow. Very glad I did. It’s a good read, but there are a few little holes here and there. To read my post on that, please visit Adding Gulp To Your Front End Workflow.