Okay, let me tell you about this whole “kim seib” thing I tried out a while back. It wasn’t some big official project, more like a personal experiment, you know? I kept hearing the name pop up in different places, some folks online, a mention in a meetup maybe. Sounded interesting, or at least different, so I thought, why not give it a whirl?
Getting Started with It
So, I decided to try and apply this “kim seib” idea to how I was organizing my side projects. Nothing too critical, just my own stuff, less risk that way. First thing I did was try to find some basic steps. It wasn’t super clear, honestly. Lots of talk, but finding a simple ‘do this, then do that’ guide was tough.
I ended up just grabbing the core ideas I could piece together. Seemed like it involved breaking things down differently, maybe focusing more on certain types of feedback early on. I started by restructuring my usual to-do list and planning notes based on what I thought “kim seib” was about. Felt a bit awkward at first, like wearing shoes on the wrong feet.
The Actual Process – Bumps and All
The initial phase was… messy. I spent more time trying to figure out if I was doing “kim seib” right than actually doing the work. It felt kind of abstract. I’d set up my tasks one way, then look at them and think, “Is this it? Is this the ‘kim seib’ way?”
Here’s what I tried specifically:
- Changing how I documented progress. Instead of just listing completed tasks, I tried writing short narratives about the ‘why’ behind each step.
- Shifting focus. I deliberately tried to prioritize tasks that seemed less defined, based on some “kim seib” principle I vaguely understood about exploration.
- Getting feedback differently. Instead of waiting for big milestones, I showed super raw, unfinished bits to a friend who’s also a coder.
Some parts were okay. The feedback thing wasn’t bad, actually. Getting eyes on rough stuff early stopped me from going too far down a wrong path once or twice. But the documentation part? Man, that felt like extra work for little gain. Just writing stories about code felt… fluffy.
And trying to organize tasks based on fuzzy concepts? Sometimes it worked, sparking an idea. Other times, I just felt lost, like I didn’t have a solid plan. It wasn’t as straightforward as my old way: list tasks, do tasks, check off tasks. This “kim seib” approach felt more like wandering around hoping you’d bump into the right path.
Where I Landed
So, did I stick with “kim seib”? Not really, not the whole thing anyway. It wasn’t a magic bullet. Parts of it felt forced, like trying to fit a square peg in a round hole for my workflow. It demanded a certain mindset that didn’t always click with getting things done efficiently.
But it wasn’t a total waste of time. That idea about early, raw feedback? I kept that. It’s useful. It made me realize I was often too precious about showing unfinished work. Sometimes you just need someone to tell you you’re heading towards a cliff before you spend weeks walking that way.
It also reminded me that sometimes trying these named methods or frameworks isn’t about adopting them wholesale. It’s like going to a buffet. You don’t have to eat everything. You pick the bits that look good, try them, and maybe add a couple of things to your regular plate. The rest, you just leave behind.
Honestly, this whole experiment felt a bit like that time I tried switching keyboard layouts. Sounded great in theory, supposed to be more efficient. In practice? Weeks of frustration, typing like molasses, only to eventually go back to what I knew, maybe keeping one or two new shortcut habits. You try things, you learn things, you move on. That’s just how it goes, right?
