サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
衆院選
www.beust.com
I’m happy to announce the release of Kobalt 1.0. Kobalt has been stable for more than a year now but it’s finally reached a point where all the features that I wanted to incorporate in a first release are now present. The most recent one is incremental Kotlin compilation from the Kotlin compiler itself. Kobalt already supports incremental builds at the task level (it can determine if a task needs
There, I said it. I know it’s fashionable to mock PHP for its antiquated syntax and semantic quirks, but I just like it. Here is why. PHP is like CThis is really the main point of this post, and it’s a realization so simple that I’m surprised not more people made it. I have often observed that developers mocking PHP tend to be much more positive when I ask them about C. “C is alright, it’s not OO
TDD leads to an architectural meltdown around iteration three These are the words from software guru Jim Coplien, who penned some of the most influential C++ books in the 90’s. The exact quote is: TDD done strictly from the YAGNI principle leads to an architectural meltdown around iteration three. It’s very refreshing to see the anti-TDD movement gather up some momentum, and I particularly enjoyed
A while ago, I explained why I thought that Duck Typing was dangerous. More recently, Scala popularized a different type of typing called Structural Typing, which is often described as being “type safe Duck Typing”. Let’s take a closer look at Structural Typing and see if it delivers on this promise. With Duck Typing, you send a message to an object in absolute darkness. You don’t know whether thi
These numbers are fairly consistent but since the data sample is relatively low, you are welcome to dismiss them as not representative, but that won’t stop me from elaborating a bit more on the subject… My overall impression is that Ruby on Rails has settled in a niche that is probably not marginal any more but is still a far cry from being any close to mainstream. I’m also betting that this minds
Over the years, I have had the opportunity to work with various code review systems, and I have come to believe that one particular approach works better than the other. Here is what I’ve learned. There are basically three ways to approach code reviews: No code review. Everybody checks in code liberally, and while everyone is welcome to examine change lists as they please, there is no incentive
Update: here is a follow-up to this article, written two years later. You won’t be reading any Ruby on Rails bashing in this blog post for a simple reason: I love Ruby and I love Ruby on Rails. Rails is a fantastic framework built on a wonderful language that appealed to me the very first day I started to study it. I think David did a fantastic job in two areas: Coming up with innovative ideas t
I have a very complex relationship with math. I minored in math but I was really bad at it, and my classmates were regularly running rings around me. My mind was simply not a good fit for it. Then I switched to a computer science major, and everything changed. But even back then, I realized that math was special. It’s so much more painfully obvious to me now, but it took a while to get there. You
このページを最初にブックマークしてみませんか?
『www.beust.com』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く