サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
体力トレーニング
reinteractive.com
A few days ago a prospective client asked “Why do you use Ruby on Rails?” and I told them a simple answer. Profitability and Productivity. There is nothing else out there that can develop the majority of business web based software as cost effectively as Ruby on Rails. This might be an unpopular position in an IT world that releases a new and shiny tool every other day, but I don’t care. What I ca
During the [previous post] I looked at what feature flags are and why you’d want to use them. In this post I will explore how I’ve implemented them in the current web-application I’m working on. It’s a very simple process which means there are no excuses not to use a feature flag in your application. everything is easier on Rails The [Rollout] gem I use the [Rollout] gem as a way of implementing F
eNearly a month ago the Rails 4.2 beta1 was released. It contains a host of interesting changes but some are definitely more exciting than others. I’ve scoured through the change notes to bring you some of the more interesting tidbits that are changing, along with a small amount of commentary. This is based off a talk I gave at the Sydney Ruby meetup in September. Let’s dive in. AdequateRecord Mer
I figured I would take some time to write about a nifty feature that I’m not sure many developers know about, or have had an opportunity to use yet: the reversible method in Active Record migrations. Introduced in Rails 4.0, reversible makes it possible to tell a migration using change (instead of up and down) how to reverse migrations that Active Record doesn’t know how to reverse by default, so
Rails 4.1 was released on April 8th and subsequently Lucas Mazza from plataformatec blogged about 3 favourite features in Rails 4.1. I liked the idea, but some of my favourite things are different. Without further ado, here’s my favourite things about Rails 4.1. No more rake db:test:prepare One common busy-task which occupies Rails developers during development is keeping the test database migrate
In the Ops Team, we love Ansible. If you’re not familiar with Ansible, it is a tool to automate, document and systematise server provisioning a.k.a Infrastructure as Code. At the basic level, one can write simple tasks in yaml files and Ansible will run them sequentially via SSH. When you offer Operations as a Service like we do, Infrastructure as Code is one of the keys to a happy life. Here are
Face it, you are a top developer, one of the best at your game, you eat lambda’s for breakfast, refactor whole apps as an afternoon snack and bad code just trembles when you approach. You are at the top of your game and nothing stands in between you and the code you desire. Yet, the Rails asset pipeline still trips you up, not once, not twice, but just about every time you try and use it. Here’s a
Enumerator::Lazy Recently, I have had to analyse a very large CSV file and look for some lines containing specific values. In this post, I will explain how the lazy enumerator let me write simpler code. Enumerator::Lazy is still relatively new to many Rubyists including myself, but in short, the lazy enumerator lets us evaluate its elements as needed. This behaviour is quite different from the reg
このページを最初にブックマークしてみませんか?
『reinteractive - top Ruby on Rails web and mobile development』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く