51–60 of 94 posts
Not only that, if the core team moves to the open source product to "rebuild" the same features, isn't that way too dangerous IP-wise?
This is also one of the reasons I didn't use dgraph: Open source core doesn't work. All the companies that were sold to now have nowhere to go for support.
Earlier quoted context omitted.
> I don't know who you are or what your motivations are. I'm a rubbernecker passing by a car crash. I have no other motivations. I don't know you personally or anyone who works at Dgraph. I'm piecing together a guess of the culture from what's available externally. I would love to read the details when you're ready to share. Editing to say that the only reason I remembered the blog was because there were multiple par…
It sure seems like you used to work there since you're making specific critiques about company culture and decisions that only someone internal would know. And you're taking statements like "lost a couple of deals last quarter due to engineering challenges" as being a personal slight against the engineering team when an impassioned observer would not really see it that way. I don't know the specifics of Dgraph's fail…
I have no opinion on this broader company, but you focused on the wrong part of the sentence.
OP was focused on "I can help solve in weeks but would take my team months on their own" -- something that indeed is throwing your engineering team under the bus to me, an impassioned observer.
Yeah, that's a bad look for both dgraph and the new company imo. What guarantees the same thing ran by the same people won't have the same issues again? Not only that, if the core team moves to the open source product to "rebuild" the same features, isn't that way too dangerous IP-wise? This is also one of the reasons I didn't use dgraph: Open source core doesn't work. All the companies that were sold to now have now…
I think all you need to know about this CEO/CTO, Dgraph as a product, and the underlying key-value database Badger, is that when people report data loss bugs where the database fails to return data written to it, they'll claim it's not data loss if the data still happens to reside on the disk somewhere, and *then delete the bug report*. https://github.com/dgraph-io/badger/issues/578 titled "Badger unable to return da…
Have you tried to build a data layer engine?
This kind of attitude is so one dimensional from my perspective... they are trying and it's hard to always be perfect when it comes to data. Inevitably if you're in the data game sometimes data loss happens, that's just the nature of the game. It's not black-and-white like you portray it.
I've followed Dgraph off and on. I enjoy looking through their open sourced work. A lot of it is interesting. Manish seems to be THAT person. The technically competent, unwavering to the technical vision, doesn't work well with others person at your company. He went on to found a startup so he could do what he wants, and unfortunately has now realized board members are very similar to managers at Google. Here's a blo…
Manish here. I don't know who you are or what your motivations are. Glassdoor Reviews are anonymous (read trolls) and a lot of them were created post the layoffs, to create a story that would take the blame away from the hired CEO. Read between the lines about why the layoffs happened in the first place. If not, read this: https://www.glassdoor.com/Reviews/Employee-Review-Dgraph-Lab... When you have nothing to say ab…
Could you have better optimized your personal brand? Maybe. Could you have also done the engineering you've done if you had? Who knows. Don't over think it. State is hard
I feel for this person, but there's a line in here I found revealing: > Unfortunately, Dgraph was always undervalued by investors. This feels a bit like blaming the investors for why the company failed. To put it bluntly, there's a point at which you raise capital and build on vision. Your early investors and users are taking a giant leap that a. you can execute on the vision and b. customers will one day want to pay…
Yeah, that's a bad look for both dgraph and the new company imo. What guarantees the same thing ran by the same people won't have the same issues again? Not only that, if the core team moves to the open source product to "rebuild" the same features, isn't that way too dangerous IP-wise? This is also one of the reasons I didn't use dgraph: Open source core doesn't work. All the companies that were sold to now have now…
I would respectfully disagree that open core doesn’t work - companies like Confluent, Databricks, MongoDB have shown that you can succeed with open core. DGraph I think tried to do too much rather than focusing on graph databases, which caused the commercial product to fail.
I think all you need to know about this CEO/CTO, Dgraph as a product, and the underlying key-value database Badger, is that when people report data loss bugs where the database fails to return data written to it, they'll claim it's not data loss if the data still happens to reside on the disk somewhere, and *then delete the bug report*. https://github.com/dgraph-io/badger/issues/578 titled "Badger unable to return da…
Do rockets sometimes blow up on the launch pad? Yes. Does that mean they shouldn't have tried to build a rocket ship? Have you tried to build a data layer engine? This kind of attitude is so one dimensional from my perspective... they are trying and it's hard to always be perfect when it comes to data. Inevitably if you're in the data game sometimes data loss happens, that's just the nature of the game. It's not blac…
The level of negativity on HN around hard engineering problems like data stores...it's really unforgiving here.