An interesting tool/technology I encountered in preparation for Bootcamp
I once had to collaborate with a software developer friend, like myself, on a test project after our training programme. My role was to code the backend using php programming language. After he was done with the frontend design, he forwarded the project. After loading the pages on the browser, what I saw was a job well done, but bad news followed. I opened the code on my text editor and saw this:
His markup was very terrible. Even though it produced a nice interface in the end, it was not something any other developer could work with. Guess who had to suffer terribly. I was almost dehumanized.
On working with node.js in preparation for the Andela bootcamp, I stumbled into the ESLint. I had to struggle first to get acquainted with all the best practices and standards, but once I did, I was good to go.
ESLint gets annoying, especially in cases where it does not consider that I am in hurry to meet up with deadlines. It still demands that I fit all my code within it’s rules. I hate to see those red lines. They seem to be screaming at me. I am tempted to shout back. “Let me be, for goodness’ sake!”
Eventually, the feeling is one of calmness, to remember that any and every other developer you work with would have these rules to deal with. ESLint puts you two in the same boat to paddle in peace. You can be rest assured.
Before you clap, allow me point out one more beautiful thing about this tool: Developers can decide what rules they want to abide by. Any rule can either be turned on or off. At runtime, additional rules can be included. Now, go ahead and clap.