CEO/Principal Consultant at INNOQ, he/him, software architect, RESTafarian, conference tourist. Works at innoq.com. Fediverse: @stilkov@innoq.social

Germany
Joined April 2007
Filter
Exclude
Time range
-
Near
Replying to @jinxman
@jinxman Da würde ich der @mopo einfach schnell eine Rechnung schicken.
2
1
Replying to @thattommyhall
@thattommyhall I'm sure you meant "touché"? (Sorry, couldn't resist :-)
1
Replying to @jbrains
@jbrains @kaleidic @jessitron @ronjeffries @tastapod Just ignore me, replied with no context whatsoever
How to make sure order in programming doesn't matter
1
2
Replying to @apaipi
By now, @apaipi has very clearly become my favorite announcer. Looking forward to a daily talk show.
1
#(+ %1 %2) RT @jbrains: { |a, b| a + b } RT @RonJeffries: @tastapod @jessitron [ :a :b | a + b ]”
1
And now for some "Fun with dead languages" with Damian Conway #qconlondon
@BlackPepperLtd Thanks, much appreciated
Replying to @psd
@psd @mnot @jimwebber Listening to Damien, too
@pcalcado Re. dataflows: Not that I care much for Groovy, but have you looked at GPars?
Replying to @NicerInPerson
@mikekelly85 sorry about that :-) I'll be here until Friday night
Now listening to @pcalcado on SoundCloud's API #qconlondon
FWIW, uploaded slides for my #qconlondon “Web Development: You're Doing it Wrong” talk innoq.com/blog/st/presentati…
1
8
18
“A new request Client Hint header field that allows the client to perform proactive content negotiation” github.com/igrigorik/http-cl… (via @mnot)
1
6
3
Replying to @NicerInPerson
@mikekelly85 @mnot You most definitely are :-)
Now listening to @mnot talk about HTTP/2.0, because why settle for less? #qconlondon
2
1
"A good REST API is like an ugly website; RESTful clients should follow links and submit forms" @rickardoberg at #qconlondon
1
18
3
"Most websites are better REST APIs than what we call Web APIs" @rickardoberg at #qconlondon
14
4
Great talk by @psd on gov.uk this morning, now looking forward to @rickardoberg's road to REST #qconlondon