adambrault
Joined 15 years ago
Joined 15 years ago
We're putting together the Redis event for the same reason we organized krtconf: we wanted to go to something like it and it didn't exist yet. We're developers first, so we're curating the content we most want to hear.
We worked hard for months proactively putting together the content for krtconf and here's the schedule as it ended up for last year: http://2011.krtconf.com/schedule/
We're still early in the content planning process, but just so you have an idea of the kind of effort we intend to put into the first RedisConf, here's what some folks said about the first krtconf:
"The quality of the talks is going to influence the quality of the conversations. The talks here have been great and the conversations have been even better." - Mikeal Rogers, Nodeconf / Pouch
"krtconf has been amazing. It’s a melding of the minds." - Kyle Drake, Geoloqi
"krtconf 2011 was impressively polished. Thanks so much for putting on the conference. I had a great time and would love to attend again. the conference was excellent, and I really appreciated how much work you guys put in." - Nate Smith, Derby.js
"Seriously awesome conference." - Pradeep Elankumarn, Kicksend
"Just wanted to say thanks for an awesome time. Really enjoyed the conference, the speakers and giving my talk. I have no doubt this will be the first of many Krtconfs." - Owen Barnes, Socketstream
"The conference has exceeded my expectations." - Astro (github.com/astro)
It's actually the feature restraint that makes it so remarkably useful and powerful.
Here's what we do. Every day, we start a new thread and each person on our team posts a daily checkin "rating" their day and then writes any comments on what they worked on, what they learned, what frustrated them, etc. Super simple stuff, for sure, but it's been one of the most valuable things we've done for creating a strong sense of team and togetherness.
What's been most surprising about this is that most of our team of 15+ work within feet from each other in our office, but our team's connectedness feels better than ever as a result of Ginger.
As the guy who generally plays this role on our team, I'm quite certain none of our developers would say they outwork me.
It's easy to see how someone without practical boots-on-the-ground, neck-on-the-line experience in design, development, or business could be utterly horrible to work with as a product manager.
But in that case, you're just working with someone who's unqualified and propped up by authority. Forget role or job title. That's painful under any circumstances.
That's it.
I'm hereby turning in all my spelling bee ribbons.
You win, starpilot. You win.