3 ms·
Why is this not on a corporate blog? It makes no sense to me post this sort of stuff on GitHub. Are they that broke they can't afford to host a static site on s
by that_guy_iain 4y ago
Why is this not on a corporate blog? It makes no sense to me post this sort of stuff on GitHub. Are they that broke they can't afford to host a static site on s3?
Edit: Nevermind, I see why. So people star their GitHub repo. People go there and oh that sounds interesting. Give a GitHub star. Then they use that as social proof which they do in the post. Smart idea.
- 99failures 4y agoThey expect the blog to survive the company.
- that_guy_iain 4y agoI may be wrong here, but I'm pretty sure they're not saying they're shutting down and are not in the process of shutting down. They are pivoting. And are in the process of the pivot. If they think that blog will survive long than the company then really it doesn't make any sense for them to keep all their marketing efforts up. Which this is clearly a part of. And it really does not make sense for them to publish that they're shutting up shop in the same post as they're talking about signing 5 companies to support deals.
- l-lousy 4y agoPutting “here’s how we changed on a previous product” doesn’t really need to be on a small corporate site. It being a sort of investigation fits better on GitHub where fewer people will accidentally stumble across it from their current product.
- that_guy_iain 4y agoThere is a whole lot of bigging up their current product. That blog post is part of their marketing campaign. And the entire point of it is so people will get to their product. Also: * it's mixed up with all their other marketing material for this product. * it's in their current product's repository It's more likely people will stumble across it when looking at their product. As I said in my edit. The reason for it being on their GitHub is to increase the likihood of GitHub stars which they use as social proof.