Hi all. It was a long time ago when I announced I Rock app development and here we are.
This first episode is quite boring like all first set up episodes:
- Install ruby, rails and postgresql
- Create rails project
- Set up rspec, capybara and guard
- Write our first test and make it pass
- Deploy application to heroku
In the next episode we’ll get to developing first feature of the application.
What is that project we’re gonna develop? First I though about Gamefinder but my plans have been changed and I decided to create another application which can be used by everyone, not only gamers.
The basic idea is Achievements Journal.
Every time you achieve something of importance it’s better be jotted down somewhere.
There are a lot of services and applications which allow you to boast about your goal (they call it making commitment), share this new dream with friends, receive a lot of encouragements and… ditch it. Well, most of the time anyway.
I do not believe in power of public commitment. From my experience I personally almost never achieve goal which I publicly told about. Here is a great short TED talk Keep your goals to yourself which I agree with on 100%.
So hence the application purpose: create a space where you can boast about your achievements and receive hard earned recognition.
You can go to public open trello board (https://trello.com/b/DcxL5Z6O/i-rock-app) to have a look on features of this application and it’s overall progress.
But basically application I Rock allows user to create and manage his achievements, organize them in lists, share them and receive encouragements from other users, find people who inspire him/her by their achievements and follow them and encourage them in return.
Very simple and it’s perfect for Rails learning. So get ready for this journey, we’re ready to start.
To stay informed about project progress or even better to participate: subscribe to my blog and follow me on twitter.
In this post I want to share with you information about the project I’m working on now for this blog and which I plan to launch on the mid-October.
The basic idea is to create live and real project which can serve in educational purposes as well. The problem with screencasts and courses I do now is that they use artificial example applications which are never really deployed to production and used by real users. But skill is gained mostly when one work with real project and solves real problems.
So I thought why not to create a real app and document the process of its development with all errors, bad and good decisions, etc. on the way?
Hi and welcome! Here is my another try to blog constantly, but this time I’m very excited because now I have a plan! In a week or so I’ll share it with you so stay tuned.
This post is about my struggling with screencasting workflow lately. So I decided to use two different approaches to record one very short screencast (less than 2 minutes in length, this is an excerpt from my upcoming Tuts+ course Design Patterns in Ruby).
So I really would like to get your opinion on which one of these two you consider better and why. And maybe you could share some thoughts on other issues which could be improved by me in my future screencasting ventures.