From ActiveRecord to Diesel - Pat Shaughnessy
Learning something new every day is exercise for your mind. (source: Jeremy Bowcock via Wikimedia Commons) As software developers we’re paid to be professional learners. People hire us (or should hire us) for what we are capable of learning, not for what we already know. To stay in shape and keep up with our peers we need to practice by learning something new every day. We need to get daily exerci
Need a Second Opinion on Your Ruby Code? Ask Crystal - Pat Shaughnessy
Running the Crystal compiler on your Ruby code is like asking a second doctor for their opinion. When it comes to your health, you don’t hesitate to get a second opinion. Doctors don’t always agree, and a second doctor’s appointment is always time well spent when it comes to staying healthy. But what about your code? A code review is similar to going to see a doctor: Someone examines your code, lo
Don’t Let Your Data Out of the Database - Pat Shaughnessy
Don’t let your data escape from your database and cause unintended performance mistakes. Keep your data in the database, not for security reasons but to avoid performance mistakes. Often the best way to speed up your application is to let your database server do what it was designed to do: operate on data. Most modern programming languages and frameworks hide databases behind an elegant, beautiful
Never create Ruby strings longer than 23 characters - Pat Shaughnessy
Looking at things through a microscope sometimes leads to surprising discoveries Obviously this is an utterly preposterous statement: it’s hard to think of a more ridiculous and esoteric coding requirement. I can just imagine all sorts of amusing conversations with designers and business sponsors: “No... the size of this <input> field should be 23... 24 is just too long!” Or: “We need to explain t
Learning from the masters: some of my favorite Rails commits - Pat Shaughnessy
Reading the Rails source code is like looking at the score of a Bach sonata or partita In the last month or two, there have been many great commits to Rails. Last week alone we saw: 0306f82 - implements automatic EXPLAIN logging for slow queries and a382d60 - ActiveRecord::Relation#pluck method. There were also many other useful commits that didn't get so much attention, such as 562583c, 85b64f9,
Besides being faster, what else is new in Bundler 1.1? - Pat Shaughnessy
Besides being faster, what else is new in Bundler 1.1? Three weeks ago I explained why Bundler 1.1 will be much faster than Bundler 1.0, which is clearly its most important new feature. However, there are a few new commands and options the Bundler team implemented in version 1.1 that can help you better manage and sort through the gems you have installed on your development computer and servers. B
Why Bundler 1.1 will be much faster - Pat Shaughnessy
If you’ve worked on a Rails 3 application during the past year or so you’ve probably noticed that running bundle install or bundle update can often take a long, long time to finish. The terminal seems to hang for 30 seconds or more after displaying “Fetching source index for http://rubygems.org/.” Well I have some good news for you: the smart people behind Bundler and RubyGems.org have come up wit
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
