sbellware

RubyGems and Namespacing

Here's what my Gemfile should be:

source 'https://rubygems.org'

source 'https://gem.fury.io/eventide' do
  gem 'eventide'
end

sbellware

CREATE EXTENSION IF NOT EXISTS pgcrypto WITH SCHEMA public;

-- ----------------------------
--  Table structure for events
-- ----------------------------
DROP TABLE IF EXISTS "public"."events";
CREATE TABLE "public"."events" (
  "id" uuid DEFAULT gen_random_uuid() NOT NULL,
  "type" varchar NOT NULL COLLATE "default",
  "stream" varchar NOT NULL COLLATE "default",

sbellware

{
  "title": "Event stream '$ce-sendFunds'",
  "id": "http://127.0.0.1:2113/streams/%24ce-sendFunds",
  "updated": "2016-04-13T23:27:54.854508Z",
  "streamId": "$ce-sendFunds",
  "author": {
    "name": "EventStore"
  },
  "headOfStream": true,
  "selfUrl": "http://127.0.0.1:2113/streams/%24ce-sendFunds",

sbellware

module Events
  class Recorded
    include EventStore::Messaging::Message
    include Lapse

    attribute :error_id
    attribute :time
    attribute :source
    attribute :hostname
    attribute :error

sbellware

rm -rf .

sbellware

To Geek or Not to Geek

We identify ourselves as geeks. We're language geeks, data geeks, process geeks, UI geeks… geek everything. It's our strength. It keeps us together. But is there a downside? Is it all good, or does geek also come with some disadvantages? This presentation explores the good, the bad, and the not-so-great of "geek". With a smattering of psychology and sociology thrown in for good measure, it summarizes twenty-five years of observation and self-observation of the software geek. And ultimately, it urges a more critical perspective and a re-consideration of our commiseration around the geek identity.

Bio

Scott Bellware is a relentless pursuer of root causes and an asker of inconvenient and untouchable questions. Scott is an avid student of the effect of software design on productivity, and the application of the Toyota Way (a.k.a. Lean) to software development. He has a track record of challenging entrenched ideas and of clarifying esoteric ones for a broader audience. Scott has been

sbellware

We identify ourselves as geeks. We're language geeks, data geeks, process geeks, UI geeks… geek everything. It's our strength. It keeps us together. But is there a downside? Is it all good, or does geek also come with some disadvantages? This presentation explores the good, the bad, and the not-so-great of "geek". With a smattering of psychology and sociology thrown in for good measure, it summarizes twenty-five years of observation and self-observation of the software geek. And ultimately, it urges a more critical perspective and a re-consideration of our commiseration around the geek identity.

Bio: Scott Bellware is a relentless pursuer of root causes and an asker of inconvenient and untouchable questions. Scott is an avid student of the effect of software design on productivity, and the application of the Toyota Way (a.k.a. Lean) to software development. He has a track record of challenging entrenched ideas and of clarifying esoteric ones for a broader audience. Scott has been up to his elbows in all aspe

sbellware

Keybase proof

I hereby claim:

• I am sbellware on github.
• I am sbellware (https://keybase.io/sbellware) on keybase.
• I have a public key whose fingerprint is 3DF7 B647 5749 825E E0E5 A810 32D0 B6DD F5B8 58FA

To claim this, I am signing this object:

sbellware

#!/usr/bin/env bash

projections=(
  "by_category"
  "by_event_type"
  "stream_by_category"
  "streams"
  "users"
)

sbellware

In Retrospect: ALT.NET and the Struggle for Identity in the .NET World

With ring-sde seats to one of the most colorful periods of .NET history, alt.net explorer Scott Bellware rewinds the clock to the early days of open source and agile development struggling to get a foothold in the Microsoft world. This retrospective walks the timeline from the days when the community was a loose conglomeration of developers scattered around the world who had never met face-to-face, to a tightly-knit weave of friendships and efforts that left a lasting impression on the .NET community as a whole, and on software development on the .NET platform. And while the last chapter of the story was perhaps more reminiscent of the Red Wedding episode of Game of Thrones, it's hard to deny the influence that alt.net and its people had. This is one participant's recount of those pivotal days, good, bad, and maybe even a little ugly.