While the general consensus tends to favor “functionally rich” issue-tracking systems, such as Jira, to manage “real” software projects, our experience shows that what really maximizes the traction of a project is how close everybody is to the code rather than how sophisticated the project management tool is. In fact, we found that choosing a simpler but more integrated tool, such as Github, with a well-thought-out set of best practices can be a robust platform for a highly effective agile development. Rather than going too much into the theory, here is our 100% Github-based agile development process.
The crust of an effective agile and high-velocity development process is less about fancy naming and disruptive tools or languages, and more about defining a well-thought-out iterative process with a clear set of roles and forward-looking deliverables that bring a minimalistic but robust and predictable production chain. Following our previous vDev methodology introduction, this article goes the next level down to explore how the right set of roles and deliverable goals can dramatically improve speed and precision of vDev 5D process.
Speed is how fast something moves, velocity is how fast something moves in a given direction. In software terms, we could say that speed is how fast code gets produced (e.g., proof of concept, demo, first pass at something), whereas, velocity is how fast an experience gets delivered. Unfortunately, speed has been the obsession of our industry lately, with the assumption that if one developer could do Y in one day, thanks to a great new technology or framework, then, it will obviously linearly scale with time and developers. Managers hear what they want to hear, developers use what they want to use, and the honeymoon starts.
The software technology industry is like an ants’ nest. From up close, everything seems random, chaotic, and purposeless, but as we zoom out, pattern, order, and purpose begin to emerge. At least, this is the way I see it. While I love to get very close to the smallest details, once in a while, I like to step back and see how we, the software industry, came to where we are in order to better understand where we are going.
Given the profusion of HTML5 libraries and frameworks, choosing the right HTML5 technologies for your HTML5 application could be a daunting task. At BriteSnow, we build high-end HTML5 applications for a living, and our two main guidelines to select HTML5 technologies are as follows:
Front-end HTML5 developers have a lot to learn in order to build high-end HTML5 applications, and the learning process can quickly become overwhelming if not tackled the right way.
From a conceptual point of view, here are the 11 important HTML5 concepts that a good HTML5 front-end developer should understand:
Understanding HTML5 can be a bit overwhelming at times, especially when reading all the buzz and articles about it. The starting point to correctly understand HTML5 is that HTML5 is HTML, and its biggest value for application developers is the fact that all browser providers (e.g., Google, Apple, Mozilla, and Microsoft) are now competing on compliance and performance on a single set of specifications (e.g., HTML5 and CSS3).
Welcome to BriteSnow, Inc., a top-notch HTML5 Web and mobile application development shop located along the top-edge of the Silicon Valley in San Francisco.