In one of my previous entries, I mentioned that I have a hard time getting better than proficient at something:

one of my bigger shortcomings -- at least in my eyes ( and if you think there are other, bigger ones, please keep it to yourself, thank you very much) -- is my lack of digging deeper and really getting to know how to work with, and learn what it is I'm tinkering with. So lately I've been trying to focus on just one Digital Audio Workstation (DAW). I've been working with Bitwig, because it's still fairly new (v3.0.3 as of this writing), and somewhere down the road I'd like to be someone other people turn to to learn this software. Then I can brag about how I've been using Bitwig since v1.0. I even have the badge to prove it. A bit childish and maybe narcissistic, sure... but it's the small things.

Like any piece of creative software, whether it be Affinity's Photo or Designer, Scrivener, or Ableton Live (Bitwig's main competitor in the DAW field), they're all easy enough to do something basic up front, but the real power comes from digging deeper, and learning the ins-and-outs of the software. And of course, the more one digs, the more complicated the software can become. Bitwig is no different, so I've been trying to break it down into smaller bits, making the knowledge easier to digest. The smaller bits also help with trying to keep focus, an issue I'm constantly struggling with.

I'm not, however, taking a very practical approach. It would make sense to start at a high level, learning the basic interface to an expert level. I know the basics well enough to feel comfortable working through the project.

continue >>
// work

It's gotten busy at work.

I mean... BUSY.

For a few months there I didn't have much to do. Mostly bug fixes here and there. And then we had a new project start and I was given the Bootstrap/UI duties for that team. And then a second project spun up, and it was decided I could be a "shared resource", and I was given the Bootstrap/UI duties for that project.

And then third project came about.

And a fourth.

Currently, I am on five scrum teams. Yes. Five. Now, I don't always have work or bugs for all teams at any given time, but there are days when I'm heads down for a solid 8-10 hours.

It shouldn't (hopefully) be for long. If it is, I'll burn out. Thankfully I have a good scrum master who's always checking my point totals and making sure I'm not going batshit crazy. Two sprints ago I was given a total of 13 points. A full sprint's effort is typically 8. That was a crazy week.

But hey, at least I'm not bored.