I had time to set up a Redis, and do a test run with Rediska – a PHP interface to Redis. It worked, and it’s in PHP. I was more impressed with the redis-cli experience. There are many atomic commands in Redis, and the datatypes are quite helpful.

We spent some time walking through a BDD tool for async web framework Node.js: VowsJS. When that was done, we looked at kyuri, the library that can transform a Cucumber feature spec into a skeleton VowsJS “vow”. kyuri was used for prenup, a web tool to create Cucumber specs for Node.js projects. prenup was quite alpha, but we sympathized with the concept.

Joel pointed to PHP-based web frameworks “like Sinatra“, and found a few that he rejected. The last man standing was named GluePHP. He can list his gripes with all the others. We looked at Troels’ Konstrukt, as well, and it got good reactions. It’s good, but it’s nothing like Sinatra.

Flask is a web microframework which was used at Forskningsavdelningen last night. “I don’t know how to use this, so let’s begin.” And we begun, and had a website up and running pretty soon. A roadblock in the form of “convert a regular font file to a PIL-font format” appeared, and a hell-of-Portfiles ensued. I should start using Homebrew…

Oskar had referenced Windows hacker Scott Hanselman, and we praised his article on changing default web browser in Visual Studio for it’s complete hacker attitude. Here is a link to his PowerShell category on his blog.

Oh, Hanselman lists Windows tools he uses.

Other stuff, that should be mentioned, so as not to forget:

Whiskey Disk is embarrasingly fast deployments – their videos, presentations, etc, are very convincing, and “keep it easy.” Someone who takes Capistrano down a notch for “not being simple enough” should be listened to. The system seems quite capable.

Inspiration: This morning I saw that some Drupal folks were using a Phing task to automate fetching and building a customized version of Drupal, for their deployment. They included two useful tasks: help and explain, where help informed about the available options, and explain printed all the variables that would be used when running a phing build. Also, they informed the user of how to change those variables right on the commandline, and gave the tip that they should run the explain task with changed command-line settings. This would verify that Phing had understood the user’s invocation correctly.

But, as a wise woman often says: “…it’s not television, it’s HBO.”

This picture is now a part of a huge collection of images of looms. I just love the Internet for that.

Via article about AI.

Riktlinjer och regler för användning av egen bild:

• Bilden får inte kränka annans upphovsrätt, rätt till varumärke eller annan liknande rättighet och ska följa god sed. Detta innebär att bl a följande regler måste följas för att en bild ska kunna godkännas.
• Bilden får inte innehålla företagsnamn, föreningsnamn eller kännetecken för företag eller föreningar, eller varumärken, logotyper eller mönsterskyddade produkter.
• Bilden får inte innehålla reklam eller syfta på någon med bankens tjänster konkurrerande produkt.
• Bilden får inte föreställa offentliga personer, som t ex politiker, musiker eller idrottsmän.
• Bilden får inte föreställa någon identifierbar person utan dennes medgivande.
• Bilden får inte innehålla motiv eller värderingar av samhällsfientligt, olagligt, rasistiskt, politiskt eller religiöst slag.
• Bilden får inte visa personer involverade i olagliga eller rasistiska aktiviteter.
• Bilden får inte innehålla svenska eller utländska texter, siffror och symboler, ej heller personliga data eller webbadresser.
• Bilden får inte innehålla inslag av vapen och militära fordon eller av alkohol, tobak eller andra droger.
• Bilden får inte ha provokativa, sexuella eller stötande inslag.
• Bilden får inte innehålla nakna eller halvnakna vuxna eller barn.
• Bilden får inte kunna uppfattas som våldsam eller obscen.
• Bilden får inte skapa säkerhetsmässiga eller andra problem vid användning av kortet, t ex får inte sedlar och mynt visas.
• Bilden får inte utformas så att kortet uppfattas som vitt eller guld- eller silverfärgat.

We met. We hung out. And, walked through the *Dynamo paper*, which was released in 2007, and is quite self-contained. That makes it “a NoSQL classic”. Good paper with which to open a reading circle. Now we have some pre-understanding for upcoming papers.

Photo by kalavinka

Other content

Neo4J’s Peter Neubauer, riffed on on Google’s data hugeness, which led us further afield: Google / Big Data; Crowdsourcing — WordNet; Concept: Discard 99% of the data, using the top 1%.

Thoughts on format

We’re currently toying with new/different perspectives/formats:

• “Developer Perspective”
• “Infrastructure/Scaling Perspective”
• “Arch. Perspective”
• “Apps/Ops Perspective”

Polyglot cases: How do you work with several multi-database setups?

Event bus usage: Some people use NoSQL stuff for the event buses. What are pros and cons here?

Do you need anything else there? I really enjoy this peek behind the scenes, implementation problems, etc. It is not something I can bring directly to my workplace and use, but I like the challenge of understanding large concepts together. The current format suits me well.a

Some hints and tips I picked up:

Google’s research end-of-level boss Peter Norvig’s talk at Berkeley (YouTube you-feel-lucky) — summarizing all the fields of research. (His official title is Director of Search Quality.)

A question: Is Stepanov’s Elements of Programming any good? Is it for me? (C++, math, beautiful type-setting.)

Next paper?

Google’s Bigtable? Cassandra? I cheated, and begun reading the Cassandra one. Let’s see how that goes.

Just great. People were their normal selves, but everyone just had that extra edge of greatness that night.

It begun with a minor planning meeting in one corner. Pragmatic. Anna F came by and planned her workshop.

StG had worked on his Rbox project, and murmured “Do you want to help program this beast?” and muttered something about the eZ80 programming environment. Suddenly, there’s a noise “yeah, it’s the MOD player I built in” and later there were graphics. “It works!” he cried, at one point, and everybody rushed to, to see the greatness. There was greatness. I won’t spoil the greatness, you can witness it at Hacknight this Saturday.

In one corner, a PHP discussion group formed, as I had installed crisis mapping software Ushahidi — which is written in PHP. “Why do they tell me to program everything in Java?” a confused PHP user asked me. I answered. “What’s a class, really?” someone else asked. I answered. “Does PHP have to be so bad?” a third person asked, and me and qzio answered, by displaying how magic methods __call, __set and __get work. qzio also showed a PDO class wrapper, which might well see action at someone’s workplace.

Some film-makers were present, scouting the location, fitting the images in their heads. It will be a glorious documentary.

A great time was had by all.

Think of those rules. Of what they mean.

Indulge me. I allowed myself to make a little poster.

Öresund JavaScript Meetup #10 on June 14, in Malmö, at Hypergene’s offices.

I guess there are a couple of things wrong with it. The date and time are lacking. Monday June 14. At 19.00. The URL says those things. (But people looking at a poster can’t click it.)

These guys would disapprove.

Update: Now, I went and added that stuff.

Still, the workshop will be great.