Press "Enter" to skip to content

Posts published in “Startuppery”

[twenty twenty-four day thirty-nine]: space cadet crashes to earth

centaur 0

When you've got a lot to do, sometimes it's tempting to just "power through it" - for example, by extending a meeting time until all the agenda items are handled. But this is just another instance of what's called "hero programming" in the software world, and while sometimes it's necessary (say, the day of a launch) it isn't a sustainable long-term strategy, and will incur debts that you can't easily repay.

Case in point, for the Neurodiversiverse Anthology, my coeditor and I burned up our normally scheduled meeting discussing, um, scheduling with the broader Thinking Ink team, so we added a spot meeting to catch up. We finalized the author and artist contracts, we developed guidance for the acceptance and rejection letters, and did a whole bunch of other things. It felt very productive.

But, all in all, a one hour meeting became three and a half, and I ended up missing two scheduled meetings because of that. The meetings hadn't yet landed on the calendar - one because we were still discussing it via email, and the other because it was a standing meeting out of my control. But because our three and a half hour meeting extended over the time we were supposed to follow up and set the actual meeting time, we never set that time, and when I was playing catch up later that evening, I literally spaced on what day of the week it was, and didn't notice the other meeting had started until it was over.

All that's on me, of course - it's important to put stuff on the calendar as soon as possible, including standing meetings, even if the invite is only for you, and I have no-one else to blame for that broken link in the chain. And both I and my co-editor agreed to (and wanted to) keep "powering through it" so we didn't have to schedule a Saturday meeting. But, I wonder: did my co-editor also have cascading side effects due to this longer meeting? How was her schedule impacted by this?

Overall, this is an anthology, and book publishing has long and unexpectedly complex and tight schedules: if we don't push to get the editing done ASAP, we'll miss our August publishing window. But it's worth remembering that we need to be kind to ourselves and realistic about our capabilities, or we'll burn out and still miss our window.

That happened to me once in grad school - on what I recall was my first trip to the Bay Area, in fact. I hadn't gotten as much done on my previous internship, and started trying to "power through it" to get a lot done from the very first week, putting in super long hours. I started to burn out the very first weekend - I couldn't keep the pace. Nevertheless, I kept trying to push, and even took on new projects, like the first draft of the proposal for the Personal Pet (PEPE) robotic assistant project.

In one sense, that all worked out: my internship turned into a love of the Bay Area, where I lived for ~16 years of my life; the PEPE project led to another internship in Japan, to co-founding Enkia, to a job at Google, and ultimately to my new career in robotics.

But, in another sense, it didn't: I got RSI from a combination of typing every day for work, typing every night for the proposal, and blowing off steam from playing video games when done. I couldn't type for almost nine months, during the writing of my PhD thesis, which I could not stop at, and had to learn to write with my left hand. I was VERY lucky: I know some other people in grad school with permanent wrist damage.

"Powering through it" isn't sustainable, and while it can lead to short-term gains and open long-term doors, can lead to short-term gaffes and long-term (or even permanent) injuries. That's why it's super important to figure out how to succeed at what you're doing by working at a sustainable pace, so you can conserve your "powering through it" resources for the times when you're really in the clinch.

Because if you don't save your resources for when you need them, you can burn yourself out along the way, and still fail despite your hard work - perhaps walking away with a disability as a consolation prize.

-the Centaur

Pictured: Powering through taking a photograph doesn't work that well, does it?

[twenty twenty-four day eighteen]: something clever (un)evaporates

centaur 0

Don't you hate it when you think of something clever to say, but forget to write it down? I do. My wife and I were having a discussion and I came up with some very clever statement of the form "if people do this, they don't end up doing that", but now I can't remember it, so please enjoy this picture of a cat sending an email.

Just a moment. Just a moment.

"If you haven't climbed a mountain before, thinking about what you'll do when you get there is a distraction from starting the journey towards it. Climbing a mountain seems hard, but they're only a few miles high, and perhaps ten times that wide; most of your journey towards it will be on the plain, and that deceptively level terrain is the hardest part. Speculating about what parka to wear on the upper slopes does nothing to get you walking towards that slope; set out on your journey, and you can buy a parka when you're closer."

This bit of armchair wisdom was designed to encapsulate why it's better to start work on your business than it is to speculate on how to grow it into a multibillion-dollar conglomerate. Sure, it's great to have a grand vision, but you don't need to worry about mergers and acquisitions before you've found any customers - if you've never built a business before, that is.

If you are someone who has built many businesses, it's okay to build on your experience to guide your steps - but most of us have not, and our grand dreams can actively get in the way of figuring out how to make your product, how to get it in front of your customers, and how to make your product excel in their eyes so that they choose you over the alternatives.

Phew. Strangely enough, that first image was load-bearing: I picked a "random" recent picture for this blog, but it so turned out that our cat had been playing with his catnip laptop right around the time that Sandi and I had been discussing strategies for startups.

Feed your memory with enough cues, sometimes you get a retrieval.

Cogsci out.

-the Centaur

Pictured: Loki, sending emails on his catnip laptop, and resting on his laurels after a hard day at work.

[twenty twenty-four day seventeen]: we’re stronger with each other

centaur 0

No, this isn't a post about family, though it could easily be adapted to that topic. Nor is it a post about generic togetherness - that's why I said "each other" instead in the title. No, this is a post about how we're often stronger when we take advantage of the strengths of those around us.

Often at work we have our own perspective, and it can be easy to get caught up in making sure that our way is the way that's chosen, and our work is the work that is credited. But if we do, we may miss out on great suggestions from our coworkers, or on the opportunity to benefit from the work of others.

Just today at one of my contracting jobs, I had to present our work on the project so far. While most of the machine learning work on the project was mine, a lot of the foundational analysis on the data was done by one of my coworkers - and I called him out specifically when presenting his graphs.

Then, we came to the realization that collecting the amount of data we would ideally like to have to learn on would literally cost millions of dollars. I presented a few ways out of this dilemma - but then, one of our senior engineers spoke up, trying to brainstorm a simpler solution to the problem.

I'd been hoping that he would speak up - he had shown deep insight earlier in the project, and now, after a few minutes of brainstorming, he came up with a key idea which might enable us to use the software I've already written with the data we've already collected, saving us both time and money.

Afterwards, the coworker whose contributions I'd called out during the meeting hung on the call, trying to sketch out with me how to implement the ideas the senior engineer had contributed. Then, unprompted, he spent an hour or so sending me a sketch of an implementation and a few sample data files.

We got much farther working together and recognizing each others' contributions than we ever would have had we all been coming to the table just with what we brought on our own.

-the Centaur

Pictured: friends and family gathering over the holidays.

[seventy-eight] minus eighty-two: tl;dr: get to the point

centaur 0

tl;dr: get to the point in the first line in your emails, and also in the subject.

"TL;DR" is an acronym meaning "Too Long; Didn't Read" which is used to introduce a quick summary of a longer document - as I did in the first line of this email.

Often when writing an email we are working out our own thoughts of what should be communicated or should happen - which means that the important point usually comes at the end.

But people don't often read to the end. So it's important, when you get to the end of your email, to port the most important point up to the top (which I typically do with the TL;DR tag).

And, even better, if you can put it in the subject line, do that too.

Your email is more likely to work that way.

-the Centaur

Pictured: our wedding dragon lamp, sitting on a side table with our wedding DVD, which is sort of a coincidence; and a very cool light bulb.

Discussed: a topic I swear I've written about in this blog, but I cannot find via searching past posts.

[thirty] minus twenty: why i wouldn’t work for elon musk at twitter

centaur 0

Because he took Twitter private. Look, I'm not against private companies per se: I'm part of one (Thinking Ink Press) and have started another (Logical Robotics). And I'm not against Elon Musk per se either: I have some criticisms of how he's running Twitter, but those criticisms are not material to my point, and, hey, he has made me a great deal of money over the years as a Tesla and Twitter shareholder, so, perhaps he knows what he's doing in this case (though, based on how it's going, I seriously doubt it.)

No, my issue is, it's not a public company anymore. I strongly believe most large companies should be public, and that I would not work for a large private corporation if I could possibly help it. Private corporations exist to serve their shareholders; public corporations exist to serve the public. We structure them for the benefit of shareholders to encourage people to create companies and improve the economy, but going public places the company under increased oversight to ensure it is serving the public interest.

Public corporations place structure between the shareholders and the business: shareholders elect a board, which selects a CEO, who selects the employees of the company and directs its business. So at a public corporation, both the lowliest employee and the CEO work for the company, not the shareholders.

This insulation creates a great equalizer. In the end, everyone at the company, from the CEO to the mail room temp, are all responsible for serving the company. At a public company, you don't work for your manager; you both work for the company, and you both should act in its best interests.

At a private company, this is no longer the case. And at Twitter, this is definitely no longer the case. Elon Musk is removing security features and artificially boosting his own engagement and firing anyone who contradicts him, much less disagrees with him, which is a big problem since he doesn't realize he's incompetent at running software companies (this kind of nonsense is what got him fired from the company that became PayPal, after all) and he's desperate to cut costs and boost revenues before the debt payments eat them alive.

At a healthy company - a public company - you have the moral right to say, "No, sir, that doesn't work that way," or "No, ma'am, I won't do that; that's harmful to the company." Admittedly, this can get you fired, but you still have the moral right to do it.

At Twitter, however, it's Elon's show. And he has the right to run it the way that he wants - he certainly paid enough for it. So, if I worked at Twitter ... I think I would have to have taken the severance, if offered, because while I will work for a public company, I won't work in a feudal kingdom.

The King can boost his own tweets.

-the Centaur

Pictured: More graffiti, from an undisclosed location.