How to live in the Kingdom of Nouns, why mathematicians cry, filling gaps in algorithms, portion of clojure, STM, HTTP and more.
Another great Steve Yegge's post. Not a post, a tale about Javaland, a place where all verbs are owned by nouns. Accept it like an analogy between OOP and FP.
Verbs in Javaland are responsible for all the work, but as they are held in contempt by all, no Verb is ever permitted to wander about freely. If a Verb is to be seen in public at all, it must be escorted at all times by a Noun.
Of course to be escorted must be replaced by VerbEscorter.
The Verb "execute", and its synonymous cousins "run", "start", "go", "justDoIt", "makeItSo", and the like, can perform the work of any other Verb by replacing it with an appropriate Executioner and a call to execute(). Need to wait? Waiter.execute(). Brush your teeth? ToothBrusher(myTeeth).go(). Take out the garbage? TrashDisposalPlanExecutor.doIt(). No Verb is safe; all can be replaced by a Noun on the run.
You are not forced to use functions everywhere, but use them where it is appropriate to simplify solution and avoid enterprise hell. You know, not everything is an object. The same way not everything is a function.
Long paper by Paul Lockhart about problems in mathematical education.
Math class is stupid and boring. - Students.
Author claims that mathematics is an art, instead of some practical thing. Of course, it can be applied in real world and it is, but it's not primary goal of math.
A mathematician, like a painter or poet is a maker of patterns. If his patterns are more permanent than theirs, it is because they are made wit ideas.
Very exciting reading.
Algorithms are not just devils you need to learn for CS course or to prepare for interview. You can apply them to solve real-world problems. This SO answer provides links and some explanations where specific algorithm is used in linux kernel, chromium browser and some utils.
... Red-Black trees are used for scheduling, virtual memory management, to track file descriptors and directory entries, etc.
grep, implements the Boyer-Moore algorithm
fgrep implements the Aho-Corasick string matching algorithm. ...
Even Bubblesort has its application!
I'm huge Rich Hickey's fan. It's just a list of his most interesting presentations. Definitely, must see.
Two parts explanation how clojure vector works.
Yeah, simple square brackets
[1 2 3] in clojure have a lot complex things under the hood. Moreover, it gives understanding not only how vectors work, but how all other persistent structures can be implemeted in efficient manner.
Have you heard about STM?
It's a good model for concurrency control, like database transactions, but on memory. Much simpler and less error-prone to use. This article explain STM basics with some implementation details.
For my attempt to implement STM refer presentation
Five Parts article of looking at HTTP from developer's perspective. Worth reading to dig into some details.
Great list, perhaps most ideas are already partially implemented.
This is a vision for how computing could be. I began writing ideas down a number of years ago, this is a selection of ideas old and new.
Some of them are great:
Task management between computers is an unsolved problem in desktop environments. Many users have multiple devices. Sending tasks, inputs or outputs to different computers is painful. Usually sending audio to be played through another computer, taking control of an application running on another computer, sharing files or streaming data to other machines requires special software.
It would be great to have the same in reverse order also. I get a phone call, but phone is far away. Much better to click on current machine Accept Call and to talk. Security can be a challenging.
Keyboard shortcuts are configured differently in each program. Shortcut configuration should be in a standard format. This way you can load them and share them between operating systems and share configurations between applications.
This reminds me of xkcd comics:
Some ideas are not so great:
Mounting source code does not solve a problem at all, it's just adds a bit of sugar to project structure and adds more pain to build tools.
Metalist of Top 10 items of Top 10 java pitfalls.
Hundred times discussed, but if you are java programmer, you may refresh your knowledge. List of common java pitfalls includes:
The GOF religion
Return null from API methods
By the way, this list contains some other useful java things, like top 10 java people and top 15 worst Computer Software blunders. Not worst, but definitely bad.
Different Garbage Collector algorithms briefly explained. Bookshelf used as an analogy:
Bookshelf - Memory, Books - Objects.
Ruby GC implementation discussed, but you are not forced to know ruby to understand that. By the way, article contains a lot of links to more detailed GC algorithms explanation.mishadoff 25 November 2013