Blog

Apr 22 2014

Comments

Apr 10 2014

Comments

Apr 01 2014

Comments

Where to Find Cognitects: April Edition

Want to meet a Cognitect in person? Here's where you can find us during the month of April:

Durham, NC 4/4-4/5
Inaugural ClojureBridge Workshop
Attending: Sandy Ezzell, Kim Foster, Justin Gehtland, Lynn Grogan, Naoko Higashide, Jamie Kite, Yoko Harada

New York, NY 4/4-4/5
New York Software Symposium
Speaking: Stu Halloway
Sessions: Clojure in 10 Big Ideas, Narcissistic Design, Simulation Testing with Simulant, Generative Testing

St Louis, MO 4/11-4/12
Gateway Software Symposium
Speaking: Stu Halloway
Sessions: Clojure in 10 Big Ideas, Narcissistic Design, Simulation Testing with Simulant, Generative Testing

St. Louis, MO 4/15
St. Louis Clojure Meetup
Organizing: Alex Miller

Durham, NC 4/15
West End Ruby Hack Night @ Cognitect HQ
Attending: Yoko Harada

Boulder, CO 4/19
LambdaConf
Speaking: Ryan Neufeld
Talk: Building Web Applications in Clojure

Durham, NC 4/24
Triangle Clojure Users Group @ Cognitect HQ
Attending: Yoko Harada

Online 4/24 at 10 am PDT
O'Reilly Webcast
Speaking: Ryan Neufeld
Topic: Building Web Applications in Clojure

Reston, VA 4/25-4/27
Northern Virginia Software Symposium
Speaking: Stu Halloway
Sessions: Clojure in 10 Big Ideas, Narcissistic Design, Simulation Testing with Simulant, Generative Testing, core.async, Datomic for the 96 Percent

Richmond, VA 4/29
RVA Data Hackers
Speaking: Craig Andera
Talk: Datomic: Data, Meet Simple

Durham, NC 4/29-4/30
Intro to ClojureScript & Datomic Training
Trainer: Stuart Sierra

Mar 25 2014

Comments

Bridget Hillyer - Cognicast Episode 053

cover art

We talk to Bridget Hillyer about ClojureBridge and increasing diversity in the Clojure community.

Listen to or download this episode.

Read More »

Mar 18 2014

Comments

Alan Dipert - Cognicast Episode 052

cover art

We talk to Alan Dipert about Hoplon, a set of Clojure libraries for writing interactive browser applications.

Listen to or download this episode.

Read More »

Mar 16 2014

Comments

s/DevOps/Etsily/

Dave Thomas urges us to kill the word "agile". Many of the original leaders in agile software development have now disavowed the term. Why? In short, it's been devalued. Literally, stripped of its values. Today, the word is used as a capitalize noun, as in the hideous phrasing, "Do Agile," rather than as the lowercase adjective it was meant to be.

The word "Agile" always seemed like a branding initiative, bundling together the various things we had been calling "lightweight methods" and giving them a business-friendly label. It succeeded. No manager in their right mind goes on record saying, "Agile? We'll have none of that, thank you very much."

Dave suggests that we need an adverb rather than an adjective. It should describe how we develop software, rather than describing ourselves.

I think we face the same problem, and the same debate, with the label "DevOps."

Here's my proposal. We do need a label for a style of organization. Not for a team, nor for the individuals within that organization. If nothing else, we need that label as a shorthand to describe the style of interaction we expect. It helps us understand what culture to expect.

However, I think we also need a label that isn't so attractive to tool vendors and Big Process consultancies.

I propose we adopt the adverb "Etsily". It refers to Etsy of course, since they are the avatars of DevOps anyway. It sounds a little bit silly, so it should safely repel the blue-shirt consultants and enterprise tool vendors. Finally, it's an adverb so it can be used in sentences like, "We build things etsily."

Mar 11 2014

Comments

Dan Croak of thoughtbot - Cognicast Episode 051

cover art

We talk to Dan Croak of thoughtbot about the thoughtbot playbook, their approach to remote work, and their software development philosophies.

Listen to or download this episode.

Read More »

Mar 03 2014

Comments

Where to Find Cognitects: March Edition

Want to meet a Cognitect in person? Here's where you can find us during the month of March:

Boston, MA 2/28-3/2
New England Software Symposium
Speaking: Stu Halloway
Sessions: Clojure in 10 Big Ideas, Narcissistic Design, Simulation Testing with Simulant, Generative Testing,

London, UK 3/5-3/7
QCon London
Speaking: Michael Nygard
Talks: Exploiting Loopholes in CAP, Maneuverable Architecture, Systems Thinking and Methods

Columbia, MD 3/5
Data Science MD Meetup
Speaking: Craig Andera
Talk: Data Structures with Clojure

St. Louis, MO 3/6
St. Louis Lambda Lounge
Speaking: Alex Miller

Online 3/7 at 1pm PST
O'Reilly Webcast
Speaking: Fogus
Topic: The Shape of Functional Programming

Madison, WI 3/14-3/15
Greater Wisconsin Software Symposium
Speaking: Stu Halloway
Sessions: Clojure in 10 Big Ideas, Narcissistic Design, Simulation Testing with Simulant, Generative Testing

St. Louis, MO 3/18
St. Louis Clojure Meetup
Organizing: Alex Miller

Durham, NC 3/18
West End Ruby Hack Night @ Cognitect HQ
Attending: Yoko Harada

San Francisco, CA 3/21-3/23
Intro to Clojure, ClojureScript & Datomic Training
Trainers: Luke VanderHart, Stuart Sierra

San Francisco, CA 3/24-3/26
Clojure/West Conference
Organizers: Lynn Grogan, Alex Miller
Speakers: Timothy Baldridge, Stuart Sierra
Attending: Kim Foster, Justin Gehtland, Stu Halloway, Rich Hickey, Luke VanderHart, Alex Warr

Everywhere! 3/24
Clojure Cookbook Hits the Shelves!
Authors: Ryan Neufeld, Luke VanderHart

Feb 25 2014

Comments

Feb 17 2014

Comments

Culture is Defined by What You Cannot Say

I've been revising my DevOps at Five talk for GOTO Chicago. In it, I talk about the CAMS model for DevOps. The 'C' in CAMS stands for Culture, and it's always a hard one to define. Yes, we do say that DevOps is about culture not tools. But what kind of culture? I can say everything is a culture. Agile development is a culture. But so is waterfall development, or cowboy coding.

Every time we try to define the culture, we end up using words like communication, collaboration, and feedback. The problem is that those words don't differentiate DevOps from ITIL, TQM, or any other operational process since Deming.

Your culture is really defined by the things that would be unthinkable to say.

In that light, I'd like to offer some statements that you will never hear in a DevOps culture.

  • That's not my job.
  • (From a developer) Well, the tests all pass, so the problem must be in Operations.
  • (From operations) I did everything right, it must be a code problem.
  • Oh, production is down? I didn't know.
  • I built the production environment by hand. There's no reason to automate it because we're only doing it once.
  • How close is QA to production? I don't know.
  • You need a new environment? Put in a service request and we'll see.
  • Your service request was approved. You should have a new machine in a few weeks.
  • Why do you need another terabyte of storage? You're already using a terabyte!
  • Our DBAs won't let you install that server. We're a SQL Server shop.
  • I don't know what our slowest query is.
  • I don't know how many cores our production environment has.

I could go on, but I think you get the idea.

How many statements like these do you hear around your company?

Popular Tags