Recommended ReadingsSome interesting topics this time despite me spending lot of time on the Principles of Reactive Programming course: Java x Node.js, REST x other future-proof architectures, scary legacy code. Of course, also plenty of Clojure.
People, organizations, teams, development:
- Chris Argyris (1923-2013): An Appreciation - Thinkers 50 - recently departed Ch. Argyris is a person whose work you should know, if a bit interested in learning and organizations and how they (dis)function; and since we all work in organizations and want our work to be pleasant, this means all of us. We all want to work in orgs that do double-loop learning, i.e. they actually evovle as they learn. "Argyris argued that organizations depend fundamentally on people and that personal development is and can be related to work." Now stop and go read it!
- Bob Marshall: The Antimatter Principle - "the only principle we need for becoming wildly effective at collaborative knowledge work" - can be summarized as "attend to folks' needs" (importantly, including your own) => find out what people actually need, interpret their behavior (including anger, seemingly irrational or stupid requests etc.) in terms of needs; mastering this will make you excell in communication and effective work. Read the post to find out more.
- It’s a state of mind: some practical indicators on doing agile vs. being agile - are you agile or are just "doing agile"? Read on ti find out, if you dare! F.ex. "Non Agile teams have a process that slows the review of the changes." Cocnlusion: "An Agile mindset is just that – a state of mind, a set of values. Its a constant questioning, and an opening up to possibilities. Its a predisposition to produce great things."
- Johannes Brodwall: Humble architects - how to avoid being an architect that does more harm than good, as so many out there? Some tips: Don't assume stupidity, Be aware that you might be wrong, Be careful with technology (i.e. simplicity beats everything; applies so much to us developers too!), Consistency isn't as important as you think (or beware context), Tactical reuse in across systems is suboptimization (i.e. reuse has a cost), separate between (coding) rules and dogma (i.e. is that way unsafe, incomprehensible, or just a heresy w.r.t. a dogma?) Very valuable insights into creating good technical solutions and teams that work.
- Liz Keogh's The Dream Team Nightmare: a Review - a very good review of this adventure-style book about coaching "agile" teams through (around?) common pitfalls, provides a good base for deciding whether you shall read the book (Liz essentially says yes)
- Fibonacci Kittens: One Idea One Commit - a short story of coming from biannual releases to frequent release of individual features; I link to this primarily to spread optimism, if this company managed it then, perhaps, we other can too?
- The Eternal Struggle Between Business and Programmers - "Business: More features! Now! Programmers: More refactoring! Now!" How can we resolve this eternal conflict of needs? This post reveals how the two parties can find a common ground and mutual understanding (beware, everybody must give up on something) and thus work together rather than against each other.
- Why the future is NOT RESTful - always refreshing to read something against the mainstream; "REST is not fit for the next generation of smart client applications because it has not been designed for smart clients." According to the author, a smart client app stack needs: "1. persistence (storage and query), 2. documents/orm (conversion to tree-like datastructures), 3. data authorization (once authenticated), 4. pub/sub (websocket communications), 5. client db (client-side caching and querying), 6. templating (presentation level)" Meteor.js has nearly all but #3 thanks to mongodb (1+2), dpp (4), mongo on the client (5), spark (6). The author considers a similar but Clojure-based stack (with Datomic, Angular etc.) and looks at authorization possibilities. "Secured, personalised, CRUD operations are the future to a more simplified web." We may agree or not but it certainly is worth reading.
- Michael Feathers (of Working Effectively With Legacy fame): Unconditional Programming - "Over and over again, I find that better code has fewer if-statements, fewer switches, and fewer loops. Often this happens because developers are using languages with better abstractions. [..] The problem with control structures is that they often make it easy to modify code in bad ways." Includes a nice example of replacing if-else with much more readable and safer code.
- The Quality of Embedded Software, or the Mess Has Happened - an interesting and scary read about terrible spaghetti code (and hardware) that makes some Toyotas to accelerate when the driver tries to break; 11,000 global variables, the key function showing so high cyclomatix complexity that "makes it impossible not only to test but even maintain this program in any way." Then 80k violations of the car industry coding standard cannot surprise. And a safety control that does not work. Interesting that a great manufacturer may have so terrible IT (and Toyota isn't the only one).
- The string type is broken - the String type is M. Feathers' favourite example of a leaky abstraction - most languages fail to process/split/count less common Unicode characters properly, the fact that String is implemented as a series of bytes leaks through (UTF-16 langs like Java); worth reading to be aware of the limitations
- Why I'm Productive In Clojure - some interesting points about simplicity, consciousness, interactive development, power without overwhelming fatures, etc. "With it [Clojure] I can always easily derive a solution to a particular problem from a small set of general patterns. [..] However, the number of ways that these concepts can be combined to solve all manner of problems appears to be inexhaustible."
- Node.js at PayPal - PayPal is switching from Java to Node.js (among others to promote language consistency) and, as a part of that, has implemented the same app in Node and Java; results: Node was done earlier, had less code, performed better (though, as Daniel Kvasnička pointed out, "Comparing Node.js and servlet-based archs is not fair... compare Node with @vertx_project and you'll get a whole different story ;)"; also, as Charles Nutter said, "The
@PayPal numbers for their Java to Node move are absurd. A JVM app doing 1.8 pages/s isn't slow...it's broken.")
- IBM: Developing mobile apps with Node.js and MongoDB, Part 1: A team's methods and results - also IBM has implemented the same (REST) app once with Java and DB2, once with Node and Mongo where Node+Mongo required less work and performed better; one of the great wins was having JSON as a native structure everywhere instead of transforming from/to it so Mongo is, in my opinion, an important factor in this particular case
- Dynamics of Programming: Benefits of Scala in CS1 - reasons for and experiences with using Scala in an introductory computer science course, worth reading; some of the advantages over Java are consistency (.asInt on String and Double vs. casting/parsing, no "primitive" types), REPL with time inference good for learning, functional style enables focus on what rather than how; quite persuasive arguments
- The New Threat: Targeted Internet Traffic Misdirection - did you know that internet traffic to any site can be made to go through a particular server without anybody noticing? This has been observed repeatedly in the wild, for banks and other sites. Rather make sure you use strong encryption (NSA-approved, of course ;)).
- A (relatively easy to understand) primer on elliptic curve cryptography - Everything you wanted to know about the next generation of public key crypto - you cannot just read this, you have to study it, which I did not; but it looks good and I guess the time will come when I will come back to it
- Prezi: Intro to Specification By Example - a journey, not a destination (W. King; via @mortenberg) - a nice presentation that can be used to introduce SbE, with focus on the important things (collaboration) and some practical experiences
- Mind Maps and Automation (via
@gojkoadzic) - a smart idea to use a mind map to display break-down of the status of testing of a system (red/orange/green) instead of just one indicator, based on the observations that managers & co. never drill down below the first indicator
- MIT Technology Review: 10 Breakthrough Technologies 2013 - for those interested in the future - f.ex. ultra-efficient solar power, supergrids - highly efficient DC power grids, additive manufacturing - on the verge of using 3-D printing to make jet parts, memory implants
- Sugru - a genius DIY material for improving anything; also, very nice A partial visual history of sugru (via Bjørn Remseth)
- Stuart Sierra's Component - a library for making it easier to implement Stuart's reloadable workflow; a component is something that can be started, stopped, and depend on other components so that it is easier to do interactive REPL development
- Logan Linn: Clojure/conj 2013 - a pretty good overview of the conference
- Caribou - "the kernel of usefulness that has emerged from years of this basic practice"- a new Clojure web framework - seems to be interesting
- Results of the 2013 State of Clojure & ClojureScript survey and drill-down into what features people want - the most interesting fact is how many more participants use Clojure in production than last year and perhaps also the relatively wide adoption of Datomic among the respondents. Light Table has become the 3rd most popular dev. env., after Emacs and Vim. Some of the most mentioned language features requested were types (=> core.typed, Prismatic's Schema), better error reporting (=> slingshot, dire, clj-stacktrace, io.aviso:pretty, etc.), debuger (though progress is being made)
- Book: Clojure High Performance Programming
- Improving Clojure Feedback : Stack Traces - making Clojure stacktraces more usable by filtering out noise and linking to relevant content - io.aviso:pretty, io.aviso:twixt
- Clojure Dev discussion: Hashing strategies - Executive summary - "In Clojure, however, it is far more common than in Java to use longs, vectors, sets, maps and compound objects comprised of those components (e.g., a map from vectors of longs to sets) as keys in other hash maps. It appears that Java’s hash strategy is not well-tuned for this kind of usage. Clojure’s hashing for longs, vectors, sets, and maps each suffer from some weaknesses that can multiply together to create a crippling number of collisions." Ex.: An implementation of N-Queens took forever, spending most time on hash collisions. But be calm, smart Clojurians are working on a solution.
- Datomic Pro Starter Edition - Datomic with all storages, Datomic Console, a year of updates, full Datomic programming model; limitations: no HA transactor, no integrated memcached, max 2 peers and 1 transactor
- AirPair.com - a new site that enables developers to get help from other devs via remote pairing, code review, code mentoring etc. - a good opportunity to get help / help others (and earn something); I haven't tried it but it sounds pretty interesting
- Meteor: JS frontend + MongoDB backend with changes in the DB pushed live to the clients, i.e. MongoDB is used both as the "application server" and storage. It seems great for apps where users need to collaborate in real-time with each other, certainly great for quick proof of concepts etc.; worth checking out; it also comes with free (at least for start?) hosting so really good for prototyping - "an open-source platform for building top-quality web apps in a fraction of the time." The intro screencast will give you a good overview (10 min).
- Mean.io - MEAN (Mongo, Express, Angular, Node) stack Boilerplate - frontend, backend and storage using the same language and some of the most popular technologies (not that popular = best fit for you :)); it seems to be very new but since it just glues together 4 popular and documented technologies, that should not be an obstacle. There is an intro on the MongoDB blog.
- BusyBox (get latest win binary from Tigress.co.uk) - reportedly a better POSIX env for Windows than gow, Cygwin, et al.
[..] no organization should exist unless it is "of service" to its employees, its customers, its community. - @Tom_Peters 28/11
I hope you'll agree that there is a certain amount of irony involved in having to write repetitive code - Dmitri Sotnikov in Why I'm Productive In ClojureHappy teams are productive teams but:
Morale is 95% a function of the prevailing system (the way the work works). Which in turn is a function of the prevailing collective mindset - @flowchainsensei Nov 10th