IIRC they were random letters that do not occur naturally in English words, in order to serve as easily searchable annotation/footnote identifiers. He somewhat already knew they were extra details that would not make it to the main body. Later these get changed [1], [2], etc but you don't want to use these at the outset due to possible reordering/deleting.
Source: I was one of the founders of Stypi and we asked him when porting the data from Etherpad to Stypi.
In a lot of situations, no additional time is spent (and thus wasted). This happens with advisors in the general case too: they become an advisor and never meet again.
Probably because founders tend to have strong influence over a company and tend to have their share of personal fans and supporters among the userbase. So they try to avoid alienating them by pretending that they still get along.
Like when Carl Pei left OnePlus, we all knew it would go to shit once Oppo took over but they kept up the pretense for a while to protect the brand before they started undermining it.
For the 'advisor' there's probably a financial arrangement to this to keep them quiet and from shoveling up dirt in the media. It's hard to just give someone money like that so again a fake role comes in handy.
At Slab (https://slab.com), we believe that knowledge is the foundation of any organization's success. When a team's collective knowledge is more accessible, that team's potential is limitless.
Our product helps teams easily create, organize, and discover knowledge across the entire company, from non-technical to tech-savvy. Each day, thousands of customers rely on Slab across their entire workforces, including Asana, Benchling, and Fivetran.
You'd be joining a team of thoughtful and experienced engineers, distributed worldwide across North America, Europe, and Asia.
At Slab (https://slab.com), we believe that knowledge is the foundation of any organization's success. When a team's collective knowledge is more accessible, that team's potential is limitless.
Our product helps teams easily create, organize, and discover knowledge across the entire company, from non-technical to tech-savvy. Each day, thousands of customers rely on Slab across their entire workforces, including Asana, Benchling, and Fivetran.
You'd be joining a team of thoughtful and experienced engineers, distributed worldwide across North America, Europe, and Asia.
At first https://twitter.com/theryanking/status/1485784882173255680 seemed pretty damning but if you hover over the dates of the HN posts, the title attribute shows the timestamp, and it would appear Stripe's came in a couple hours before Bolt's. Add in Lyft and the "facts" around this story really seem to fall apart.
Yes, Lyft not being YC is is mostly it but also from an early Stripe employee [1]: "Lyft was also not originally on Stripe. They were on Braintree and switched over to Stripe after both Stripe and Balanced (another YC-funded payments company) competed for their business." Balanced was definitely a payments company also backed by YC. I cannot verify the switching from Braintree as I'm mostly an observer in all this but the other details are easily verifiable.
At Slab (https://slab.com), we believe that knowledge is the foundation of any organization's success. When a team's collective knowledge is more accessible, that team's potential is limitless.
Our product helps teams easily create, organize, and discover knowledge across the entire company, from non-technical to tech-savvy. Each day, thousands of customers rely on Slab across their entire workforces, including Asana, Benchling, and Fivetran.
You'd be joining a team of thoughtful and experienced engineers, distributed worldwide across North America, Europe, and Asia.
At Slab (https://slab.com), we believe that knowledge is the foundation of any organization's success. When a team's collective knowledge is more accessible, that team's potential is limitless.
Our product helps teams easily create, organize, and discover knowledge across the entire company, from non-technical to tech-savvy. Each day, thousands of customers rely on Slab across their entire workforces, including Asana, Benchling, and Fivetran.
You'd be joining a team of thoughtful and experienced engineers, distributed worldwide across North America, Europe, and Asia.
At Slab (https://slab.com), we're making the workplace a source of learning and purpose through knowledge-sharing. Our product helps teams easily create, organize, and discover knowledge across the entire company, from non-technical to tech-savvy. Our customers include Asana, Benchling, and Fivetran, who rely on Slab daily across their entire workforces.
You'd be joining a team of thoughtful and experienced engineers, currently distributed across North America, Europe, and Asia.
This post makes some salient points about the challenges of team knowledge sharing:
- Tree structure is too strict for cross departmental content ex sales to customer success handoff - should that be under sales or customer success?
- The right answer can be found in multiple tools - companies are not going to ditch Google Sheets / Excel for Notion tables
- A common source of truth needs to take into account the variability in skill - some users are going to be heavier users or more technical than others
- Collaboration needs to be as good as Google Docs or else people will just use Google Docs
It looks like the author is envisioning a new solution with Dokkument but if you want an existing one, take a look at https://slab.com. It’s designed to focus on team knowledge sharing while recognizing that it will be part of the productivity stack. For example, there is have a Content Map feature that shows a bird’s eye view of the entire information topology (with filters and drill down possible) and even mass reorganize from there. Integrations are first class with search retrieving results from other tools and rich linking that will preview external content. Knowledge sharing used to be an afterthought for a lot of teams but with the world going remote it’s exciting to see the innovation and prioritization pick up in this space.
Some friendly criticism. I was curious how slab topics work but could not find the details after a minute of trying to click and scroll around. The marketing bit about topics does not link anywhere. I finally made some progress by scrolling to the bottom, going to the support section, and searching for "topic". I had to scroll past results that described how to reorganize topics, assign permissions, until I arrived at the basics of topic usage. Even that did not provide an insight about how topics are different from regular tags, and I still am not sure what the difference is. So a "features" or "concepts" page would be nice, and even better if it was the main page. (I am an engineer.)
Normally I would not promote my own company to the HN community without contributing something of value, but from the looks of the UI decisions in the "juicy screenshots" I would venture to say we have already done so: https://share.slab.com/v1uy96K8
So if Confluence and internal knowledge sharing is problem for your team but you want to try out a ready and available product, please give https://slab.com a look.
Cheeky, but all is fair in business I guess. I had a look at every product I could possibly find (Notion, Confluence, Slab, Bear, CodeStoryApp, Evernote, Dropbox Paper, Google Docs, GitHub Wiki, Quip, Guru, Slite, Coda... listing them out makes me anxious) and made sure to incorporate what I thought were really smart product decisions. From Slab I really liked the table of contents and having the search bar up the top left, I can't say much more was included in Scribe that doesn't exist in every other product tackling this space though.
Source: I was one of the founders of Stypi and we asked him when porting the data from Etherpad to Stypi.
https://techcrunch.com/2011/08/09/yc-funded-stypi-is-etherpa...