Latest Articles on 2013 by Our Team

It might sound trite, but the importance of communication in the success of a software project cannot be overemphasised. If given the choice between over communicating and under communicating, I'll choose going overboard every time.

There are many tools and processes to help communication levels remain high, both within the project team and with clients. This post I will talk about three of the most important:

Before I was thrown into the Ruby and Rails Community through my work at reInteractive, I had no previous development experience. So, you may be thinking, who am I to tell you that you should choose to learn Ruby, and how can I give you technical advice on picking one programming language over another another? I’ll tell you:

In most cases, you really could pick any language and build something you want with it. So, again why choose to learn Ruby? Not all programming languages were created equally, so while the chances are that you can build your application with any of them, each was created with a different purpose. The sole purpose for the creation of Ruby was for developer happiness, to create a language where people love doing what they do, writing code!

Since I started working at reInteractive earlier this year, I’ve gone from having absolutely no development experience at all, to now having a pretty good understanding of how it all works. I’ve got a long way to go before I can call myself a developer, but being surrounded by Rails devs and running events to get new developers started has helped me understand a lot! I’ve realised that learning to code can be difficult, but there are certain habits we can pick up to help us along our journey.

So, have you started learning Rails too? Let me guess, you either breezed through the first lesson, and then either skipped the next lot because these weren't “things that you needed to know” or you hit a steep learning curve and called it quits. Did you really do enough?

Recently we talked about how important communication is in the life of a project. In software engineering, a big part of the communication is delivered through documentation. And on the field, nothing beats a good README.

So.