HNHacker News
TopNewBestAskShowJobs

keithwhor

3,884 karma · joined March 14, 2013

hacker. canadian in sf. oss = <3. learning to be a CEO, one mistake at a time.

building Superuser, come join :)

https://superuser.app

https://x.com/keithwhor

submissionscomments
keithwhor··on Show HN: Autocode – Automatically generate API code for SaaS apps
Do you mind sharing a screenshot and your Chrome version?
keithwhor··on Show HN: Autocode – Automatically generate API code for SaaS apps
Thank you so much!

I will say it hasn’t been a small effort. We’ve been working on the suite of products that have led up to Autocode for years. At this point I’ve personally done hundreds of 1 - 2h sessions with customers to figure out what works and what doesn’t, and I think that has sort of enabled us to focus on the features that matter and why they’re important.

As you play around, I’d be interested to learn what you like and what you think is missing!

keithwhor··on Show HN: Autocode – Automatically generate API code for SaaS apps
That’s great feedback, thank you! We’ll definitely see if we can test across a few different password managers / signup experiences to make sure it’s a smoother process.
keithwhor··on Show HN: Autocode – Automatically generate API code for SaaS apps
It's just JavaScript. It's absolutely portable. The APIs that run atop us use the Standard Library registry, you can think of it like a package manager / proxy of sorts. But if all you're doing is writing logic to connect things, you could conceivably host it on your own after you prototype with us -- you'll just lose some of the goodies we provide like automatic webhook signing.

Also, our gateway / schema specification is open source and portable as well:

https://github.com/FunctionScript/FunctionScript

keithwhor··on Show HN: Autocode – Automatically generate API code for SaaS apps
Hey all,

Keith here, founder and CEO of Standard Library (we made this <3). The problem we're focused on solving is simply -- building modern integration software is too difficult. (1) For professional engineers, it's mundane work nobody wants to do and (2) for non-developers, best-in-class integration tools that rely on visual workflows just don't cut sophisticated use cases for modern businesses, they often need some code.

Autocode solves these problems by providing an IDE that professional engineers can use to ship simple integrations in minutes and new (or "low code") devs can use to automatically generate API integration code without needing to know much to start with. We provide a ton of features: an API registry, API autocomplete, code generation, serverless hosting for your APIs, an in-browser execution engine for your workflows, observability + logging, complete revision history. It's kinda like Heroku and Zapier had a really, really ambitious child.

We've been at this, somewhat quietly, for four years and Autocode is what we're the most proud of to date. We've been very fortunate to have the opportunity to work with some of the best companies in the industry to support our vision -- Slack and Stripe have been investors since (nearly) day one. That said, we're a small team -- just five people -- and we still have a hell of a lot of work ahead of us. We would love thoughts and feedback!

YouTube video here for anybody that wants to see the full demo:

https://www.youtube.com/watch?v=ha3C0X3Vyi0

Thanks so much! :)

keithwhor··on Startup Ideas 2020
Not to be too cheeky, but this is mostly a list of trends dictated by companies started three or more years ago.

Meaning it's actually "VC Compatible Startup Ideas 2017."

Outside of Developer Tools (I'm a fan!) I would say your advice -- it's feasible to start a company outside of these ideas -- is probably exactly where you want to be looking if you're starting a company today. Daniel's an investor, so he's casting a net for startups / founding teams he hasn't heard of yet. Content marketing is dealflow 101. That said, if you're a founder in one of these spaces, he has a fantastic reputation, so you should absolutely reach out. He wouldn't have posted it if he wasn't looking for awesome people!

keithwhor··on Startup Ideas 2020
I think monetization is difficult IFF you don’t think about asking for money from the get-go. I’m actually of the opinion that open source projects are not well-equipped to build companies around, but can serve as an early guide to nascent market demand.

Monetization looks difficult because people keep building free things and then trying to figure out how to charge for them. From my perspective, the better bet is to build a free thing, prove the market, and then figure out what the paid thing might look like — even if totally different.

I think there’s a decade ahead of us where developers can start asking, “how can I turn this {useful tool} into a SaaS product?” We've been seeing this for years, I just think folks can start getting more ambitious about it. :)

keithwhor··on Startup Ideas 2020
Everybody in this specific social group of investors continues to list Developer Tools as, effectively, an Evergreen space.

What’s baffling to me is that the amount of innovation in Developer Tool businesses (not tools, businesses) is surprisingly small. There are three factors that influence this, IMO:

(1) The OSS community has trended towards an insular culture incentivized by OSS popularity where stars and Twitter followers are status signals. In this world, it’s hard for talented engineers to stop seeking “star status” and transition to the business ecosystem where they’re bottom rung of the ladder.

(2) The space is extremely sophisticated — with longer R&D cycles — and VCs routinely incentivize suboptimal growth trajectories when they’ve identified apparent winners and miss opportunities with more practically iterative companies. (Expecting growth at all costs in a space where continuous delivery + R&D is the norm.) This blows up some companies early and prematurely kills other promising technologies. I think the 18mo expected cycle time probably needs to be adjusted for these companies, especially early stage.

(3) Founders are heavily pressured towards exits. Long R&D cycle time, the pressure cooker of VC growth expectations, and the rarity of high-ownership, customer-oriented developer tool + engineering talent makes early exits extremely attractive for both founding teams and acquirers.

How do we fix this? Between Daniel, Elad and a bunch of folks who keep writing this stuff — I think it’s time for a new developer-oriented fund, backed by the people and companies passionate about the space.

I’ve been a major sponsor of Vue.js for years. I’d like to do more to help talented developers start businesses in the future, when possible. If anybody thinks something like this is interesting, give me a holler.

keithwhor··on How Shopify implemented its secure authentication service
Pretty sure Stripe is a Ruby shop as well.
keithwhor··on Visa Buys Plaid
That's interesting... 200M accounts on Plaid.

You gotta figure that's near the top of the S-Curve, right? Very close to 100% of the TAM in the US, and I would imagine that global expansion is costly given banking regulations in different regions. Visa already has the reputation / relationships to push forward there.

Congrats to the team!

keithwhor··on People Who Are Obsessed with Success and Prestige
Food for thought: People live as they live, and can have great thoughts, insights and advice without adhering to your interpretation of their words or actions.
keithwhor··on Downsides to working at a tech giant
Thanks for the feedback. This thread has me thinking about a blog post. I don’t write as much as I’d like to because I feel as though I’m still testing my worldview / hypotheses, and I don’t like delivering half-assed products. :)
keithwhor··on Downsides to working at a tech giant
The poster I replied to here created a straw man argument based on my lack of response to another comment. I didn’t think that was fair considering my bandwidth limitations, so I decided it would be best to set expectations. My response to the “math changing” comment has now been added above.

Do not assume that the lack of response of somebody else implies anything aside from the fact that they didn’t respond. They could agree, disagree, or maybe they haven’t even read or thought about it yet — and maybe they never will because something else distracts them.

I think discussions tend to be the most productive if we assume everybody has the best intentions. :)

keithwhor··on Downsides to working at a tech giant
I appreciate the kind words, but trust me, I still have a lot to learn. The most important contributor to our early success so far has been the team, who have supported me in my growth as a founder as much, if not moreso, than I’ve supported them.

Yes — being employee 50 changes the scales a little. You’re a little too far removed from the executive team to have the same level of comfort. We’re still significantly smaller than that, but at my first job I was in the same # range as an employee.

While I didn’t get to build a relationship with the executive team, my boss at the time kept in touch and ended up introducing me to my best friend / confidant in the Toronto ecosystem as a result. So I would still say the network was valuable. :)

keithwhor··on Downsides to working at a tech giant
Yes — some execution is hidden, for sure. I, personally, try to be ultra transparent with the team: here’s our bank account, here are deals in-flight, here are the VCs and founders we’re talking to.

The value I aim to provide anybody that works with us is all the things I felt I was missing when I was a startup employee. I wanted to understand how deals happen, what personalities are like, how things work. As we grow I can’t share entirely as much — a piece of minor bad news can hit me pretty hard emotionally and it’s not fair to subject the team to me being upset or a hothead over something that will blow over — but I do try to encourage folks to learn as much as they can.

Even if somebody were to be entirely disinterested in founder-level execution, early employees have a super easy, instant warm introduction to any investor on that company’s cap table downstream. You might not be using that aspect of your startup career yet, but it certainly can help you if you wanted to use it.

keithwhor··on Downsides to working at a tech giant
I don’t disagree with the spirit of your post. Large tech companies are paying ridiculous salaries and generally speaking we’re in a period of early-stage capital glut.

The point you’ve made — that it makes more sense to just start a company — is directionally correct, but for the most part is a logical fallacy. I hear this from competent, capable people all the time, “I might as well just start my own company rather than work at a startup as an employee.”

The reality is that 0 to 1 is an extremely, extremely difficult hump to overcome and most people intuitively know this. Which is why anybody who says, “I’m better off starting my own company than working at a startup,” especially without startup experience, is likely to never actually do that thing. I’ve never actually seen it, though I’ve seen a number of people go from working at to founding startups.

The real insight here is that it is actually more valuable to found — or be a really early employee at — a successful startup. And so the question becomes: how do you put yourself on track to get a $72k check from Peter Thiel at 23? Take risks, prove your competence and grow your network. That means work at startups.

Sure. I’m (currently) a lucky recipient of survivorship bias. There’s a long way to go and my current state is incomparable to most of the people we look up to and respect as a community. But the key word there is, “survivor.” If you look at the start of my startup career — middling ad tech company in Toronto, eng. lead at a failed Series A SF startup, short stint at a biotech company, turned down by BigCos — none of it looks like it could possibly have been leading anywhere. I just used those opportunities to meet really talented folks who believed in me and, one by one, would end up supporting me down the line. I’m lucky and very grateful for that. Some of the aspects of my journey to date are non-repeatable, and I’ll always give thanks for those moments — but a lot of the lessons I’ve learned can apply to any ambitious young technologist.

Keep at it. If startups aren’t for you, fine, but, again — survivorship bias requires you to survive in the face of insurmountable odds. And it does happen. Startups teach you how to survive. It’s OLN on steroids for careers.

keithwhor··on Downsides to working at a tech giant
The reason I haven’t responded to the math changing is because it’s Christmastime and I’m spending time with family. Some of the responses to my post require a much more thoughtful answer than I can muster while at the gym between meeting family members.

Be patient. I’ll respond to the other post if you wait.

keithwhor··on Downsides to working at a tech giant
You’re making this (single startup) v. (single S&P company). That’s not how it works. Prove yourself at being an adept generalist and you’ll, over time, create access to the most ambitious people and companies.
keithwhor··on Downsides to working at a tech giant
The pessimism in this thread really bothers me. I’ve read anecdotes on entrepreneurship being on the decline, but it pains me to read so many negative takes on startups. We’re actively training our young people to avoid taking risks, and it’s going to fuck us — especially if some of those young people have the ambition be early employees at, say, a startup that takes on climate change in a big way.

Look — the fact that Garry knew Peter Thiel when he was 23 is nuts. When I was 23 I was broke and living with my parents in the suburbs outside Toronto. I didn’t even personally know any other software engineers. I think many people here would relate more similarly to that position.

Just because he won the social lottery early, doesn’t mean his lessons are wrong. I got a junior engineering job in Toronto when I was 23, at a startup, making less than Garry. $57.5k CAD. I worked on my open source portfolio and next took a job in another startup in SF for $120k USD the next year.

That startup failed. I took a brief job at a biotech startup after being turned down by Google and Facebook (twice). After three months I quit that startup to run the company I’m still running today, four years later. Today, we’re very fortunate to work with some of the largest companies in SV.

Reflecting on this: I think a better story Garry could’ve told is not that he missed out on $200M, but that startups basically built his network so that — years later — he’d be a prominent VC working with Alexis Ohanian, funding the next round of exciting companies. $200M is an eye-catching clickbait headline, but not the real substance. The real substance is — how the fuck did he meet Peter Thiel at 23, and how can somebody recreate that?

In the story I just told about myself, I got really lucky as a function of working at startups. I didn’t really make any money doing it. But a whole bunch of interesting things happened:

- The first job in SF I worked at introduced me to a product manager who went to school with Aston Motes, employee #1 at Dropbox who would eventually be an investor in the company I run today.

- The founder of that first failed company introduced me to AngelPad, the accelerator that gave me my first $50k in financing. The fact I stuck it out as an engineering lead at a failing startup helped: I gave it my all. (Aside: YC turned me down. Twice.)

- The biotech company I worked at was founded by two early SpaceX employees, one who would also become an investor later on.

Don’t work at startups to make $200M. Work at startups because you’ll work with people who have risk profiles that are much more likely to generate outsized returns as a group. You’ll have the opportunity to join or create a community of high-performing folks that, in aggregate, outperform anything you can do on your own. Maybe you’ll be the CEO one day, maybe not, but no matter what you are very likely to come out ahead if you apply yourself.

And don’t let the comments here dissuade you. Startups are hard, but they kick ass. I’ve cried myself to sleep some nights — as both an employee and CEO — and still wouldn’t change the experience for anything. I’m a better person because of what I’ve been through.

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
That’s fair! From my perspective that’s something that’s building trust with the SaaS provider. We’ve all heard, “ugh! This API is so shitty!” before — I’m fascinated by what tools and products can be built to prevent developers from feeling these pains.

Thanks for the feedback. Can definitely see that changelogs are really underinvested in across the industry, and it’s useful to have people mention how valuable they are.

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
I think you misunderstand where I’m coming from with my line of questioning.

I’m asking questions because we provide tools that standardize the API development experience. Semver is trustable if the tools create the contract instead of the developer that decides to build the API. We deliver the tools that create the contract.

In this sense, APIs built and delivered atop our platform don’t need to “encourage best practice,” best practice is — or at least can be — hardcoded in with no potential for footguns.

Your concerns about semver are well-founded. I’m asking questions because I’m pondering aloud if we can fix them and change semver — with respect to APIs — from a social contract to a coded contract, and include tools necessary to inform end-users of API changes. :)

Does that make more sense?

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
Do you think it’s possible to achieve the same sort of system by just using semver + release candidates?

For example, 5.x.x is currently stable, so you release 6.0.0-rc1 (2, 3, ...)?

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
I don’t disagree with your assessment on semver as it currently exists for, say, NPM packages.

I do think that with web APIs specifically, the surface area is a lot smaller — the HTTP interface is literally all you touch — so semver, in its purest form, is actually completely enforceable as long as you understand the API schema.

Our team has talked a lot about either hard-enforcing or automatically applying semver where applicable. My question to you is — does this sound reasonable, and if you knew a semver contract was actually bound to implementation (i.e. guaranteed and not implied), would you trust it more?

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
Good points.

Do you think a combination of the two is possible, and how do you think that might work?

year.month.minor.patch?

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
Would a tool that easily shows you documentation / schema changes between API versions be useful to you, or create more trust with a SaaS provider if they offered it?
keithwhor··on How Shopify Manages API Versioning and Breaking Changes
What specifically about SaaS API constraints do you think makes a date-based approach more appealing than semver?

My high-level feeling is that it’s just way more difficult to ship a SaaS API than a Ruby Gem, so adding semver to that is just another layer of API management everybody has to agree on. Do you agree with this assessment?

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
I think it’s the implied stability, especially for long-standing APIs. S3’s API is 2006-03-01 — meaning there haven’t been breaking changes in over 13 years. This creates a psychological contract with developers that nothing’s changing anytime soon.

The trade off is that AWS has some godawful APIs (DynamoDB has the least intuitive API I have ever worked with). But they’re stable.

If you go with a date-based approach and create a process + contract whereby you guarantee API stability and / or deprecation date, the developer always knows exactly how much time they have before an upgrade.

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
How often do you feel like you find / consume changelogs when you’re looking at APIs? I feel like they’re either non-existent or non-obvious for most SaaS companies.

Do you feel like you’d trust a company’s API more if you could peruse the API changelog more easily?

keithwhor··on How Shopify Manages API Versioning and Breaking Changes
Hi everyone. As the founder of an API company, this article has me wondering about the semantics of versioning — so I thought I’d ask the community a question. I hope the Shopify API team doesn’t mind!

When you all think about API versioning, what makes the most sense to you — a semver approach (major.minor.patch) a la NPM, or a date-based approach (2020-01-07) a la AWS? Or is some combination of the two desirable?

At Standard Library [0] we both allow people to publish APIs but also publish API proxies on behalf of partners (Stripe, Slack + others) using a semver approach. It’s not perfect but theoretically enforceable (schema parameter additions can be forced to require a minor update, schema parameter removals can be forced to require a major update). We’ve just stuck to this semver approach based on intuition and haven’t had negative feedback about it, but I do like the idea of time-based versioning.

Would love thoughts! If you want to play around you can build your own APIs using https://code.stdlib.com/, which uses the FunctionScript specification [1] to enforce HTTP request schemas.

[0] https://stdlib.com/

[1] https://github.com/FunctionScript/FunctionScript

keithwhor··on The town's so full of these confounded dials (195 BCE)
I love this. I remember reading an anecdote of Gates discussing his relationship with Buffet — there may be a video interview — where Gates was astounded at how empty Buffet’s calendar was.

As a founder, I’m more of a Buffet. I schedule time when and where necessary (which is, admittedly, most of my time most weeks) but I hate feeling as if I’m restricted to obeying numbers in a database in order to function.

It fills me with an inordinate amount of joy to imagine the simplicity of a world in which you’d only return home to eat. I think that’s how I operated as a kid in the summers, riding bikes and walking around town with friends until we needed to eat. I feel like those moments are underrated and very visceral, instinctual parts of the human experience.

Wild how only a few lines of prose from people that existed thousands of years before us can evoke these sorts of feelings.

[Edit] Apparently, this anecdote is very famous and very Google-able:

https://www.cnbc.com/2018/09/07/warren-buffett-taught-bill-g...

← PreviousPage 8 of 20Next →