あとでかく
いやちょっと持ち帰り残業じゃないし直接業務に関係している訳じゃないけど
内容が興味深い論文を読んでたりしていてですね以下略
Learn C, Then Learn Computer Science : programming
Learn C, Then Learn Computer Science | Hacker News
Learn C, Then Learn Computer Science | qrohlf.com
HN、reddit 両方で盛り上がってたので見てみると
Learn C, Then Learn Computer Science | qrohlf.com
Learn C, Then Learn Computer Science
Theoretical understanding is great, but fundamentals are just as important.
I’m an undergraduate studying computer science. It’s great to get to sink my teeth into interesting,
high-level problems like machine learning algorithms and graph theory, but I feel like my formal CS education
isn’t touching on some of the fundamentals of how computers work and how to write good code.
In his post “Learning to Code vs. Learning Computer Science”, Terence Eden raises some excellent points about
the importance of learning the algorithms and intellectual principles behind programming. However, while I
agree that “no conversation about teaching coding in schools is complete without a theoretical understanding
of the science behind the code”, I also think that it’s important to talk about students' understanding of
the mechanics behind the code.
(略)
This is the problem with emphasizing computer science over learning to code. Without an understanding of what’s
happening at a low level, my peers ran into issues like C segfaults and Java NPEs and had no idea what to do to
debug them. This is a problem that stems from teaching people computer science but not teaching them how to code.
Learning to code isn’t just teaching people how to spell - it’s teaching people the meaning behind the words.
That’s why I think “learning to code” is just as important as computer science to teach - and teach well - at
an undergraduate level.
09 Feb 2014
Copyright © 2014 Quinn Rohlf.
Java NPEs って「ガッ」されるあれかw
この Millって最近ちょくちょく名前を見かけるんで
ちょっと気になってたんですが
Topic: Introduction to the Mill CPU Programming Model | Out-of-the-Box Computing
Topic: Introduction to the Mill CPU Programming Model | Out-of-the-Box Computing
Introduction to the Mill CPU Programming Model
The Mill is a new CPU architecture designed for very high single-thread performance within a very small power
envelope.
The Mill has a 10x single-thread power/performance gain over conventional out-of-order (OoO) superscalar
architectures, yet runs the same programs without rewrite.
The Mill is an extremely-wide-issue, statically scheduled design with exposed pipeline. High-end Mills can
decode, issue, and execute over thirty MIMD operations per cycle, each cycle.
The Mill architecture is able to pipeline and vectorise almost all loops, including while loops and loops
containing calls and flow control.
The pipeline is very short, with a mispredict penalty of just five cycles.
Processor Models
The Mill is a family of processor models. Models differ in various parameters that specify their performance
and power constraints, such as the width of their vector units, the functional units, number of pipelines and
belt length.
All Mills can run the same code, however. Code is compiled to an intermediate representation for distribution,
and specialisation for a particular Mill processor model is done by a specialising compiler at software
installation time or on-demand as needed.
へー面白そう
＞designed for very high single-thread performance within a very small power envelope
九州方面の某氏はこれも追いかけているんだろうか
Absolutely No Machete Juggling ≫ Top 10 Career-Changing Programming Books
こういうのをちょこっと訳して
翻訳本のアフィリエイトをこれでもかって貼り付ける類の人っていますよね。
あ、オレか。
Absolutely No Machete Juggling » Top 10 Career-Changing Programming Books
When I graduated with a Computer Science degree ten years ago, I was excited to dive into the world of
professional programming. I had done well in school, and I thought I was completely ready to be employed doing
my dream job: writing code. What I discovered in my very first interview, however, was that I was massively
underprepared to be an actual professional programmer. I knew all about data structures and algorithms, but
nothing about how actual professional, “enterprise” software was written. I was lucky to find a job at a
place willing to take a chance on me, and proceeded to learn as much as I could as quickly as I could to make
up for my deficiencies. This involved reading a LOT of books.
Here I reflect on my 10-year experience programming professionally and all of the books I’ve read in that time,
and offer up the ten that had the most profound impact on my career. Note that these are not the “10 best”
programming books. I do feel all of these books are very good, but that’s not the only reason I’m selecting
them here; I’m mentioning them because I felt that I was a profoundly different person after reading each than
I was beforehand. Each of these books forced me to think differently about my profession, and I believe they
helped mold me into the programmer I am today.
None of these books are language books. I may feel like learning to program in, say, Scala, had a profound
impact on how I work professionally, but the enlightening thing was Scala itself, not the book I used to help
me learn it. Similarly, I’d say that learning to use Git had a significant impact on how I view version control,
but it was Git that had the impact on me, not the book that I used to teach myself the tool. The books on this
list are about the the content they dumped into my brain, not just a particular technology they taught me, even
if a technology had a profound impact on me.
So, without further ado…
プログラミング言語の本や、ツールの使い方のような本は除外していると。
で、十冊は以下の通り。詳しい理由などは元記事へ。
-
The Pragmatic Programmer
-
Continuous Delivery
-
Clean Code / The Clean Coder
-
Release It!
-
Head First Design Patterns / Patterns of Enterprise Application Architecture
-
Working Effectively with Legacy Code
-
Refactoring and xUnit Test Patterns
-
The Passionate Programmer / Land the Tech Job You Love
-
Apprenticeship Patterns
-
The Art of Agile Development
挙げられている本で日本語訳が出てないのはこれかな?
Amazon.co.jp： Land the Tech Job You Love (Pragmatic Life): Andy Lester: 洋書
(アフィリエイトつきでないリンク)
それとは別に、日本語訳が「あった」けど今は絶版状態になっちゃってるのもありますね。
Top 10に加えて挙げられているもの
Absolutely No Machete Juggling » Top 10 Career-Changing Programming Books
Honorable Mentions
There are a number of books that I didn’t include in the above list, but that nonetheless had a large impact
on my career. This, of course, despite the fact that I completely cheated in my Top 10 and included more than
ten books.
-
Presentation Patterns
-
Pragmatic Thinking and Learning
-
Effective Java
-
Domain-Driven Design
二つめの「Pragmatic Thinking and Learning」って何かと思ったけどこれかな
Amazon.co.jp： リファクタリング・ウェットウェア ―達人プログラマーの思考法と学習法: Andy Hunt, 武舎 広幸, 武舎 るみ: 本(アフィリエイトつきでないリンク)
あ、ひょっとして
Amazon.co.jp： Presentation Patterns: Techniques for Crafting Better Presentations eBook: Neal Ford, Matthew McCullough, Nathaniel Schutta: Kindleストア
(アフィリエイトつきでないリンク)
って翻訳出てない?
Amazon.co.jp： プレゼンテーション・パターン: 創造を誘発する表現のヒント (パターン・ランゲージ・ブックス): 井庭 崇, 井庭研究室: 本
(アフィリエイトつきでないリンク)
は別物だよねえ
ぼちぼち読み始めているんですが、
読む前に情報収集 :) して気づいた(知った)ことがあって、なんかロクでもない扱い方されてるんですねこの方。
にも、フリードリヒ2世に関するのは酷く傷つけられている彫像だけ。
ガレは第6回十字軍を絵にしなかったのだとか
第6回十字軍 - Wikipedia
しかし
フリードリヒ2世 (神聖ローマ皇帝) - Wikipedia
には
