Six Software Products in One Year

Time and effort

The time is flying by.

I think I’m gaining a sense for what is achievable in a given period of time. My usual strategy is to think “I need this done TODAY” and then burn very hard to get it done. I get my payoff at the end of the day and am temporarily satisfied. I don’t really ‘get’ longer-term planning, though.

For the last few weeks I’ve been working hard and consistently. I haven’t been getting the big payoff at the end of the day, but I have been satisfied with my effort. I think that’s more important in the long term. It does make me anxious that things will never be completed, though, so I’ve spent a little time writing a plan for how I’m going to get to the next major milestone - someone giving me money for a product. My Plan for Profitability, although profitability comes a long way down the track.

I’ll probaby do The Plan in another post. It doesn’t help that I haven’t written it yet, despite claims to the contrary in the preceding paragraph.

Bluetooth sensors

I had a fun little coincidence when, within 24 hours, I received two separate enquiries for temperature logging devices. Then another one for a sound sensor. Then some accelerometers. And I want heart rate and altitude monitoring.

So one of the ’software products’ will be data logging/Bluetooth/alarming widgets. It’s within my capabilities as an electronics geek and provides a nice alternative to software (though there is a lot of software inside anyway).

I did have a half-hearted attempt at an electronics design/manufacturing business a few years back. I can confidently say that back then, I was a noob. In a few years, I’ll probably look back at this time and say that I’m a noob. I do that anyway. I’m always smarter in the future.

Anyhow, I’ve slapped together a basic Bluetooth temperature sensor. The technical challenges at this point are:

• Produce a smaller, cheaper, more battery-friendly design.
• Work out how to provide more accurate temperature measurements. Sensor calibration is not a business that I want to get into.
• Design an API for people to write software for the thing.
• Work out if there are going to be any regulatory hurdles that I’ll have to jump through - EMI/EMC emissions, RoHS regulations, export controls and so on. Software is a lot easier - any chump can ship dangerous software anytime.

It’s fun. It is a lot more capital-intensive than software, but there’s a much greater variety of activities. And being able to hold a device in your hand and say, “I created this” is satisfying on a much deeper level than software.

More and more marketing

After my initial marketing binge at the start of the year, I haven’t done much (apart from this blog). I need to get on top of it again. It helps me work out where my efforts are best spent, and I need to get some consulting work happening. Not really need, I guess, but I’d feel a lot better if I didn’t have to dip into my savings to pay my bills.

I’ve been writing content for various websites, but I have a much lower tolerance for that than coding. I can manage six solid hours/day of coding. I can manage maybe one or two for writing marketing copy. Electronics design I can do more or less indefinitely, but it’s far less demanding than either of the two (most of the time is spent interfacing with the tools rather than mentally designing things. I still use pen and paper for most of it).

Planner

One of my initial ideas (on the right) was for a hierarchical todo list thing. I wrote a prototype that satisfied my needs and then lost interest. Most of the features that I had determined other people wanted were completely uninteresting to me. Plus, the concept was more or less stolen from AbstractSpoon’s ToDoList, so I felt a little bad about trying to charge money for his ideas.

So I’ve been using this hacked-together Python-and-wx-and-sqlite thingo for a year or so, now, and it suits my needs beautifully. I’m sure it will suit somebody else’s needs, so rather than try to commercialize it, I’m going to stick the code up somewhere and let you lot Have At It.

Eventually, anyway. Releasing free software is not on The Plan, so it will most likely get ignored for a while.

There’s a lot of stuff on my plate right now. Everything is progressing reasonably well:

• Client A is still causing trouble, but they appear satisfied for now.
• The Mutex Labs website design is looking very good. I’ve also started writing content for it, so that should be up in the next couple of weeks.
• I’ve started narrowing my focus for consulting work. I’m going to start out focusing on embedded C coding, particularly the Gumstix platform. I’ve been writing a list of things that I’m good at and would like to work with, so that should lead nicely to a list of capabilities for consulting work.
• I’ve also been trawling local job sites to see what is going. There’s a surprisingly large amount of work available. The old pains of dealing with recruiter ads is showing - “must have xyz in the SDLC”, “must have 93 years of experience in brand new tech Y”, “must be an expert at buttering bread”. Stupid stuff like that. I’m trying a different tack this time and seeing if I can more or less bypass the ad and get people excited about the package that I bring, rather than just checking boxes on the ad. It’s going to be interesting to see if I can convince employers to let me work independently from my office rather than being a short-term full-time contractor.
• Something that is working quite well for me is looking on freelancer sites like Elance and getting in contact with the people with work available. I’m generally not able to compete with overseas programmers, price-wise, but I can offer things like business relationships or I-build-it-you-license-it-from-me type of deals. That’s fine for me - I love building things and I want to work on my product portfolio. I have two hardware projects on the burner and a very interesting third in discussion.
• I’ve even been working on SyncDroid! I’m in the middle of some really hairy multi-threading-uncertain-relationships code, but it’s coming along slowly. I think that once that’s out of the way I can start using it on a day-to-day basis. At some point I have to do a bunch of UI coding, but I’m avoiding that for now.

Something that I’m going to have to watch is not taking on too much at once. I love the feeling of a new project, but I fall down when it comes to actually completing them.

I’ve noticed that money appearing in my bank account improves my motivation quite a bit. This is probably the main factor that is encouraging me to look for work at all - just that nice reassurance every couple of weeks. I don’t need the money right now. I just need to know that if I want to, I can earn some cash. Conversely, big projects like SyncDroid are difficult for me to stay focused on because I don’t see any immediate payoff and won’t for a while.

I’ve been thinking about my current work situation a lot.

For the last month or so, my workload has been primarily Client A and MicroISV work to fill the gaps. Client A is getting very sloppy about paying invoices, typically running a week or two overdue. I need to forcibly remind them and usually resubmit the same invoice multiple times. They are a high-stress client, change their mind a lot and have frequent emergencies. Two years ago when I started with them they were paying what seemed like a lot of money. In that time I’ve taken a pay cut, suffered from high inflation and significantly improved my skill set, so I’m not being paid very well either.

So I think the time has come to let them go.

Of course, this is the ‘take the leap’ problem all over again. Do I try to make it on my own, or do I stick with a stable (ish) thing?

This time, I’m going to take a different approach. Rather than try to make it purely on the MicroISV, I’m also going to cultivate some consulting work. I’m eager for the human interaction, and seeing payments go into my account is a big motivator. I don’t need to be earning a lot overall, but I do want to keep my hourly rate at a fairly good level. What constitutes ‘good’ may shift with time, but I’m still comfortable for a few years even if I don’t earn anything.

Along the way, I should pick up some interesting contacts and ideas. Not that I’m short on ideas already - the challenge is in completing them before getting distracted by the next shiny new thing.

I’ll be without predictable income for the first time since I started working (seven years). I should take a proper holiday. It’ll be the first one since I started working, too.

I think this is the right direction for me to head in. And, as always, the worst that can happen is that I have to get a job.

Ah, how time makes fools of us all. From Jan 22:

I’m at a point in development where I can finally say I understand how the whole application is going to fit together. It’s very reassuring - there was always this uncertainty as to how the different modules were going to connect (in particular, how asynchronous events were going to move around.) Now that I have a model I’m happy with, it’s just a matter of ‘colouring in’ what’s left.

I’ve just returned to the SyncDroid code after a few months off and I have that “holy crap, what was I thinking?” feeling. The small-scale implementation is fine, but the object model sucks. I can’t figure out what should be talking to what. Comments that I’ve left in the code indicate that I did have a plan, but when the journaller code is making merge decisions and the merge code is storing data on the disk, it’s a sign that something has gone wrong.

So I’m refactoring it all. Again.

I have a new plan which looks suspiciously like the old one. I think the difference is that this time I have a better idea of how data flows through the system. I’m finding SyncDroid to be very difficult, conceptually - there are multiple threads and multiple priorities and databases coming and going all of the time. Alan G. Carter of The Programmers’ Stone speaks of the importance of juxtaposition in programming. This project has juxtaposition up the wazoo. There’s enough that I can’t hold it all in my head at once (yet) and so I’m struggling.

Perhaps it reflects the elementary difficulty of what I’m trying to do. Perhaps that’s why no-one has done it before. I’ve certainly never struggled so much to hold a mechanism in my head before, and in past lives I’ve programmed 64-way machines, massively parallel dynamic hardware, and then both in the same system.

Anyway. It’s coming along, slowly. The other thing that I’m noticing with Python is that the amount of behaviour you pack into a given volume of code is very high. My major contract client has me coding predominantly in C, so it’s quite jarring at times. It’s not a bad thing, but I often wonder how much more difficult this would be in C. I don’t worry so much about memory management - I’ve got that pretty well down - but more things like standard libraries and unexpected crashes. The nasty thing about C is that it’s so brittle - a single misused pointer will crash your entire program. Python won’t let you make that sort of mistake, and if you do anyway, it handles the mistakes far more elegantly.

I’ve also finished some C security work lately and have come to the conclusion that if you want to write secure software, don’t do it in C. In fact, let’s generalize that. Don’t ever use C. That’ll be the right choice most of the time. If someone asks you to code in C++, run for the hills. Or at least make sure you’re invoicing by the hour.

Maybe it’s time for a holiday. My 26th birthday is coming up soon and I feel very old.

I’ve been doing contract work instead of MicroISV work.

Not that that’s necessarily a bad thing. Getting paid is nice. It’s just not precisely the direction I want to go in. It’s still a good direction. If I managed to build a self-sustaining consulting/custom dev firm, then that would be a great outcome. That’s just not where I intend to go right now. It involves a lot more capital and a lot more risk and as far as my financial goals go, it’s unnecessarily grand.

There have been some small developments on the business admin side of things. I’ve got a company name now - Mutex Labs. I’m vetting a number of graphic designers to do logos and websites. I’ll be talking to an accountant soon to work out how best to structure my affairs (large tax bills are already a problem). I continue to read and study and gather ideas for the marketing side of things. There have been more good product ideas.

I guess everything is just coming along nicely. My contracting time is heavily booked until about halfway through April, and that’s assuming nothing new comes along in the meantime. Taking a holiday is sounding very appealing right now!

I bought a Kinesis Advantage keyboard with the intention of reducing my finger pain associated with typing. Obviously, I spend a good portion of every day typing, and my livelihood basically depends on my being able to continue typing.

I also decided to learn the Dvorak layout while I was learning the Kinesis keyboard. I tried learning Dvorak a few years back but gave it up because I was working with a lot of other people’s keyboards as well - it was too inconvenient to keep switching layouts.

On the Kinesis/Dvorak learning process

• Muscle memory is a huge factor in switching to a different keyboard or layout. Even now, when I’m typing on my laptop I instinctively reach for the Enter key with my right thumb, because that’s where it is on the Kinesis.
• The Kinesis makes a lot of bad habits difficult, whether by accident or by design. You can’t really rest your hands on the pads while typing because then you can’t reach all of the keys. You can’t twist your hands around to move them around the layout because the keys are aligned to suit your hands in the home position. When you move your hands around the layout, suddenly they’re un-aligned and awkward.
• I started out using a lot of ‘mental CPU’ time to handle the conversion. In the beginning, it took all of my concentration just to hit the right keys - I had to separate my thinking from my typing.
• While learning Dvorak, I noticed an interesting progression; I started out pressing just single keys at a time. Gradually, I started combining strings of keys into single motions (something I call ‘chording’, which I’ll come back to). This is similar to how a child learns to read - they recognize single letters, expand out to sounds and eventually can string together words.
• I made rapid progress for about three weeks. The first few days were difficult. I only used the Kinesis+Dvorak for a couple of hours each day because it was very frustrating to learn. I’ve had 20 years with a nice solid brain-keyboard link via the keyboard, and suddenly it’s horribly slow and error-prone. After the first few days things settled down a bit and I could manage an entire day’s work on the Kinesis.
• After the first three weeks, progress slowed. I was still improving, but more in the areas of chording and accuracy. Some keys still gave me consistent problems on the Dvorak layout, particularly G and P.
• You need to sit a little higher than with a normal keyboard. This is a problem for me - I already find standard office chairs too short (even the Aeron!). When time allows, I’ll be buying a nicer chair and getting the gas-lift swapped for a taller one.
• Why the A and S keys - two of the most common characters in English text - are on my two weakest fingers, I’ll never know. The pinkies get more of a workout than usual because they’re handling all of the keys on the edge of the keyboard, too. Placing these two common letters on already weak and overutilized fingers is probably the biggest flaw in the Dvorak keyboard that I’ve found.
• Dvorak is lovely for English text. It’s just a great feeling to feel the letters whiz by with so little effort. However, a lot of my typing load is not English text. It’s Linux terminal navigation, C and Python source code, all of which intentionally discard vowels in exchange for brevity. This makes Dvorak’s plan to alternate hands work very poorly - you’re just not typing anything on the left hand.
• Some common Unix commands are absolutely worst-case scenarios on Dvorak. Take the command ‘ls -l’, which I would type dozens of times per day. On Dvorak, L, S and hyphen are all on the right pinkie. If you’re using a standard keyboard, so is the Enter key. It’s really, really unpleasant to type ‘correctly’.
• Naturally, position-based key bindings don’t work: Vim’s HJKL, WASD for games, Ctrl-Z/X/C/V for word processing.

I really tried to make Dvorak work. I gave it a month. At the end of the month, I switched back to QWERTY. It’s a fantastic layout for cranking out lots of English text, but that’s not my use case.

On the Kinesis keyboard

• The up and down arrows are backwards compared with the Vim convention. That’s relatively easy to remap on the keyboard.
• The macros are rather buggy. Actually, scratch that. The keyboard’s firmware is rubbish. I suspect that either the authors had never programmed on a microcontroller before or were not trained as programmers to begin with. I can crash the keyboard in two fairly common scenarios. That said, the crap firmware is not a reason to not buy the keyboard. It’s perfectly usable despite its flaws.
• I opened it up to look inside. It’s pretty typical of small-scale electronics manufacturing: no surface-mount parts, revisions hot-glued to the case, off-the-shelf components. It’s not badly made - it feels very solid for its weight - but it does have a few rough edges which might surprise you if you’re expecting a mass-produced product.
• It’s ripe for hacking. The main controller is an Atmel AT89S series microcontroller. The macro RAM is on standard serial EEPROMs. There’s even a socket for a second one (the Advantage Pro upgrade). Apparently the firmware can be changed over the PS2 or USB port, but Kinesis didn’t seem to willing to send it to me when I mentioned I wanted to modify it.

Where to from here?

I still want to improve the keyboard layout. The Kinesis makes typing less painful, but some of my pains appear to be linked to the QWERTY layout. And the feeling of effortlessly flying through English text with Dvorak was just amazing.

To come up with a better keyboard layout, I want to log my keystrokes for a month. Each keystroke will be tagged with the time and the active process. The process lets me figure out whether the keystroke intent was a letter or a position. I can also detect errors by tracking Backspace presses. With that information, I can determine exactly which keystrokes or combinations are the most common for me.

In addition, I want a ‘trainer’ - a program that will prompt me with an arbitrary series of keystrokes and time how long it takes me to hit them. This will give me information on how strong and fast my fingers are and if any of them are particularly error-prone. From that, I can generate a map of the keyboard, each key associated with a ‘performance’ score. Combining the two datasets, I can then come up with an ideal keymap for me, given my typical usage patterns and my own brain-keyboard performance data.

I’d also like to integrate information on common digraphs, but I’m not sure how best to use them. I’m not sure that Dvorak’s assertion that alternating hands is the best thing to do. A common case for me is the ‘chording’ I mentioned previously, where a single hand can hit a sequence of keys very rapidly. The timing is simpler - I arrange my hand correctly on the keys, then use the individual fingers to press them in sequence. Of course, this sounds like the sort of thing that might cause tendon damage. But it’s fast.

There’s more discussion on chording and performance here.

Development progress

I’d say I’m about 30% of the way to a SyncDroid release. It’s frighteningly small, but I know that boring stuff like testing, installers, licensing, graphics and documentation is going to eat up a lot of time.

I keep detailed lists for this stuff. Some people say it’s obsessive-compulsive; I say it’s damned well essential because there is just so much to do. If I don’t write it down, I’ll keep worrying about it until it’s done, and that’s a huge energy sink.

I’m at a point in development where I can finally say I understand how the whole application is going to fit together. It’s very reassuring - there was always this uncertainty as to how the different modules were going to connect (in particular, how asynchronous events were going to move around.) Now that I have a model I’m happy with, it’s just a matter of ‘colouring in’ what’s left.

Typing

I’ve had some level of hand pain for probably a decade. It’s mostly been quite ignorable and always went away after a few days. I blame it on the 1996-1999 period where I trained on Quake variants for anything up to 8 hours per day instead of studying.

Lately, though, it’s been getting worse. Much of this is that I’m doing a lot more typing now that I’m not rotting away in meetings. Short-term, I did an eleven-hour-long adrenaline-fueled hack-fest (on client work, no less). I didn’t type much for the following two days due to the pain. After some encouragement from my officemates, I bought a Kinesis keyboard.

I’ve seen them before, but ignored them due to the high price. Now, with the low US dollar, my improved financial situation, increased frequency of pain and likely expense of surgery, it seems like a bargain. I’m learning Dvorak on it too. It’s intensely frustrating to not be able to bang out 100+WPM without thinking about it, but so far I’m seeing major reductions in pain. I see daily improvements in speed and accuracy, so I’ll almost certainly stick it out.

Logos and icons

I can imagine what I want in graphics, but can’t express it (in words or images). I need some icons for SyncDroid and some logos for the website(s), so I went to a <$40 logo design place.

Lesson 1. If you say you want the logo to look like something, they’ll give you exactly that, copyright law be damned.

Lesson 2. If you let them pick a colour scheme, they’ll pick something ugly.

Lesson 3. If you specify colours, they’ll use them in the most ugly way possible.

Lesson 4. If you specify “simple, no detail”, they’ll add superfluous detail that would suck even if you had the resolution to display it correctly.

I’ve got ‘unlimited revisions’, but that doesn’t mean anything if they can’t design anything that looks good. So I walked a few doors down to an art supplies store, had a nice chat with the hottie at the counter, and bought a nice soft clutch pencil. I’ve sketched out some designs that don’t completely suck. I did have a quick go at implementing them in Inkscape but lost patience quickly.

I’ve looked at a lot of icon sets on the web and can see a pretty strong correlation between price and quality. Damnit.

Tuba

There’s a guy outside playing Mario Brothers and Star Wars tunes on the street corner. Newtown is by far the most fun location that I’ve ever worked in.

I’m here! I’m alive!

I’ve been doing a lot of client work lately, more because people want work done rather than because I want money.

Since the last update, I’ve made great progress on SyncDroid. After thinking about this thread on the Business of Software forum, I’ve decided to split SyncDroid into several different, smaller products - one for USB drives, one for network sync, one for SaaS Internet backup, and so on. It also helps me to focus - I’m working on a smaller product with a more clearly defined feature set rather than this great big ‘do everything’ product. And it helps me to focus the marketing message and differentiate (people like specific things that fit them well rather than generic things that happen to fit them). So I’m very happy with my decision to split into a whole product line.

UI work continues. I’ve got the scope of the project worked out and can finally say that I understand the project rather that just focusing on little bits of it. I can also confidently say this is where my product fits in the world and this is why you should pay money for SyncDroid instead of Unison. It’s a nice feeling. Very confidence-inspiring.
I’m amazed at how far off my original effort estimation was. I wrote most of the sync engine and figured I was about halfway. Now I can say that the sync engine was maybe 2% of the total effort required. UI’s are hard. Marketing is time-consuming. I haven’t started doing any serious cross-platform work yet, either - I’m doing a Linux release first.

I’ve been thinking about the different platforms a bit, too. My feelings are that:

• Linux is easy and fun to develop for and you’ll get good feedback, but nobody will actually buy your stuff
• Windows has a huge user base, but they’re relatively clueless
• OSX has a fairly intelligent user base and they’re trained to expect to pay for good software, but there’s just not that many of them

OSX has the additional problem that in order to develop for it, you have to buy a Mac. This becomes a simple economic problem: if I spend AUD$850 on a Mac Mini and $2000 worth of labour on an OSX version, will I sell enough Mac licenses to make the money back?

After spending years looking at everything through purely economic terms, I now believe that a decision based on such terms is an oversimplification. If I was going for (legal) profit maximization, my strategy would be:

• Go to my contract clients, start billing a lot of hours, and use my position as sole developer/provider to leverage a large $/hour rate increase
• Move back into my parent’s place
• Stop spending money on things like petrol and coffee

The economic decision-making model ignores the fact that my life would suck if I followed it through to its logical conclusion. I would be miserable. Starting this MicroISV has been one of my best decisions in recent memory just because of the quality-of-life improvements that it’s made. I’m not making anywhere near as much money, but I’m a lot happier. And so, I can confidently say things like I will keep doing this even if I’m just breaking even. I can happily forfeit a large income and go for a riskier, cheaper existence, because my life is that much more enjoyable.

And so, Buying A Mac. I’m going to wait. I’m going to get a Linux and a Windows release out there, gather some feedback, measure the size of the response. If nobody is interested in SyncDroid, I’m better off cutting my losses immediately.

I was going to end the post there, but it’s such a down note. Running a MicroISV rocks. Hard. Down with The Man!

Here’s a quick list of MicroISV’s that I know of in Sydney. I know there are lots that I’ve missed. Email me if I’ve forgotten you!

(I’m considering a bootstrapped software company of four people or less to be a MicroISV).

• tiinker by Deep Grey Labs: an intelligent news aggregator that uses datamining techniques to find the best stories for you
• pulse by zutubi: a really slick continuous integration system

Honourable mentions to people who gave it a try and are getting back up to try again:

• Lachlan Gemmell
• Ian Sorbello

Oddly enough, I can name a whole lot more Brisbane micro-ISV’s, despite having only spent three days there.

Another day, another status update.

I’m getting a lot done. What’s amazing me is the sheer volume of work that needs to be completed. I feel like I could keep someone busy just writing material and investigating sales opportunities and gathering requirements and so on.

Yesterday and today, I:

• Bought domains for my filesystem and file synchronizer.
• Set up WordPress on integrifs.com and syncdroid.com.
• Came up with something to share a single WordPress installation between multiple sites. Instead of WordPress-MU (which assumes you’re hosting all sites under the same domain) I put a switch statement in index.php to change database names based on the hostname in use. This is a whole lot easier, especially when the time comes to upgrade WordPress.
• Wrote a bunch of marketing material for IntegriFS: overview, how it works, download and a few drafts.
• Cranked out a dozen pages that I have to write for SyncDroid. I’m just putting the titles into WordPress right now and leaving the pages themselves as drafts, so I can log in whenever and wherever and fill them in.
• Ditto for IntegriFS. There’s a lot of writing to do.
• Set up some Google AdWords for SyncDroid. There’s still a lot more work to be done there.
• Finally found a use for all of those random news aggregators: finding potential customers! I’ve been tracking interesting discussions and gathering a lot of useful information.
• Made some good progress on a WordPress theme that I’ll share across all of my sites. Each site will have its own colour scheme to differentiate it.
• Explored a bunch of competitors to SyncDroid. Without exception, they look complicated. They have fancy conflict resolution screens. Complexity is what I want to avoid with SyncDroid. I want it to be as automatic as possible. I want to put in an Undo feature so that if it does make a mistake, you can back it out anyway.
• Importantly, got a lot of the IntegriFS design and strategy out of my head and onto paper. This is the crux of Getting Things Done: get it out of your head. For the last week or so I’ve been buzzing with ideas and thoughts, and my mind is finally clear to look at other things that are important in the short(er) term. I need to get some bigger pieces of paper, because at the moment it looks something like this:

Note that I’ve written no code at all in the last two days. This would have surprised me a week ago. Right now, my focus is to get a bit of attention from people. This should help me work out what sort of demand there is, whether my marketing efforts are working and hopefully even get a bit of feedback from potential users. If it turns out that I’m on the wrong track or there’s no interest at all, I won’t waste time writing code.

There are a few different directions I could push in for SyncDroid. The base technology - detecting, logging and propagating file changes - is useful to several applications. The first ones that come to mind are:

• Automated real-time backups
• Synchronization via USB drives
• Time Machine (snapshotting and rewinding a filesystem)

I wanted to implement all of these, but at this stage I’m focusing on laptop-desktop synchronization. With the new office, however, my own use case has changed. I’m synchronizing over the Internet using Unison, but if I need to move any large amounts of data around that’ll need to go over a USB drive. Hence, using a USB drive as the go-between becomes attractive. Another nifty idea relating to this is to use a mobile phone (connected via Bluetooth) instead of a USB drive.

The Time Machine opportunity is interesting. It’s a very early market with few competitors. There are no compelling implementations for Windows, yet. I have no doubt that there will be an effective free one in time. With the base technology already in place, though, it’s not a big technical challenge to toss another UI over the top. There’s still a huge marketing effort to do, but I’m getting better at that all the time.