One of the great things about the Internet is how it has made it easier to put great ideas into practice. Whether the ideas are about improving people’s lives or a new way to sell and old-fashioned product, there’s nothing like a good little startup tale of creative disruption to deliver us from something old and tired.
We work with a lot of startup firms and we love being part of the atmosphere of optimism and ingenuity, peppered with a bit of youthful zeal – something very indie-rock-and-roll about it. But whether they are just starting out or already picking up pace every startup faces the same challenges to scale a business. Recently, we were reminded of this when we watched Inc’s video interview with Birchbox founders, Hayley Barna and Katia Beauchamp. Continue reading Scale Quickly Like Birchbox – Startup Scalability 101
Deploying new code that includes changes to your database schema doesn’t have to be a process fraught with stress and burned fingers. Follow these five tips and enjoy a good nights sleep.
1. Deploy with Roll Forward & Rollback Scripts
When developers check-in code that requires schema changes, that release should also require two scripts to perform database changes. One script will apply those changes, alter tables to add columns, change data types, seed data, clean data, create new tables, views, stored procedures, functions, triggers and so forth. A release should also include a rollback script, which would return tables to their previous state. Continue reading 5 Tips for Better Database Change Management
Agile software development seeks a more lightweight methodology of making changes and releases to software. In the traditional, incremental approach, large pieces of software are written at once, and releases happen less frequently. Once features are complete, the testing phase happens, and then deployment to production. These releases can happen over many weeks in time, so turnaround for new features tends to be slow. Advocates would argue that this forces discipline in the process, and prevents haphazard releases and buggy software.
Agile methodologies, seek to accelerate releases of much smaller pieces of code. These releases can happen daily or even many times a day, as developers themselves are given the levers to push code. Agile tends to be more reactive to business needs, with less planning and requirements gathering up front.
While Agile remains the buzzword of the day, it may not work for every software development project. Web development & applications where small failures can easily be tolerated and where small teams are at work on the effort, make most sense.
Sean Hull asks on Quora – What is Agile software development and why is it important?