Tuesday, February 09, 2016

Beyond React: Introducing Cycle.js

I'm giving a talk at the Montreal JS group tonight.

Title: Beyond React: Introducing Cycle.js

"Cycle.js is a reactive RxJS/Virtual DOM based front-end library. Andy will provide a quick introduction to Cycle.js basics and philosophies, go through a tutorial of its concepts and demonstrate with some code examples."


View Slides Online

Sunday, January 31, 2016

Ultra Light Wizard v0.0.6

Now includes basic Rails scaffolding with attributes as part of the work.


rails generate ultra_light_wizard:wizard Project steps:basic_info,project_detail,file_uploads,preview attributes:name:string,description:text,start_date:date,delivery_date:date step_alias:part


More on the way, I promise!

Friday, January 29, 2016

Ultra Light Wizard v0.0.5

We're getting near 0.1.0, but not quite there yet at 0.0.5:

Still, the gem has become much more useful at this point with form scaffolding and advanced navigation helpers implemented.

A few more things need to happen before we hit 0.1.0, and then automated tests need to be added before hitting 1.0.0

Stay tuned!

Wednesday, January 27, 2016

Ultra Light Wizard v0.0.2

Ultra Light Wizard v0.0.2 is OUT... with view navigation support (Previous/Next) and Rails helper generation.

Also, fixed issues with wizard step controller.


Enjoy testing and reporting feedback!

Tuesday, January 26, 2016

Ultra Light Wizard v0.0.1

Ultra Light & Maintainable Rails Wizard was a solution pattern I came up with 3 years ago to facilitate creating Rails multi-step forms that adhere to REST, OO, MVC, and other software best practices.

The original blog post about it is over here:

And the RailsConf 2014 talk I gave about it in Chicago is here:

From talking to developers at our local Montreal.rb user group and interacting with different client developers, it seems that the pattern has caught on and is being put to good use, sometimes with the aid of the Rubygem Wicked.

Of course, given that the Ultra Light & Maintainable Rails Wizard approach simplifies development and maintenance of wizards immensely, it is not necessary for the many smart and responsible developers out there to have a library. After all, following the approach is supposed to yield a lighter-weight solution than using most libraries out there. Nevertheless, if it is possible to codify the pattern in a library that is light-weight enough and simple to use, then we may as well have one...

And two years after announcing the idea at RailsConf 2014 (and a few hours of work).... I finally have something to show!

Ultra Light Wizard v0.0.1: https://rubygems.org/gems/ultra_light_wizard/versions/0.0.1

GitHub: https://github.com/AndyObtiva/ultra_light_wizard

Please install and use on your projects.

Stay tuned for more developments and enhancements and feel free to suggest ideas via comments.

Tuesday, October 13, 2015

CodeMentor Experts Reveal The Secrets To Staying Motivated

I've been featured in an article on CodeMentor.io, so thought I'd share:

CodeMentor Article: Experts Reveal The Secrets To Staying Motivated

Build a personal low-risk project that tackles a new idea or puts a new twist on an old idea” – Andy Maleh

“Get training or regular mentoring by an expert in the language of choice or technology you aspire to master” – Andy Maleh

If you ever feel like solving a programming problem on a side project with the help of a mentor, expert, or pair-programming partner, hit me up at CodeMentor.io:


Monday, April 13, 2015

Presenting Abstract Feature Branch at Montreal.rb April 2015

I am giving a talk at this month's Montreal.rb user group, taking place next week on April 21, 2015:


How many times do you find yourself near the software release finish line on an exciting new feature only to be pulled off by management in the last minute to sneak in some higher priority emergency fix? What do you do with the unfinished feature's code if parts of it were already functional and merged into master? Do you pluck it out and move to a remote feature branch? Do you simply comment out the code not ready for exposure to the customer? What about some of the nice software design improvements that were done as part of the feature and are being put to good use by the team today? Do you also put design improvements off till the feature is deemed by management high priority again?

These questions typically get decided on by the team on a case by case basis, and often with big compromises affecting both project delivery and code quality.

While consulting for Sears in 2009 and working at Groupon.com in 2012, I happened to work in teams that adopted a very effective and inexpensive solution to the problem called "Branch by Abstraction", a technique originally popularized by Martin Fowler, author of UML Distilled and Patterns of Enterprise Application Architecture.

In this talk, I aim to explain Branch by Abstraction and demonstrate how to apply in Ruby using a gem I wrote called Abstract Feature Branch, partly inspired by the internal team libraries used at Sears and Groupon. The gem has already had over 50,000 downloads from rubygem.org and has been utilized in several of my newer projects, including launch of EarlyShares.com and enhancements of Factor75.com.

Attendees should walk out with basic understanding of Branch by Abstraction and enough knowledge of Abstract Feature Branch to be able to explore further in their own projects after the talk.