Live data from Hacker News

What we've learned from building Ghost after 5 years and $3M

blog.ghost.org

161–170 of 182 posts

Re: What we've learned from building Ghost after 5 years and $3M

#161

Good morning HN! John from Ghost here - Thanks for all your support over the last 5 years. We wouldn't be here if it wasn't for that very first blog post hitting the #1 spot of HN and getting so much attention back in 2012. That was the very first time anyone ever heard about Ghost, and everything we've built since then has been thanks to that.

Would you please consider sharing more about working remotely? How are you dealing with its psycho-social challenges (the "human" challenges)?

Re: What we've learned from building Ghost after 5 years and $3M

#162

Earlier quoted context omitted.

Why not just close the issue and direct the person to stackoverflow, superuser, etc. if you think it falls into that category?

Then you get a reputation as a rude developer, whether or not that's fair or warranted.

You could create an issue template that explains the rules. If people still file support issues, you close those with a friendly reminder text (copy/paste) in which you explain the reasons why this is not the place for support. If people still think this is rude, they have personality issues which shouldn't be of your concern.

Re: What we've learned from building Ghost after 5 years and $3M

#163

Earlier quoted context omitted.

If you’re setup as a non-profit and you reinvest all profit, what do you do if you get to the point that you are making more profit than you can reasonably reinvest? Build up a large cash reserve?

Fantastic question. So the obvious answer is grow the company, right? That's pretty much what Amazon did for 20 years. Eschew profit in favour of reinvesting in building the company as big as possible. Not really our style, we'd rather keep the company small, but there's definitely still room to grow quite a lot from where we are now. Beyond that point, we can spend money on anything which reasonably furthers the mis…

How is the company governed? Have you considered becoming a worker cooperative and creating a democratic governance structure? Does the non-profit structure allow for that?

Re: What we've learned from building Ghost after 5 years and $3M

#164

Earlier quoted context omitted.

User docs are customer-facing, and therefore entirely fitting to be under marketing. Of course building the documents requires engineering contribution for technical details.

Yes, user docs are customer-facing, but the problem is that if they're under the control of marketing, then documentation priorities will be set as if they are marketing materials. And, possibly worse, a writer who works in marketing will by and large be treated by engineers like, well, somebody who works in marketing. (Without getting into sordid details, I'm speaking from personal experience of having been a tech w…

That's cool, but we literally don't have a marketing department. So whoever gets hired will report directly to me, no matter what their title is.

The primary function of the role is to do writing, not engineering - and the success of the role will be measured in terms of marketing, not engineering - so to me the title we went with makes the most sense. I can definitely understand the discussion here though :)

Re: What we've learned from building Ghost after 5 years and $3M

#166

All I got to say is that Hannah Wolfe is a beast (in a really good way!). Check out her number of commits compared to other contributors: https://chart.ly/github-dashboard/TryGhost/Ghost Keep up the good work guys!

Without trying to offend… what's the quality of those commits?

I have a co-worker who commits 6x more changes than me, everyday, but only because she commits many errors in the morning and have to fix them during the day after multiple code reviews. She often forgets to run the test suite before pushing her changes up. Even after the creation of a Git hook to pre-test the changes after every commit, she still manages to break things when they fall outside the scope of the automated tests.

The number of commits mean nothing if the quality is low.

Re: What we've learned from building Ghost after 5 years and $3M

#167

All I got to say is that Hannah Wolfe is a beast (in a really good way!). Check out her number of commits compared to other contributors: https://chart.ly/github-dashboard/TryGhost/Ghost Keep up the good work guys!

Without trying to offend… what's the quality of those commits? I have a co-worker who commits 6x more changes than me, everyday, but only because she commits many errors in the morning and have to fix them during the day after multiple code reviews. She often forgets to run the test suite before pushing her changes up. Even after the creation of a Git hook to pre-test the changes after every commit, she still manages…

Given that she's the CTO of the company, lead developer of the project, the most senior engineer on the team, literally one of the top JavaScript developers on all of Github - https://github.com/erisds... what do you think the answer to that question is? :)

Re: What we've learned from building Ghost after 5 years and $3M

#168

Earlier quoted context omitted.

How is the decision to use emberjs as the Admin interface panning out for you?

I'm probably biased as I work on the admin interface day-to-day but technology-wise it's been great. Upgrades are painless, typically requiring around an hour at most. If there are bigger framework changes we can usually upgrade immediately then clean up deprecations later as necessary but even then the work is normally minimal. When there are more stylistic changes that touch many files it's usually very quick work…

I'd wager almost everyone who has used ember in production feels much the same way. Ember is basically the best js framework for most use cases but React won the marketing war and has the backing of FB, so Ember just got crushed. It's sad because I love using Ember but the limitation on opportunities is a career killer. At this point it's embrace React or die. I see companies moving to React simply because they can't hire for Ember, not because React is better in any way.

Re: What we've learned from building Ghost after 5 years and $3M

#169

Good morning HN! John from Ghost here - Thanks for all your support over the last 5 years. We wouldn't be here if it wasn't for that very first blog post hitting the #1 spot of HN and getting so much attention back in 2012. That was the very first time anyone ever heard about Ghost, and everything we've built since then has been thanks to that.

Hi, I'm vaguely in the market for a new blogging platform, I went to ghost.org, hoping to get a sense for a sense of how it would feel to actually use ghost, but didn't find it easy to get that sense from the website. Do you perhaps have something like a test instance people can log into to try out, or a gallery of examples or somethng like that?

Re: What we've learned from building Ghost after 5 years and $3M

#170
post #106

I was on board from the beginning! What a great product. Too bad they dropped support for Postgres at some point, otherwise it would still be my platform of choice!

I’ve seen a couple comments about this issue, as well as it’s mention in the article. What about Postgres is appealing to the point that it is a deal breaker not to have? Is it familiarity or a specific aspect like scaling or ecosystem?

[deleted]
Post reply on HN