■_
・カレチ
今週のモーニングにはカレチが掲載。今回みたいな話は好き。
・買った
権藤さんが監督ではやってられないって、
森さんを呼んでからおかしくなったんだよなあ。
いや、森さん自身は悪くはないのだけど
(といいつつ、ノムさんと一緒で自分は好きな監督ではない)。
今見返してみると、初期の絵って以下略だったんだなあ。
2011年02月06日
■_
心の野球
何ヶ月か前に図書館で予約してたのですが待ちが多く、
ようやっと順番が回ってきました。
さくっと読み終わっちゃったのですが、
これは買ってから感想を書かねばなるまいと判断しましたのであとで書きます :)
でもアサマシははっておくw
■_ これ
鬼車では警告してくれたような。オプションだけど。
正規表現 Part7 [chaika] 807 デフォルトの名無しさん [sage] 2011/02/06(日) 17:49:31 ID: Be: (.+)+ これってどういう意味を表している？ 808 デフォルトの名無しさん [sage] 2011/02/06(日) 17:55:28 ID: Be: (任意の文字の1文字以上の繰り返し)の繰り返しなので すももももももももものうち の場合 (す)(ももももももももも)(の)(う)(ち) とヒットするに違いない 809 デフォルトの名無しさん [sage] 2011/02/06(日) 18:01:40 ID: Be: >>807 captureに全部食われるんじゃない 実質 (.+) と同じ。つまり空でない文字列 810 デフォルトの名無しさん [sage] 2011/02/06(日) 18:21:07 ID: Be: >>808-809 そうなのか・・・ 梟本で"=XX==========="に対して 'X(.+)+X'って正規表現を使ってたんだけど イマイチ理解できなくて 811 デフォルトの名無しさん [sage] 2011/02/06(日) 18:25:21 ID: Be: >>810 何版の何ページ？小見出しも教えてくれると助かる 812 デフォルトの名無しさん [sage] 2011/02/06(日) 18:25:39 ID: Be: >>810 何ページくらい？ 813 デフォルトの名無しさん [sage] 2011/02/06(日) 18:30:08 ID: Be: >>811-812 第３版の第４章、4.1.5.2、p142-143 正規表現エンジンの判別による説明の件 814 デフォルトの名無しさん [sage] 2011/02/06(日) 18:30:36 ID: Be: かぶってしまった 815 デフォルトの名無しさん [sage] 2011/02/06(日) 18:37:04 ID: Be: 今emacsでX\(.+\)+Xを試したけど =XX=========== マッチしない =XhhhooogggeeeX=========== hhhooogggeee にマッチ =XすもももももももものうちX=========== すもももももももものうち にマッチ 816 815 [sage] 2011/02/06(日) 19:03:06 ID: Be: amazonのなかみ検索で該当のページをみたけど、 その正規表現はマッチさせるのが目的じゃなくて、 NFAだと時間がめちゃかかるよっていうことが伝えたい内容だね だからわざとマッチさせずに バックトラックするような例を選んであるのだと 817 デフォルトの名無しさん [sage] 2011/02/06(日) 19:25:59 ID: Be: >>810 なんとなくわかるレベルの漏れが言うのもなんだけど 4章全部読んで足りなければ オートマトンの載ってる教科書も読んだ方がいいと思うよ フクロウ本はDFA/NFAの話をしてるのに図を載せてないのがネック 818 デフォルトの名無しさん [sage] 2011/02/06(日) 19:30:40 ID: Be: あれ一発でDFA/NFAが理解できたとか言ってるやつは、はったりだよなあ。
最終的にマッチした結果は同じだとしても、そこにいたるまでの道のりが違うというか。 あ、いや、(.+)+ だけでは意味がない(変わらない)か。
■_ Scala の新機能(予定)
らしい。
Clever Title: Scala's upcoming dynamic capabilities Thursday, February 03, 2011 Scala's upcoming dynamic capabilities I was surprised to see the Scala team check in a new "Dynamic" trait into Scala trunk recently. Once this trait is mixed in to your class, any unresolved method calls are passed to an invokeDynamic() method, much like Ruby's method_missing. I've been thinking about this a lot, and I see three decent reasons for the inclusion of the Dynamic trait: 1. Integration with dynamic languages on the JVM. 2. DSLs for accessing data where there's already no type safety, ie JSON and XML (written by @jorgeortiz85, I think) 3. DSL for reflection. Reflection libraries are ridiculously verbose, and like JSON/XML/etc libraries, offer little static typing benefits anyway. (略) Using the Dynamic trait is very easy, and really fun. I thought I'd try hooking up Scala to Ruby using Dynamic, JRuby, and the Java Scripting Engine (JSR 223). I was really pleased with how easy it was. Here's some Ruby:def sub(a,b) a - b end def add(a, b) a + b end def method_missing(sym, *args, &block) puts("hey now!") endWith a little setup (installing JRuby to get the "jruby" scripting engine and getting Scala trunk running), I had this simple Scala class: 以下略
Dynamic な trait…?
■_ 問題
もう一つ Scala
Recursion: See Recursion - Scala Meetup in Stockholm Scala Meetup in Stockholm Today at the Scala meetup here in Stockholm a couple of guys had prepared a test for the others attendees. The purpose was to cast some light on some tricky parts in Scala and to make us aware of what, and what not, to do. There was no prestige involved (thank God) and we did not get grades based on our result :-) I thought it would be a good idea to share some of the questions and their answer to you all out there (and also to write it down somewhere to remember myself). Below you can see some of the questions and a short description of their corresponding answers. A suggestion is that you open the Scala REPL in a terminal window and feed it with some code to see how it reacts. I find this a really good and effective way of learning the behavior of the language. All the correct answers and explanations can be found in the end of the blog post. Q1: What classes can call the method area in the code below? class Triangle(height: Double, base: Double) { def area = height * base / 2; } A1.1: the same instance only A1.2: every instance of the same class A1.3: only the class' companion object A1.4: all classes in the same package A1.5: all classes Q2: What classes have access to the field name in the code below? scala> class Person(val name: String, val age: Int) scala> val x = new Person(“Olle”, 36) scala> x.name res0: String = Olle A2.1: the same instance only A2.2: every instance of the same class A2.3: only the class' companion object A2.4: all classes in the same package A2.5: all classes Q3: Since Scala 2.8 it's possible to replace the apply method in the companion object in a neat way, how? scala> case class Person(name: String, age: Int) scala> object Person { | def apply(name: String) = new Person(name, 0); // newborns | } scala> val baby = Person(“TheBaby”) baby: Person = Person(TheBaby, 0) A3: ____________________________________________ Q4: What assertions are true about the code below? scala> val numList = (1 to 1000000).toList scala> numList.head // Snippet A res1: Int = 1 scala> numList.last // Snippet B res2: Int = 1000000 A4.1: Snippet A and B executes equally fast A4.2: Snippet A will execute in constant time where as B executes in linear time A4.3: Snippet A will execute in constant time where as B executes in exponential time Q5: Will the code below return true or false? scala> List(“foo”, “bar”) == List(“foo”, “bar”) A5.1: true A5.2: false Q6: What is the value of x? val x = try { 7 / 0 } catch { case e: ArithmeticException => 1 case e: Exception => 2 } finally { 3 } A6.1: 0 A6.2: 1 A6.3: 2 A6.4: 3 Q7: What will happen when the method add is run in the code below? object Counter { private var c = 0 def inc { c += 1 } } class Object(start: Int) { def add = { inc start + c } } A7.1: The code won't compile A7.2: The value of counter is changed A7.3: The value of counter is unchanged Q8: In Scala there is a concept of a main contructor. What keyword is used to indicate such a constructor? A8.1: super A8.2: this A8.3: nothing A8.4: you don't have to write anything at at THE ANSWERS Hope you enjoyed the questions above. Here are the answers and a short explanation. 以下略
■_
プログラミングのスキルを向上させるもっとも効果的な手段とは?
よく見直したら結構前の質問だな。まあいいやw
language agnostic - What is the single most effective thing you did to improve your programming skills? - Programmers - Stack Exchange Looking back at my career and life as a programmer, there were plenty of different ways I improved my programming skills - reading code, writing code, reading books, listening to podcasts, watching screencasts and more. My question is: What is the most effective thing you have done that improved your programming skills? What would you recommend to others that want to improve? I do expect varied answers here and no single "one size fits all" answer - I would like to know what worked for different people. Edit: Wow - what great answers! Keep 'em coming people!!!In no specific order... * learning other frameworks/languages, and seeing how they do things, and compare that to stuff that I already know * reading about patterns, best practices, and then examining my old stuff and applying those patterns where necessary * pair programming * working with people far smarter than myself * Always listening to what others have to say, regardless if they're junior, intermediate, senior or guru. job title doesn't mean anything. * Disagreeing with everything Joel says. ;)Deciding TO be a 'Jack-of-all-Trades' Fairly early in my career, I was an expert with a particular database and programming language. Unfortunately, that particular database lost the 'database wars', and I discovered that my career options were ... limited. After that I consciously decided that I would never let myself become boxed in like that again. So I studied everything I could get my hands on: Windows, Unix, C, C++, Java, C#, Perl, Python, Access, SQL Server, Oracle, Informix, MySQL, etc. Whatever tools and technologies are new or unusual, I became the 'go-to-guy' -- "Ask Craig, if he doesn't know it, he'll learn it." As a result I've worked on all sorts of projects, from embedded systems for environmental telemetry to command and control systems for missile defense. The only problem I've ever had is with companies that insist on pidgeon-holing me into a specialty, when my specialty is being a generalist. [EDIT: Also known as a Polymath or Renaissance Man or multi-specialist.] Something to keep in mind ... what's the half-life of knowledge in high tech? It tracks with Moore's Law: half of everything you know will be obsolete in 18-24 months. An expert who chooses the wrong discipline can easily be undermined by the press of technology; a generalist only has to add some more skills and remember the lessons of the past in applying those skills.Two things: 1. Read code written by different people. 2. Write documentation for code written by other people. Writing code is extremely easy; every other person I know can do that. But reading someone else's code and figuring out what it does was a whole new world to me.Read * books, not just websites * for self-improvement, not just for the latest project * about improving your trade, not just about the latest technology * read code, not just you are working on. Just develop the appetite for reading.I think the most important thing you can do is make a conscious effort to improve. There's no single silver bullet, you have to keep looking for new sources of information, new experiences, and more practice. And the second most important thing, think about what you're doing, why you're doing it, and how you can do it better. Same thing with previous projects. Look back at what you've done, and how you might do it differently now. Think about what could have been done better, or where you could still improve on it. I see two great examples of this at work every day. I have one coworker who loves to learn, and wants to be the best developer he can. He's uses any downtime to read blogs, read books, discuss programming techniques, and ask tons of questions. He's also very noticeably improved in just the past year. Another coworker does his job, and does it fairly well. But that's all he does. He sticks with what he knows, doesn't make much effort to improve, doesn't work on any projects outside of his existing ones, and after 4 years, he has the exact same skill set and programming ability that he had when I met him.
さっきの桑田の本にはこれの回答になるようなことも書かれていたなあ(と意味ありげなふり)
ところで reddit で取り上げられてたのでこれをしったのですが、 What is the single most effective thing you did to improve your programming skills? : programming
コメントに面白いものが。
What is the single most effective thing you did to improve your programming skills? : programming 127.0.0.1 reddit.com 127.0.0.1 youtube.com 127.0.0.1 redtube.com
三つ目がわからんけど。
■_
- adieu_ptr_vector
- Togetter - 「一山いくらで人月見積の大手ベンダーを外し始めたユーザー企業のITガバナンス」
- cofoja - Project Hosting on Google Code
- ドメサカ板まとめブログ:広島スレでお好み焼きのオススメ店を聞いてはいけないらしい
- 二つ返事とは - Weblio辞書
- キュゥべえ先生から学ぶ交渉術（魔法少女まどか☆マギカ - ほわいそーしりあす？（旧「書店員の異常な愛情」）
- Java(TM) 6 Updateが複数あるが・・ | OKWave
- OSを勉強するには・・・。 高校２年男子です。 情報系の勉強をしたいと思ってるん... - Yahoo!知恵袋
- itemanblr., 1 名前：以下、名無しにかわりましてVIPがお送りします：2011/02/04(金)...
- 企業向けに500万のアプリを作るより、大衆向けに1000円で配布したほうが儲かる気が... - Yahoo!知恵袋
-
Clang results | Rafael Espindola's Blog
With this it is now possible to run some interesting benchmarks of Apple's current gcc (4.2) versus clang builds.
- Eli Bendersky's website » Blog Archive » Where the top of the stack is on x86
- ソフトウエアジャパン２０１１の講演からの感想: 組み込み技術者の単身赴任日記
- アナログモデム技術は死なず：白物家電の遠隔故障診断での応用: 組み込み技術者の単身赴任日記
- pricing - Why do programmers write applications and then make them free? - Programmers - Stack Exchange
- プログラマーって景気が関係ないですよね？Web関連だと寧ろ不景気が強味だし、かと... - Yahoo!知恵袋
- An Infinite Number of Cats on Keyboards: MAG-85: 8085 Microprocessor Project Software Progress
- 東京メトロと都営地下鉄、一元化の障壁は？｜日経BP社 ケンプラッツ
- career development - I'm graduating with a Computer Science degree but I don't feel like I know how to program. - Programmers - Stack Exchange
![GA 芸術科アートデザインクラス OVA(初回限定版) [DVD]](http://ecx.images-amazon.com/images/I/51GWbeuiZPL._SL160_.jpg)
