Software has been around for more than fifty years and there have been a lot of learnings generated in how to best manage the process of building software. Before the internet it was quite common for a large software project to be initiated, worked on and completed without more than a handful of people knowing what was going on. This lack of transparency led to many dissatisfied stakeholders and sometimes even the software being taken to the trash upon delivery. How do modern software practices avoid the pitfalls of black box software development?
At reinteractive we use Pivotal Tracker to get all of the features translated into User Stories that are clear for the developer to implement. Once a User Story is completed by the developer the User Story must be accepted by the Product Owner. The Product Owner is the person who decides what the features should and should not do and has ultimate authority. If the Product Owner rejects the developers work Pivotal Tracker will notify the developer that the User Story is reopened and the developer will then attack the User Story again. It is very important for the User Stories to be accepted or rejected quickly because a developer will only hold a complete understanding of the code for a short amount of time.
We've come a long way with web development technologies. To the point where developing on a virtual machine is now a realistic option as the performance issues that once plagued VMs have all but been eradicated. As the sole VM management tool, Vagrant utilises several virtualisation tools VirtualBox, VMware, etc.) and provides a whole host of benefits. It makes your development environment as close as production as possible and it takes away the excuse of "It works on my computer". If you need to work on different projects, you will appreciate not having your machine messed up by different setups. Here I will show you a simple example of spinning up a Rails project using Vagrant.
Caveat: In the guide we refer to a
Host Machineas your local environment. A
Guest Machineis the virtual machine environment.
So, you have the opportunity to work on a Ruby on Rails app.
Perhaps you are a potential new company employee, a freelancer, or even a consulting company. Regardless, you will probably want to get an idea as to "how well" new development on this app is potentially going to go before you fire up your editors and start coding.
As developers working on a project, we often deal with integrating third party APIs, data storage, and business tools that are outside the scope of our applications. Salesforce provides a powerful business tool which is, more often than not, used by teams outside the development team.
One task we were recently presented with was to "Create a Rails application around a Salesforce workflow".
We have some very exciting news to kick off your weekend! We are very proud to announce that the app we built for businest® was selected as the overall winner for 'The Small Business App You SHOULD Be Using' in the Accountex Meridian Awards!
Each year more than 150 new apps are added to the small business, cloud accounting ecosystem. The Meridian Awards, created by Accountex, are presented to a prestigious few apps in the accounting technology space who have displayed excellence beyond their peers in a given award category.
A Top MBA Graduate's Experience with Software Development.
I’ve been with reinteractive now for just over 6 months and it has been both an exciting experience and quite a learning curve.
Saturday the 22nd of October was Global Day of Code Retreat. This year, reinteractive brought Code Retreat to Adelaide.
Code Retreat is an all-day intensive coding practice, focusing on the fundamentals of software development and design. It is a non-denominational event and coders from all disciplines and all experience levels are welcome.
✏️ This blog post uses ionic 2.0.0-rc.o
In my previous article, I gave a basic overview about ionic2 and its features. Now it is time to go beyond that and build something that actually works.
Ruby on Rails came out about 10 years ago as the "first" MVC (Model View Controller) architecture, database out of the box web framework. MVC architecture meant that any Ruby on Rails developer would know what a custom application was doing because they knew where to look. Having a database out of the box allowed lots of developers to get an application up and running fast because they didn't have to work through the barriers of setting up a database connection. Before Rails, the option was 'spaghetti' PHP applications which had in turn killed off most of the Perl applications that started the internet revolution.
The hands down best thing to do before building your next software project is to invest in a set of rapid prototypes. What do I mean by a prototype? Here's an example: http://ux.reinteractive.net/C3F2ZS/#p=introduction
For those of you who are too scared to click on the link I salute you for your security paranoia and offer the following description: A prototype is an interactive, clickable schematic structure of your final product and represents the experience the users will have with your application.