Top products from r/beta

We found 5 product mentions on r/beta. We ranked the 4 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/beta:

u/Kaitaan · 3 pointsr/beta

I'm going to try to unpack this one point at a time. I'm going to preface this with the statement that all of the below is "to my understanding", and "as best I can recall". I'm not going to keep hedging all the below statements; I'll hedge once for this entire post unless stated otherwise below. A lot of what I am putting below is stuff I've either picked up over the years, or read in this book (or found on wikipedia while writing this post)

>Reddit was supposed to be a non-profit too,

I don't think this is the case. Steve and Alexis are probably the only people who can say for certain what their goals were. To my understanding, they approached Paul Graham with a completely different idea, which got rejected from the first class of YCombinator. They were well liked by a couple of the YC folks though, despite their idea, and were told to come up with a new idea and then pitched Reddit. Now, I don't know Paul so maybe I'm off base here, but I doubt that YC gave Reddit a space (in exchange for, iirc, 10%) to create a non-profit.

>Until the founder with that vision got assed out by a couple of multimillionaire VCs with dollar signs in their eyes

Paul Graham (the "multimillion dollar VC") was involved in Reddit before Aaron was. Aaron got introduced to Reddit at YC, after Paul had already invested.

>Anything you'd like to know about archive.org, you can ask them

You're making claims about their budget (though since they're a non-profit, this is probably public info somewhere), their hardware, staff, and bandwidth; you have to back up your claims, not me.

>their engineering staff would be fully capable of creating a platform like Reddit in a matter of days, on their existing hardware,

That claim is just shenanigans. I'm going to skip over this. Short of them actually doing it, there's no way to validate this claim.

>Not counting the bloat that exists solely to milk as much profit as possible

Ah, of course. Not counting all the parts of the business that are meant to actually pay for the business to run.

>They are engineers who have worked throughout the valley tech industry, like myself, helping to create sites much bigger than reddit

Sure. Sites like Youtube, Amazon, Snap, Facebook. All much bigger than Reddit (depending on whose numbers you look at, of course). All sites with a much larger staff than Reddit has.

>I don't have much insight into reddit anymore, even though I knew the aforementioned founder

Aaron left Reddit in 2007. That's 12 years ago. Any insight you had then, was of a vastly different company. Hell, the Reddit of 5 years ago was vastly different than it is today.

>Nobody has any insight into reddit anymore

I may not know as much about the company as maybe the executives, but I like to think I have a pretty good idea what's going on there.

>I do know that they burned through about 500 million dollars this year

No you don't. You know Reddit raised money. You don't know how much of that has been spent, how much of it has been invested, how much of it is left, or how much of it is sitting in a box under my mattress, for that matter.

>and they pay their programmers better

How much does Wikimedia pay? According to glassdoor, pay is a fair bit higher at Reddit.

u/ShesSoInky · 1 pointr/beta

I think you're lost.

But while we're here I am going to recommend you read Bright-Sided so you can get a better, more well rounded idea of how the world works and what makes things happen and gets goals achieved. Spoiler alert: the whole "positive thinking" thing isn't it!

u/depraved_desires · 2 pointsr/beta

> but from what I remember during my time at the company the frontend was pretty rough. The work needed to get it into a state where you could slot "labs" features in a forward compatible way would have likely been a tremendous re-write on its own

but there's proven methodolgies for dealing with giant balls of mud and untested/undocumented legacy code. (I'm partial to this one

First, make sure you have a reproducible environment. Then right a bunch of tests. A BUUUNCH. It's unglamorous, laborious, hard work, but it's necessary to make sure your changes don't break anything. Then you use a combination of heavy refactoring + abstraction, et voila.

I've fixed legacy software, from a Uber-clone that bought a template from a team in India (no shit, the code has references to "UberForX") and having to replace every part piecemeal over months, to re-writing financial services spaghetti code that was doing over a million a year. The approach never really changes.