martini

The funny thing is that, due to Bond's popularity, asking for your martini stirred is now the contrarian thing to do.

It's like they're amused at the idea that any particular situation, person or statement could possibly make their martini taste bad.

My opinion is that Martini took a pragmatic approach to getting things done.

The author of Martini released his framework, some people in the community said it wasn't idiomatic Go, he agreed and eventually released another one called Negroni.

A stirred martini will be clearer than a shaken one.

Applying the Martini Method to coding is not so simple: as has been pointed out countless times, programmer productivity can't be measured in lines of code produced.

Personally, I would like to highlight the part about Martini not being idiomatic.

Now what, the three-martini lunch of the 1950s?

I use a variant of the Martini Method where I try for at least 2 substantive svn commits a day (not including minor bugfixes or cosmetic issues).

Obligatory s/martini/negroni comment here.

I'd recommend against both martini and gin.

True story: I was in a group project in a distributed systems class, and we had made a project that relied on a go http routing package (I think it was martini or something).

This is another good walkthrough which focus more on what is perhaps considered more "idiomatic Go" than using Martini.

The "short" version is that Martini did a lot of 'magic' stuff with run-time reflection.

If he was 50 right now, he's right at then end of the "3 martini lunch" brigade that became socially unacceptable about 1990.

A shaken martini sucks but I wouldn't call it "ropey".

Negroni is from the creator of Martini, Goji is apparently high in antioxidants, but I'm partial to Macaron.

These ports from Python and Ruby (like Martini, for another example) are well-intentioned, but I don't think they're a good idea to use.

Martini is cool but you probably don't need it.