UPSTART “street party” helps local entrepreneurs connect to startup resources

What: UPSTART, an innovative, entrepreneurial networking event and showcase

Sponsored By: NKY Tri-ED, NKY Chamber of Commerce, ASWD Law, Republic Bank, BLDG, West Sixth Brewing

When: September 19, 2013  | 4:30 – 8:00pm

Where: Pike Street, Covington, KY 41011
Free parking available next to Artisan Enterprise Center located at 27 West Seventh St.

Cost: Free to attend

RSVP: http://www.eventbrite.com/event/7394991619

Description: (Covington, KY) – On September 19, beginning at 4:30pm, the City of Covington will close Pike Street to launch UPSTART, a street party designed to inspire the entrepreneur in all of us. The purpose of the UPSTART event is to connect entrepreneurs with local organizations who provide resources to startups.

October Training Smackdown

Beginning this week and continuing for the next month I’ll be heading off to various training, certifications, and seminars including CDBG, Affordable Housing, and KY APA. I’ll be doing my best to catalog things I learn, insights and anecdotes, as well as resources here.

Because of that oncoming train-pocalypse, I have not made time like I should to draft a proper post for this week.

Instead I’ll leave you with a short story about a city council meeting I attended last night:

After having just finished my presentation on tax rate calculations, several ordinances are given their first reading. Among them was an ordinance about nuisance and All-Terrain Vehicles (ATVs and Dirt Bikes).

Upon the reading of said ordinance, a couple stands up at the back of the room and starts throwing accusations that this ordinance was crafted specifically to target them. They suggested that city council could perhaps control the train whistle and dust that trains kick up, likening the power to stop dust and noise to godly power.

A heated exchange followed where shouting, finger pointing, and emotions ran high. At one point the couple decided that it was a sad day when people could not do what what they wanted on their own property. Finally the couple stormed out of the chambers while the city council proceeded to pass the ordinance.

A few moments later, a car begins driving by city hall blaring its horn every few minutes. As I walked out of the building at the conclusion of the meeting I saw that it was that same couple.

Whether the ordinance was right or wrong, I found the meeting entertaining.

Quantifying (and Qualifying) Self

Another recent hobby of mine is looking at data about my life. I think we can all agree that sometimes we just don’t remember things the way they happened. More often than not, this is observable in disagreements I have with my fiancee over various sequences of events. Given that problem, we become unreliable narrators of our own lives. In order to get at and understand some of the minutia of daily living it becomes important to have instruments, sensors, and data collection methods that fulfill a few criteria:

  1. Accurate – that these measurements are taken in parallel to qualitative information inputed by the user (me).
  2. Automated – that data collection takes place with little need for my direct involvement.
  3. Analyzable – that data collected present some meaning or capture something worth understanding.

On a quest to understand, how do you get all that data?

Undertaking this quest, I’ve fallen into the rabbit hole and found a web of services, solutions, and self-guided practices that have allowed me to begin tracking more.

I started early on with google calendar, excel, and a notebook. This required too much effort from me at times and was often forgotten in light of more important or immediate issues. Slowly I moved to using smart phones apps. Many of them I’m still using, but in more complex ways than before:

Saga: Probably the first thing I needed to get myself off of google calendars. It tracks the where, when, and how long while integrating information from other connected applications. It is both an end point and an entry point for much of the data I’m now collecting.

Sleep-bot: Sleep bot was a newer find, and was something that replaced a similar app I was using on my iPhone earlier last year. When I got an android phone I went without any sort of smart alarm/sleep analysis. Now that sleepbot has about three months of data, I’m starting to see trends and am slowly improving both the quality and quantity of sleep I get.

MyFitnessPal (MFP): I’m a bit off and on with this service, it integrates well with other apps and programs, but it requires attention and manual entry of food. There isn’t yet a good solution for calorie and food tracking, so this is about as close as I can expect anyone to get. I had originally used Lose It! but lost interest after some changes to the application and discovering MFP.

RunKeeper: The first app I started using (and began using again recently), RunKeeper has come such a long way since I first used it. It logs more than just running and now has support for a heart rate monitor. Easy to use, nice customization options on the audio cues, and definitely a main stay on my phone.

Have data, want additional data.

Recently I’ve also done some research into getting a fitness tracking device like fitbit flex, jawbone up, or basis. I’m currently waiting on an invite to purchase basis due to the additional sensors offered there.

The major problem with “quantified self” is the difficulty in pooling and analyzing data across systems, programs, and devices. Currently no simple solution exists, but Saga, MFP, and RunKeeper are all integrated via API/integration features. Basis is still fairly closed, but offers what I feel is the most robust device. An API would do much and more to help me pool my data and for developers to connect the services.

Where are we going here?

I’m really hoping that in the next few years I’ll be able to pool my data, and run regressions like crazy on it (the one really useful mathematical skill I learned in the PhD Program I recently left). In addition, I’d love to be able to take this information and show it to my doctor. As you’ll likely come to know, I’ve got a bit of a problem with weight (really its not that bad), and being able to show my physician whats going on, what working, and what is not would be nice.

I currently don’t have anything in place to help me understand how stress relates to my psoriasis, but that’s something I’m exploring for the future. I know stress and certain diets are affecting it, but I don’t know how. We don’t know as much as we could about psoriasis, and this might be one way of starting toward the big-data approach to understanding commonalities among people with psoriasis instead of the voodoo-like-advice I see on internet forums about it.

And another thing..

Two things I think are worth mentioning: the spatial dimension and the lack of qualitative data.

Spatiality is something I’ve talked about quite often in my (former) PhD program. Space, whether we like it or not, has interesting and unique impacts on the way we live. Even something as simple as bid rent theory suggests a complex relationship with economic thinking, sociological concepts that operate and motivate breaking or imposing social barriers, and psychological patterns of how we understand the world. Tracking some things without understanding the where will prove fruitless.

Qualitative data is also something I feel is worth logging alongside quantitative data. Some of my most insightful exploratory questions have come from looking at personal, group, and internet-consensus qualitative trends. Even something as simple as looking at a thread on Reddit can prove useful in finding new avenues of exploration and preliminary insight into how the question might be answered.

Every app and service I mentioned above has rudimentary elements of spatial and qualitative data collection, but it is not as robust nor as integrated as I would like. Hopefully that’s also in the future.

Homebrewing

Another thing I’ll likely be writing about consistently is our home-brewing.

By our, I refer to the list of people I collaborate with to brew beer:

  1. Rebecca (my fiancee) and I brew small all-grain batches (1 gallon) in our kitchen.
  2. Matt, Nikki, Mike, and Emily brew as a “guild” doing all grain batches.
  3. Rebecca, her father, and I brew extract kits together in his driveway.

Overall we’ve completed:

  • A failed Russian Imperial Stout that became the Midwest Godfather Hoppy Stout.
  • A going away gift to our friend Seth, the Going Away (Mosaic) IPA.
  • A Dunkelweiss we call the imBiber/imBieber,
  • A Maple Chocolate Porter, I call the MCP (Maple Chocolate Porter) Contingency Plan.
  • A Vanilla Porter we call Mad Maddie’s Porter.
  • An American Amber I called Papa Nezzy’s NumerUno.

We’re currently planning:

  • A pecan or almond brown ale (1 gallon all grain)
  • A pepper chocolate stout (5 gallon all grain)
  • A clone of the White House Honey Ale (5 gallon extract)

Most recently we finished the Dunkelweiss listed above. We opened the first bottles last Friday and overall we were a bit disappointed. Everything leading up to then had been promising, even Matt (the major skeptic), was waiting with bated breath for this beer. What we drank that night was good, if not promising, but not what we had anticipated.

We’ve resolved to let the beer condition for a month now and see if that mellows out the fruity/spicy/banana flavors and reveals some of the maltier flavor.

The Dunkelweiss definitely had our best brewing process to date, we resolves issues with mash efficiency and even created a yeast starter. There is, however, something we missed. Matt blames abnormally high fermentation temperatures due to summer heat. I think that may be part of it, but I wonder what else might have gone awry?

The Going Away IPA is still my favorite beer we brewed, it was so enjoyable and complex that we ended up drinking all of it the day we were able to being drinking it. We found a rogue bottle a month later and it still tasted great.

Anyway, more updates (with pictures!) to come as we improve and plan more beer.