Latest blog posts
August 2nd, 2011
A Ruby developer I met recently told me that the majority of us Rubyists skip documentation in favor of Test Driven Development tools. Some business are still pretty waterfall oriented and demand all the requirements gathering, business analysis and design beforehand, as well as hard documentation with lots of funny terms and fancy diagrams.
I told her I was looking forward to studying Cucumber and Rspec in order to improve my skills. She asked me how I did documentation using those tools and I answered: “Cucumber and Rspec are the documentation”. As she twisted her nose I could tell I had to research more on the topic; so I did.
Read the rest of this entry »
July 5th, 2011
Blogrite has been having a steady grow since I announced it; slow but growing still. Single pages finally work and I’m pretty happy with the results. Thanks to Ruben Fonseca for helping me out with this issue I had bugging me for quite some time.
I have reached a milestone. The next thing I need to build is an index page that inevitably fetches all the posts I have. But how am I supposed to do that with files? If I didn’t build Blogrite to allow multiple content providers, I would fix the posts’ location into the filesystem and perform system calls like find or tail or something else. I wouldn’t have to think about an index file that would be built everytime I write something new, in order to increase performance. But since this is not the case, I need to come up with a solution.
What I do know is the responsability of getting the index content is the provider’s.
- If I hosted content live along with the system – like I mentioned above –,
find or tail system calls would be fine.
- If I used Git, I could use a post-commit hook and have it change that post info in an index file.
- Dropbox would be a totally different story. Are there any hooks in the service for automated scripts? (honestly I don’t think there are, feel free to prove me wrong!)
All of this considering an automated index page. There might be another ways of accomplishing this. I’m open to suggestions, throw ‘em away.
June 9th, 2011
I have been working with Utopic Farm‘s jQuery Form Validator for a while, it’s a good plugin. But I have been forced to change it to suit my needs. I thought it would be a great idea to just fork it and release the changes I made previously.
I asked Tolga Arican what the license what kind of license they had for the plugin, they said none. I decided to fork the project and host it on Github, so I could make improvements to the plugin and share them with everyone. Enjoy! Props to the Utopic Farm team for building such a great plugin.
June 8th, 2011
TDD is so much fun. The tests I made allowed me to redo the whole plugin system and understand what I should do instead. I am pleased with with how the direction is being set and I can’t wait to put this up for you guys.
In the video you’ll see I’m having trouble with requesting a good post after a request done wrong. Everytime a request is a bad one, all the following ones are bad as well, I’m not being able to control it. I appreciate the help you can give, thanks a bunch!
May 24th, 2011
I told you before I would post a video on the development of Blogrite after Rubynorte. So here it is.
Topics included
- It works!
- Well, sort of. The first request is a 200, all the other ones throw me a 404 CSS file!
- ERB for rendering the templates.
- Classes over modules for extension?
I appreciate your feedback, you can clone the project at Github.
After fixing the bugs I still have, I intend on fetching the list of posts at the root. Or I can let the final user create an index.txt for a landing page.
Older Entries Newer Entries