workflow - Jerome Covington

Jerome Covington

Sign in Subscribe

workflow

A collection of 8 posts

Creation Myths

The more I work and think about web development, the more I think that the mystical, magical state of starting from zero and creating an innovative language, framework or web app "from scratch" is a well cultivated, but false, myth. Everything starts from something, and the ability to

Web Development: Process and Product

It seems to me, that my workflow benefits most from a posture focused on the process of web development, rather than exclusively the set of deliverables that compose a final product. It seems that this is not a unique point of view. But it does seem that focusing on the

Head in the Clouds

Although I'm not ready to make the project public yet, I've been working on something I'm calling CZR (Caesar), which is a script that you can include on your page that allows fellow developers, designers or other site stakeholders to up-vote, down-vote and comment

Lessons in Jugaad

This article [http://www.nytimes.com/2014/02/18/business/international/from-india-proof-that-a-trip-to-mars-doesnt-have-to-break-the-bank.html] from the New York Times is great. Here are a few takeaways which translate from the world of space exploration on the cheap, to web development. 1. "Ours is a contrasting, inexpensive and innovative approach to

This Front End Ops Animal

Up front, this blog post would not exist without the amazing work and progress towards pushing the Front End Ops agenda by such trailblazers as Wesley Hales and Ryan Bridges, who gave a cool talk at the Velocity 2013 conference in Santa Clara, California. Of course there are countless awesome

Tend to the Garden

There's really only one thing that will doom the codebase, and that is neglect. As you know, there is an abundance of tools and libraries out there, especially in the JavaScript community. Sometimes you're locked into using older versions for any number of reasons, some internal.

Refactoring the Process

The best managers I have had do two things well: they remove impediments to a trusted developer's understanding of the larger business purpose behind that developer's task, and they, as proficient developers in their own right, approach solving problems in what seems to me to almost

Belling the Cat

Are we on track for a future where the skills of a developer will become all but ubiquitous? Will there still be a place for product managers and UX designers unless they are not merely conversant in the tools of a developer, but proficient? Will fluency with code be a