PART 1: THE PROBLEM STATEMENT AND THE END SOLUTION

The entire WeBill development ethos is underwritten by the guiding principle that all of our developers must adhere to the WeBill design and methodology. When we carry out code reviews all the code developed by Tim must be indistinguishable in style and form from the code developed by myself or Jedd. In an enterprise scale development of the magnitude of WeBill single-man dependency and individual idiosyncrasies are anathema. New developer recruits are taught the methodology, design and style, and, within a month or two, can swim in the code developed months ago by developers who have long departed from the company. Sustainability of code is crucial and methodology is key. What I mean by “methodology” is difficult to articulate but it includes design, style, template and convention. We strive to be at the cutting edge of technology, and, at times, templating and convention can dumb down complexity, but it works for us. We have a factory-line development process which we believe deals with cutting edge technology and issues. …

About

Ayal Rosenberg

Founder of WeBill — where we aim to change the way utilities are managed for the consumer.

Get the Medium app