Hurricane Dorian forecast contest

Due to a technical error with the forecast submission script. the contest is cancled. I’m not sure I want to invest any more time in fixing this old and busted script, and I have yet to make good on my ten years of “I will rewrite it this winter”, so this may be the end of tropical forecast contests on Funnel Fiasco.

It’s that time of year again! Submit your forecast for mainland landfall by 0000 UTC on 29 August (8pm ET on Wednesday).

Is venture capital hurting the tech industry?

Maybe.

So many of the ethical lapses in the tech industry (think Facebook or Uber) seem to be driven, in part, by the need to grow as rapidly as possible. From where does that need come? At least part of it comes from the venture capitalists (VCs) who provide the early funding for those companies.

VC firms work by throwing a little money at a lot of companies, and throwing more money at the companies that are doing well, in the hopes that they go public or get acquired. Then the VC firms get big ol’ paydays. The nature of business is that most companies fail, so in order to keep going, the VC firms need the successes to be really big successes. Grow as fast as you can, profit and ethics be damned, until someone buys you for oodles of money.

To make themselves attractive to venture capital firms, fledgling companies will sometimes go for the flashy new technology. They’ll think about how they can disrupt industries with blockchain-based crypto-cloud-crowd-AI-machine-learning whatever-whatever-whatever. Everything has to scale exponentially. Throw in all sorts of sensors and have the device do local inference. Even if all they need is to put a stick-shaker on a steering wheel.

But this growth comes at a cost. Scaling a company culture is hard. Scaling it as fast as you can spin up a new AWS region is impossible. Free-flowing capital allows companies to build out quickly, but quickly isn’t always the same as well. Having restricted capital available is a constraint that can help a company make focused and deliberate decisions.

I’ve been thinking about this a lot recently. Not just because of my experience at a local pitch night, but because it’s just past the two year anniversary of Microsoft acquiring Cycle Computing. Jason and Rachel Stowe founded Cycle Computing in 2005 on their credit card. Apart from a debt round in 2016 (if I remember correctly), the company existed for 12 years on revenue.

It wasn’t always easy. There were times when I took a far-too-early flight because it would save the company fifty dollars. We had to be careful with our expenses and we couldn’t hire as fast as we wanted. But when we did spend money, it was because we thought it was the best thing for the company’s success, not just because it was there to spend. But that also meant that when the big payday came, the employees got a nice windfall — there were no VCs to pay off first.

Companies, particularly software and consulting companies that don’t need much equipment, can succeed in low-capital mode unlike anything we’ve known in the past. You don’t need office space because your employees can work remotely. You don’t need data centers because you can run on cloud services. Pay your employees and give them laptops, and then you’re off to the races. Capital infusion can help, but often it can make it worse. If you’re in business to run a successful business (as opposed to making big money), then maybe venture capital is not the answer for you.

As an industry — and a species — we’ve grown to love big, flashy numbers. But it’s important not to mistake valuation for value.

Business cards at conferences

Paper is dead; everything is digital.

Are you done laughing? Good! Stephanie Hurlburt posted a lengthy set of thoughts on using business cards at conferences, and it inspired me to think about how I use business cards.

I happen to be at a conference right now, and I brought my box of business cards with me. I’m sure I’ll only hand out a few, if any, but I prefer having them to not having them. If someone wants my card, I should have one available for them.

When I worked in marketing, I really liked getting business cards from prospective customers and partners. It made following up after the conference much easier. Sure, we had those nifty badge scanners, but some people covered their codes to protect from sneaky scans or they used a throwaway email address to avoid spam. But even if the scan worked, typing useful notes into the scanner is a tedious process. It’s much easier to pull out my pen and jot a few notes on the back of their card.

Now that I don’t work in marketing, the above scenario isn’t as important. But it’s easy to be insulated against the scenario arising.

What about digital methods? Sending someone an email or LinkedIn connection as you stand there works: unless it doesn’t. Conference WiFi can be unreliable, and mobile networks aren’t always great inside a large metal and concrete building. Taking pictures of business cards works, but it’s still harder to take quick notes, even with the stylus on my phone. I have a QR code that is a link to my LinkedIn profile saved on my phone. I have literally never used it.

Conferences are hard places to make connections. You’re busy and you meet so many other people that by the time you get home your brain is mush. For me, business cards are an easy way to preserve data. And sometimes they’re useful for winning a free lunch at a local restaurant.

Is it really open source if…?

I see this question asked (or stated as an accusation) with some regularity: “is it really open source if ___?” Fill in the blank with whatever. For example:

This conversation started with a criticism of GitHub restricting Iranian users in order to comply with US law. Like true Scotsmen, we all have a notion in our heads of what open source means, and the picture doesn’t always align from person to person.

Part of the problem is that there are two separate parts: the output and the input. The output is the legal part. The part that deals with licensing. That’s easy to deal with. Software is open source if it is presented under a license that meets the Open Source Initiative’s definition. Easy.

The hard part is that open source also has a cultural component to it. This is the input. There’s a community involved in the project. That’s often what people think of when they consider “open source”, but it also has no real definition. So we argue about it. A lot.

Is it really open source if you don’t allow it to be used by Iranians? No. That violates number 5 in the Open Source Definition. Is it really open source if you don’t allow Iranians to be in your community? Yes. Does that make it right? Well, that’s the real question we should be asking.

Other writing: July 2019

Stuff I wrote

Red Hat/Fedora

Lafayette Eats

  • El Maguey — A delicious Mexican restaurant in no hurry to get you to leave.

Stuff I curated

Red Hat/Fedora

Does open source benefit independent developers?

Patrick’s heresy is not an unreasonable statement. My current employer grew to a $34 billion market value using, creating, and supporting open source software. But there are plenty of stories of open source developers working on key projects that are barely able to sustain themselves.

Benefits of use

It’s clear that independent software developers benefit from using open source software. If nothing else, the programming languages themselves are immensely beneficial. Much of the tooling, frameworks, and libraries used for developing applications these days are available for free under open source licenses. The economic barrier to entry would be much higher if everything had to be paid for.

Benefits of development

This is where the answer becomes more qualified. Contributing to open source projects can open the door to being hired at one of the businesses that make good money. But that’s not attractive to everyone. And an “everything should be free” mindset can make it hard to earn money.

It comes down to what you want to get out of it. If you’re doing it to make money, then it might not be beneficial, unless it’s a boost to your resume. But for some people, contributing to open source projects is a hobby they enjoy. I got started out of a sense of giving back to the community that provided me with a free operating system. The fact that it eventually became a paying job is a nice benefit.

Harm of not contributing

The flip side of the question is “does not contributing to open source harm indie developers?” The answer is “yes” far too often. A lot of development positions explicitly or implicitly expect your GitHub profile to be a key part of your resume. But not everyone has the privilege to be able to contribute to open source projects in their spare time. Hopefully that understanding spreads more broadly through the industry.

Switching from consumer Gmail to G Suite

Last spring, I was having some trouble with my email. I had my @funnelfiasco.com email forwarding to the Gmail account I’d been using since 2005 or so. But for some reason, every so often email would silently just not make it through. This nearly cost me the opportunity to be the technical reviewer for The Linux Philosophy for SysAdmins (affiliate link). There was no real indication of what was going on, and since my friend graciously hosts my site for free, I didn’t want to push too hard. So I decided I’d just be Google’s customer instead of their product.

Here’s the kicker: Google doesn’t let you just become a paying user. So I created a G Suite account for FunnelFiasco, a “company” of one person. But this also meant that I couldn’t just magically promote my existing account. Instead, I had to migrate all of the data. This turned out to be mostly easy, but a bit of a pain in some regards.

Migrating

Chrome

Moving Chrome data to a G Suite account is very easy: you log out and log in with the new account. The main thing to remember is to not deleting the existing data when you log in with the new account. It’s that simple. If you have any payment methods stored, those are in Google Play, not in Chrome.

Voice

Moving Google Voice is less easy. You can’t import your history into the new account, which killed a lot of the value for me (that was part of the reason I decided to port my Google Voice number to my mobile carrier). You can export it and keep it locally, but that’s not entirely helpful. But once I made peace with that, I was able to transfer it to my G Suite account. However, the Google Voice support site says that’s not an option these days.

Contacts

It’s as simple as exporting from the old account and importing to the new. It took a little while for my imported contacts to show up, which led me to think the import failed. So I tried again. And then I had all of my contacts twice. So I deleted them all and imported again. This time I was patient, and it was fine. But if you switch the main Google account on your Android phone, you may be surprised when an edit to a contact doesn’t appear to be reflected on your phone (it’s still showing the old account’s version, too).

Mail

G Suite provides a data migration service for importing email. This worked very well, but very slowly. One of the benefits of Gmail, especially in the early days, was the bountiful storage space. Combined with usable search, it meant not having to delete email. So I had something like 383,000 emails in my account. This took about 10 weeks for the data migration service to import. There are probably faster ways to do this, but I didn’t really care. If I needed an old message, I could log in to the old account.

The data migration service does not move mail filters. Those can be exported as an XML document and reimported to the new account.

Calendar

I apparently didn’t take notes on this at the time, but I think what I did here was to add my G Suite account as a fully-privileged user for my consumer calendar. I had them both displayed and as I saw things that were owned by the old account, I moved them to the new calendar. Most of my calendar events are on the shared family calendar anyway, so making my new account an owner there was essentially no different.

Docs/Drive

As with the calendar, I had to add my new account as owner to the documents I still cared about. It’s an annoyingly manual process.

Other services

I didn’t have much data — if any — in other services (YouTube, etc), so I didn’t worry about that.

Life with two Google Accounts

In the end, I’m sort of stuck with having two Google Accounts. Most people don’t email me directly at my @gmail account because I’ve been using @funnelfiasco.com for so long. But the account still exists and I go check it every so often to make sure I’m not missing anything. The few people who use Hangouts Chat still mostly IM me at the funnelfiasco account, but occasionally they’ll slip up and use the gmail account.

G Suite is overkill for my needs, but it’s the only way Google will take my money. At some point, I’d like to extricate myself from Google to some degree. I know it’s possible, and I know many of the people who might read this post would strongly advocate it. But it’s also very convenient to use Google, and I’m aware of the trade-offs I’m making. I’m not interested in having that conversation.

I cry at work

The new podcast “This is Uncomfortable” had an episode about crying in the workplace. I don’t have a lot to say about it, other than it’s a good story. But I wanted to go on record as saying that I cry at work.

Sometimes work is overwhelming. Sometimes my personal life leaves me on edge. Sometimes I read a moving article.

Sometimes I cry. It’s okay to feel things.

Adding more isn’t always better

Earlier this year, I attended a pitch night at my local coworking space. One of the teams that presented is working on a product to help prevent driving while drowsy. It’s a noble goal — drowsy driving can be as dangerous as drunk driving. Like drunk driving, people aren’t very good at self-evaluating their fitness to drive when they’re sleepy.

But as they talked, I sat there going “no. What are you doing?” They talked about learning who the driver is and establishing a baseline of their attentiveness to measure their drowsiness. All kinds of cool whiz-bang stuff. And maybe someday they’ll add some haptic feedback to the steering wheel.

I suggested that they target diabetics as a first market. Hypoglycemia is dangerous, too, and it’s an easily-defined audience, which helps in initial go-to-market efforts. When I talked to them after their presentation, they started talking about maybe adding blood sugar sensors.

No. Just no. I asked them if they’d considered what storing data might mean. It creates a liability for the driver in case of an accident. It could be used by insurance companies to change rates. It could be compromised and used for something else.

Using the latest tech is neat, but only when it makes sense. And sometimes, the more you add, the worse things get.

If you want a diverse community, you have to stand up for marginalized members

On Monday, The Perl Conference’s Standards of Conduct Committee published an incident report. In a talk at the conference, a speaker deadnamed and misgendered a member of the community. As a result, they took down the YouTube video of that talk.

The speaker in question happens to be a keynote speaker at PerlCon. The PerlCon organizers wrote a pretty awful post (that they have since edited) that essentially dismissed the concerns of the transgender members of the Perl community. They went on to mock the pain that deadnaming causes.

I did not think to save their post in the Wayback Machine before they edited it down to a brief and meaningless statement. “We are preparing a great conference and do not want to break the festival and trash our year-long hard work we did for preparing the confernece, the program and the entertainment program.”

What they don’t say is “we value the marginalized members of our community.” And they make that very clear. Editing out the insulting part of their post does not ,mean much, as VM Brasseur pointed out.

If you value an inclusive community, you have to stand up for the marginalized members when they are excluded. If you don’t, you make it very clear that you’re only giving lip service to the idea. As it is, the PerlCon organizers don’t even apologize. They’re more concerned about the bad publicity than the bad effect on the community.