Transforming Code into Beautiful, Idiomatic PythonRaymond Hettinger Learn to take better advantage of Python's best features and improve existing code through a series of code transformations, "When you see this, do that instead."
Refactoring Legacy Rails Controllers
Ruby on Rails controllers are like the bouncers of a nightclub. No identification at a club? You aren’t getting in. Without the proper clothes, you can expect to be turned away. Oh, you wanna say something slick? You’re definitely not getting in, and you might be getting a beatdown on your way out. Controllers are the bouncers of the Rails software stack. You aren’t logged in? See ya. You aren't a
Better Javaの一歩先へ！ Scalaリファクタリング入門 (2016/12/02 19:30〜)
イベント説明 Javaの豊富な資産を活かしながら、スクリプト言語のように簡潔に、表現力豊かなコードが書けるScala。 いわゆる「Better Java」として手続き型スタイルで利用されている方も多いかもしれません。 この勉強会では、Better Javaなコードをより堅牢なScalaらしさを活かしたコードへと改善するテクニックを、架空のアプリケーションをサンプルに解説していきます。 イベント内容 第一部 「大改造！静的ビフォー・アフター」田所 駿佑 なぜBetter Javaの先なのか？ パターンマッチのパターン タプルを避ける Scalaな例外処理 case classに制約を持たせる sealed traitで網羅性を担保する 第二部 「ScalazでウェブアプリがCHA-LA HEAD-CHA-LA」岩松 竜也 無印時代の仲間たち(Option, Seq, Future, Eith
7 Design Patterns to Refactor MVC Components in Rails — SitePoint
In our previous post, The Basics of MVC in Rails, we discussed theoretical aspects of the MVC design pattern. We defined what MVC stands for, identified what each MVC component is responsible for, addressed what happens when a component contains redundant logic, and, most importantly, we introduced the concept of refactoring. In this article, as promised, we’ll show you each design pattern at work
Ozcode (オズコード) C# のデバッグ環境を格段に向上させる Visual Studio 拡張機能 : エクセルソフト
平素より、OzCode 社製品をご利用いただきまして、誠に有難うございます。 弊社では 2015年 9月より OzCode 製品の販売代理店を務めてまいりましたが、OzCode 社の意向により、2021年 11月 30日を以って、販売代理店を終了しました。 今後の窓口に関しては、OzCode 社が窓口となります。 ライセンスの購入/更新の窓口: sales@oz-code.com テクニカル サポート: support@oz-code.com ※ どちらも英語でお問い合わせください。 本件に関して、ご不明な点がございましたら弊社お問い合わせフォームまでご連絡ください。 よろしくお願いいたします。 今後とも、弊社取り扱い製品をよろしくお願いいたします。 エクセルソフト株式会社
RubyKaigi 2016, September 8..10, Kyoto, Japan #rubykaigi
Chris is a Ruby developer at Red Hat on the ManageIQ core team. He enjoys working full time on open source software to manage The Cloud™ and has contributed to various projects in the Ruby ecosystem. Chris hails from Minnesota in the United States and also enjoys hockey, hiking, and tasty beers. Good news! Ruby is a successful and mature programming language with a wealth of libraries and legacy a
RubyKaigi 2016, September 8..10, Kyoto, Japan #rubykaigi
Nobody knows bad code like Justin Searls—he writes bad code effortlessly. And it's given him the chance to study why the industry has gotten so good at making bad software. He co-founded Test Double, an agency focused on fixing what's broken in software. Until recently, we didn't talk much about "legacy Ruby". But today, so many companies rely on Ruby that legacy code is inevitable. When code is h
Journey of a Trailblazer (1)
A road to refactoring August 21, 2016 in code • 26 min read I decided to refactor one of my Rails side projects with the Trailblazer architecture. Why? The short version is, I’m looking for some standards and conventions to refactor my day job’s Rails API application. After reading a bit about Trailblazer and what it offers, I decided to try it on one of my side projects. I would refactor it to le
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Medium – Get smarter about what matters to you.
Methods Can Be Longer Than Five Lines
Code coverage done right.
DirtyInformation - Two Duplication Refactorings in Elixir
Refactoring Ruby: DRY up your domain models using a struct table – RubyTapas
The typical Ruby bugs with changing the last line in a method
GitHub - rbspy/rbspy: Sampling CPU profiler for Ruby
GitHub - joshuaclayton/unused: Deprecated; see https://github.com/unused-code/unused
GitHub - tcopeland/olde_code_finder: Ye olde code finder
GitHub - seattlerb/debride: Analyze code for potentially uncalled / dead methods, now with auto-removal.
GitHub - testdouble/suture: 🏥 A Ruby gem that helps you refactor your legacy code
The Pros and Cons of Ruby Refinements