Literate Programming versus Unix shell (?)

See More shell, less egg for a great example of two completely different approaches to a programming problem.

11 programming trends to watch

Here.
Specially number 3, No code is an island
"There's a dark side to these tightly integrated stacks of code: the walled garden."
Number 8, Traditional education fades from relevance

coding isn’t fun if all you can do is call things out of a library (Knuth)

"Today, I mostly paste libraries together" in Whatever happened to programming?

Is this the problem with today programming? Or are the libraries too dull? dumb? Low-level? Insuficient abstraction?

Think of the very different concept of Unix small programs put together, one after the other, to "treat" data. See next post,Literate Programming versus Unix shell (?)

Forget “Enterprise-Class Software”

"The term “Enterprise Software” is poisonous because it implies a scalability ceiling for a solution serving a few 10,000 people that used to be ambitious, but that’s no longer the case. It’s also no longer the hardest class of software solutions – not at all."
Read here, Enterprise Software is much much simpler than, example, multi-players games. Think of scale and availability.

Types, classes of Mathematical abstractions?

Back from types and classes to the more abstract mathematical entitie:Where do types come from?

Answers in  Translating math into code: Examples in Java, Python, Haskell and Racket.

For more details look at Chris Okasaki's Purely Functional Data Structures book.

The futility of developer productivity metrics

..."A highly effective, productive developer workforce is often the result of high-quality, effective management. Unfortunately, nobody has developed a metric for that yet. Coincidence?"

Lasagna code

Good Lispian rant at the complexities of object oriented and other languages as compared to Lisp, Scheme or Algol.