Almost all of the code examples in the book are in JavaScript (not Java) though a significant feature of Sharvit's approach is that it decouples Data Oriented Programming from any specific language. As a Clojure geek, I highly recommend the book as the way to achieve some of Clojure's core virtues in other languages.
I still have my cherished VT125 EDT rubber overlay from when I worked at DEC '82-'85. Great editor. And the amazing thing was that there could be 50 people time-sharing on a single 1 MIPS Vax 780, and EDT was very responsive, virtually no lag.
I came here to mention this book also. I learned a lot. He explores a mind numbing number of properties which are potentially in the mix. They depend in turn on the properties of the source material. (Authors play all kinds of games with meter and structure and arbitrary constraints - and preserving some can come at the cost of deprecating others.)
One warning: among the genuinely deep insights, Hofstadter can occasionally come off as smug and self-congratulatory about his own poetic genius. I found this rather off-putting - and surprising since I found the tone of G.E.B. rather more like enthusiastic play.
Very cool. Back in ancient times, shortly after Kerberos for GSS-API came out I was tasked with achieving interoperability between Hewlett-Packard's GSS-API implementation (based on MIT's) with popular commercial ones (Cygnus? Microsoft?). It was my introduction to subtle art debugging crypto protocols, handy when SSL came along. Implementing to the spec doesn't necessarily mean they'll interoperate. This brings back some memories: https://web.mit.edu/kerberos/krb5-devel/doc/appdev/gssapi.ht...
True. I chose my neighborhood in Somerville with proximity to the T as a top priority because I assumed I'd be taking it to work in Kendall every day. Then I bought a bike and found it better in almost every way: free, enjoyable (much of the time), healthier, and much faster. So much so that I biked nearly all of the time, year-round. I had dedicated lanes for most of the trip, and quiet almost car-free neighborhoods for much of the rest.
An unexpected pleasure was the schadenfreude of passing scores of cars on Hampshire/Beacon on my way home during rush hour.
An unexpected annoyance was the fair weather bikers who don't seem to know their bike has gears, and take f.o.r.e.v.e.r. to get going at a green light.
And free outbound from Logan! Though I must say, the last time I did this it was a bit of a nightmare. The SL1 was very late and we were packed in like sardines.
I've long been impressed by Hickey's problem solving skills, so I took much of this talk to heart, and even bought a copy of HTSI. Can't say it really helped me any more than Rich's talk (as a programmer) but I'm thinking I'll give it another look.
There is a viable path from (upper?)-middle class to early retirement that is built mostly out of hardcore discipline, willingness to delay gratification, and some luck. The idea is to live well below your means, be "frugal", and pound every spare dollar into tax advantaged retirement accounts (first) then your own aggressive growth equities. Get a bonus? The whole thing goes to your brokerage, have a stock plan at work? Max it. Since this mild form of FIRE may take 30+ years, you should invest aggressively in equities (risk decreases with longer time horizon) and possibly buy some rental properties along the way. IMO this gives the best probability (though no guarantee) of retiring financially independent before age 60.
Almost all of the code examples in the book are in JavaScript (not Java) though a significant feature of Sharvit's approach is that it decouples Data Oriented Programming from any specific language. As a Clojure geek, I highly recommend the book as the way to achieve some of Clojure's core virtues in other languages.