We'll help you bring your ideas into a demonstrable and clickable reality.
Design and development of your Ruby on Rails application.
Ongoing code maintenance for your Ruby on Rails application.
24/7 dedicated Ruby on Rails Operations as a Service for your Rails application, keeping it online and secure.
View Case Study
"The blueprint that has been developed leaves me with confidence to expand with new features, that will respect many of the lessons learned during wireframing and prototyping with reinteractive."Tim Koopmans - CTO & Founder, Flood IO
View case study
"The difference with reinteractive is the talent pool - Mikel has captured the best talent in the country. The consultants are top resources; self motivated, passionate and upfront."Simon Farrell - CTO, RedBalloon
View case study
“When we cut across to OpsCare and completed the migration, I was extremely pleased and surprised at how smooth it went. The OpsCare model and the work that has gone into building and developing it is technically very impressive.”John Bishop – Director, PetRescue
If you are not completely happy with the result when we are done, we will give you $10,000 worth of our development time, at no charge, to make it right.
We appreciate that a lot of learning comes from experience so we like to give back and share our knowledge with Ruby on Rails Installfest and Development Hub, to help our community grow.Learn more
Development Hub is our monthly free gathering where you can work on whatever Ruby on Rails problem you like. Get help to debug that annoying bit of code or just come and hack, all are welcome!
Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design. It is a non-denominational event and coders from all disciplines are welcome.
reinteractive is an organisation made up of individuals. We take pride in our team. Without them, we are just an empty shell.Meet our awesome team and tell us how we can help
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.
In three years of Installfest, there is one thing that is guaranteed to strike fear in the hearts of our dedicated mentors: a Windows user having difficulty with their install. Well, it did up until now...
I have been lucky in Brisbane to have a wonderful mentor, Freibuis, who travels all the way from the Gold Coast to help out. Not only is he a great mentor, he is a bona fide out-of-the-closet Windows enthusiast with a background in ops! Almost too good to be true. :-)
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.
In April 2013 we hosted our very first Ruby on Rails Installfest in Sydney. Since then it has gone from strength to strength.
For the first two years we held regular Installfests in Sydney and Melbourne. And in 2015 we hosted the first Brisbane event to record numbers. Later that year we included Adelaide in the schedule. Next month we are excited to be hosting our very first Perth event. Installfest is now Australia-wide - woohoo!
Arrayisn't like your typical array: it's an object with keys that are indexes. What this means is that you need to be aware that the length can be more than the number of elements and that there can be "holes".
In day-to-day development you'll probably just build up arrays using the literal syntax, like so: