Yareev's schmonz.com

Every four years, I revisit my thinking about voting.

There was an Agile Coach Camp two years ago in Indianapolis — I could have been making crucial career-changing connections, then sleeping in my own bed!

I’ve been running a public web server since 1999, when my employer registered schmonz.com for me as a gag gift.

After a week and a half in Chicago, we’re home.

Lately I’ve been trying to learn C, starting with online training a month ago, and continuing with daily practice.

This week I ran a workshop.

Gesticulating At Path to Agility, I told stories of “Shoestring Agility in a Velcro Organization”.

Previously My coding workflow My podcasting workflow My writing workflow What I’ve been up to I’ve done very little writing lately.

Blur-o-Vision: Next-to-last story At Agile and Beyond, I told stories of “Shoestring Agility in a Velcro Organization”.

Saturday morning at PillarCon My employer — with offices in Columbus, Ann Arbor, and Des Moines and some consultants who don’t get to visit the offices very often — held its first ever internal conference, PillarCon.

Saying yes After effectively taking the winter off, I came back to work about a month ago.

Blur-o-Vision: Whole audience up and talking At the fourth AgileIndy conference, I led off the proceedings with Agile in 3 Minutes.

At the inaugural Agile Alliance Technical Conference, I got to meet and hang out with lots of people I’ve looked up to for a long time.

At the March meetup of AgileIndy, I facilitated “Behavior-Driven Development for Everyone”.

A month ago, when I shared some of what I’d accomplished during my time off, I promised to share the rest when I got back to work.

Schmonzcast #19: Three years ago, I attended my first big tech conference.

On the heels of last week’s post, I’ve created a very simple notification list for my upcoming and recent talks, podcasts, writings, and the occasional video.

After the first of my three weeks at this fitness retreat, I’m pleased with the outcomes: Since I’m working on strength, flexibility, and overall fitness, it’s no surprise my muscles (and possibly metabolism) are waking up.

When I was in college, I discovered that after two semesters of the kind of thinking that helped me complete my course assignments, I’d itch for the kind of thinking that helped me consult for clients.

As software developers, “technical lead” sounds like a role we’re supposed to want.

I envision my day job (software development coaching) being rather akin to parenting.

I’m finally coaching!

Scope of this article The 3 things almost every team does to meet deadlines that make things worse: 1.

I was to take six weeks off until a minor but very painful condition afflicted the plan’s back end: instead of returning from a fitness retreat, I’m recovering from (very minor and extremely helpful) surgery.

Schmonzcast #20: It was during last year’s Agile and Beyond lightning talks that I introduced my new micropodcast.

Back to our roots Last week I had the privilege of speaking at Agile Roots in South Jordan, Utah, a place hemmed in by mountain ranges to the east and west.

Last year at this time, I was nearing the long-awaited end of a longer-than-needed sabbatical during which I was angling to get hired as a coach.

Expertise is learning This recent tweet resonated with people: An expert is someone who keeps learning even when learning is harder to find.

For the first time since mid-May (and only the second time since the show started in April), there’s no Agile in 3 Minutes this week.

Processes and tools The folks who gave us the Agile Manifesto wrote “We have come to value individuals and interactions over processes and tools.”

Similar, but different Creating my podcast feels like debugging.

This week Monday morning, in my regularly scheduled stupid-early cab to the airport, I reflected on where I’ve come from (besides being home, in bed, asleep, like a normal person) and where I’m going: 6 years ago today, I came back to software development.

What you’re looking at here is a razor-thin allegory about incremental improvement — why it can be hard to start, and why once started it can be easy to continue — in the guise of a story about improvements to this website.

Update: I wound up keeping the old Textpattern site around, just in case, until November 2024.

A few weeks ago, while wandering through Muscatatuck National Wildlife Refuge with Haskell, I proposed to Bekki.

A year ago, with several aspects of my life in heavy ferment, many goals bubbled up and filtered through.

I’ll be presenting Bring Your Whole Self To Work (In 15 Years Or Less)!

The following idea popped into my head after discussions with some colleagues.

Do you write on your own site?

At Agile and Beyond a few months ago, I launched a new micropodcast: Agile in 3 Minutes, “the simplest podcast that could possibly work”.

When I started recovering from perfectionism, I noticed I’d been trying to carry around an “effectively infinite” set of thoughts to make sure to think.

The power of associative memory On Sundays, we’ve been taking the dog to one of the many forests of southern Indiana and going for a nice long walk.

Previously My coding workflow My podcasting workflow Now that it’s a weekly habit, when I set about writing one of these here blog posts, it’s not usually happening in the heat of a ranty moment.

Why a micropodcast?

I’ve always written a lot I’ve been writing on my website, on and off, for nearly half my life.

When I’m programming, I can usually sense when I’m off track, and have accumulated a bunch of tricks to direct my flow.

Julio Merino recently described his coding workflow and invited others to describe theirs.

I’m pretty sure my claims in How to develop software, How to develop humans, and How to efficiently learn a programming language hold true for people who aren’t me.

Get some stats I’m doing a weekly micropodcast.

I have a problem I’m a perfectionist.