Sometime in the last 40 years, object-oriented programming got lost. Instead of producing code that can be understood by reading, it produces code that can be explored…
![Trygve Reenskaug - DCI: Re-thinking the foundations of object orientation and of programming on Vimeo](https://cdn-ak-scissors.b.st-hatena.com/image/square/d4dee3503ed01479eb21423eb248f537e4608990/height=288;version=1;width=512/https%3A%2F%2Fi.vimeocdn.com%2Ffilter%2Foverlay%3Fsrc0%3Dhttps%253A%252F%252Fi.vimeocdn.com%252Fvideo%252F524734557-00a9dee8d2107623defe98f871b7feca1d9b46fe250687a20f7bff88fe0ed636-d_1280x720%26src1%3Dhttps%253A%252F%252Ff.vimeocdn.com%252Fimages_v6%252Fshare%252Fplay_icon_overlay.png)
Sometime in the last 40 years, object-oriented programming got lost. Instead of producing code that can be understood by reading, it produces code that can be explored…
パターンに機能と型を取り戻す アジャイルにおいてアーキテクチャを表現する DCI James O. Coplien (著) 和智 右桂 Growth xPartners Inc. (翻訳) Copyright c 2010 Gertrud & Cope. All rights reserved. はじめに 本稿は James O. Coplien 氏の論文「Restoring Function and Form to Patterns」(http: //www.software-architect.co.uk/slides/sa10-JimCoplien Patterns.pdf)の全文を、氏 の許可を得て翻訳したものです。 要約 15 年以上前、我々はソフトウェア・パターンの規範のための基盤を築いた。—この規範は後に長 いこと、ソフトウェア・アーキテクチャにとっての中心になったものであ
“I always get so frustrated trying to dig through a project new or old, and trying to trace the flow of execution and how things fit together...” You can't afford complicated code. Writing small and easily testable methods can certainly clean things up, but as your application grows your classes start to know too much. Large classes means a large cognitive overhead for understanding how things wor
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く