It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
My Software adapts multiple types of Database systems namely Relational and Key-value.
The vision with this product is that if the idea of storing information in a way which can prove beneficial for the future is condensed into a Product that can be used by almost everyone then the amount of "knowledge"(knowing how and where to implement information) will also witness a increase in amount and quality, which can further lead to solving real-world problems having a wide range.
Real-World problems include anything from analyzing someone's eating habits and altering them so as to realize certain fitness goals to predicting the economic growth of a nation.
If these tools are made accessible to more people then we can have a plethora of useful data in the cloud.
I'm sorry but I don't really understand your answer. It sounds like it solves the problem of storing data in a usable way, which is basically the problem that any other database out there is solving.
Maybe you could explain a bit how the data is structured and how the API to query the data looks like?
What I want to say is that my software adapts two database systems namely document and key-value. By establishing the relationship with the two can increase the usability of data.
I'm afraid I wouldn't be able to disclose the data structure just yet.
The Complete Software will be launched soon, I'll make sure that your queries will be solved when the actual product is out for practical use.
I'll get back to you once we're done with the release.
I'm sorry I wasn't able to answer you completely(I might sound silly I know)
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
I don't intend to be mean here, but I have to say that it gets less and less possible to take you seriously if you start an AMA and then duck, hand-wave, and ignore questions like this. You won't explain how you're blending document (or is it relational?) and k:v strategies, and it's unclear how x-with-k:v is distinguishable from x in the first place since primary keys and document ids already serve to uniquely identify records. You don't want to disclose how information is laid out, which is one of the most important questions that can be asked about any datastore. And you've ignored questions about querying, constraints, ACID compliance, replication, and even an outright softball asking what your project can do that other databases can't. There's almost nothing of substance in what answers you've given, so all you've got is a promise that a cool new database exists.... somewhere, and we can't see it, or get any substantive details about it. Best case scenario, you jumped the gun with the AMA; worst case, it's just another vaporware project, and given there are already millions of those lying around, the maximum harm done is a few people wasted a little time asking you questions :)
Hey there,
I totally understand your point of view here and I totally respect that.
But I really don't understand when did I duck or ignore questions. And It's true that I have opted not to disclose how info is laid out cause it will be a lot easier for people to understand the logistics of my product once the product itself is out and open for practical use(which it isn't as of now). I accept that I wasn't able to reply (due to time constraints) but I suggest review the post again I think I answered a question today.
I did not intend to use the AMA so as to "jump the gun" because I don't believe that it is me who has to be "the guy with the world's best software".cause it doesn't matter who the first person is to do something. what really matters is whether the people are getting good products to use it totally nothing has to do if someone does something first if his/her creation is fruitful people will use it.
I don't recall promising that I have the cool new database,I never said that what I said is that I've built something if it's treasure or trash it's totally upto the people who will use it.
Also, I don't understand how a project can be called a vaporware when you haven't even used it, I suggest using a product firsthand before forming a verdict.
I know that you're obviously older than me and more experienced so I want to be respectful in every way possible, I totally understand your opinions and will take this in the most productive manner possible.
but I really feel calling something "vaporware" without even using it is a tad bit judgmental.
anyways thanks mam (not being sarcastic or anything) I'll make sure that you're the first person to get the first copy when the product launches.
In the computer industry, vaporware is a product, typically computer hardware or software, that is announced to the general public but is never actually manufactured nor officially cancelled.
So technically, if we could use your software, it wouldn't be vaporware :P
We're not trying to get you down or anything, but personally I'm a bit disappointed. You claim that you've written a novel database engine and make an ask me anything post, but when we ask how your database works or how it is different from existing solutions, we get either a fluffy answer that doesn't really say anything concrete or a I can't talk about this until the software is published.
ask me about anything else I'll be more than happy to answer. but I don't think you get my point. You don't haven't used what I've built so it'll be just negativity pouring down all over if I just expressed everything through words without having my software out in the hands of people, everyone will just find a way to criticize anyway, cause I can't prove what I say just yet. (Try to understand) My intent for this post was different, I wasn't expecting the whole focal point of everyone to shift towards my software, the reason why I put 17 in the title was because I expected to get asked questions about my skills in database as I built an engine. This whole things got turned the other way. No I am not intending to tune this thing to a different frequency but that's the truth....
It's somewhat similar to saying "Hey, I built program in c++ AMA" that way people would ask question directed towards the skills of someone.
OK, maybe everyone just believes that I ain't got nothing and everyone has the right to think what they want I am here to learn and I will along my way, it's just another experience.
But think about it, this thread became something I didn't expect now please don't say that I am saying this cause I am just a piece of crap coder who ain't got anythin' and is trying to jump the gun and is trying to gain attention. No....
Try and switch shoes, you'll know.
I honestly feel like if everyone was brutally honest they would say - "You built nothing, you're just here to make a fuss, we know more than you do we've got more skills"
now everyone'll just turn around and say "hey we never said that or implied anything of that sort" but believe it looks something like that when I(the bad guy here, the attention-seeker, the disappoint-er, and a full of crap douchebag) read it on my screen.
OK People,
you want to prove that I ain't got nothing no skills no shit, FINE
Not angry not happy.
everyone trynna come at me
Stay Blessed People.
Sorry If I broke loose but man this shit gets to you after a certain point, and it's not pretty why don't everyone just say what they want to say in one sentence why waste your time by searching stuff online and then typing a hundred words. save you energy people. Just one line I'll take it.
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
The part we're interested in is the database, though! It's great that you're developing your skills at a young age, and for all we're having to take your word for it at the moment it's legitimately impressive that you've seen a project of this scale through almost to release. But we've all been 17, and plenty of us were even programming at that age. There just isn't much to ask about that.
What are you worried will happen if you talk about the implementation details?
I'm sorry that it came across that way. I think I was honest in what I said, I think it's cool that you've built a database engine and I want to know more about that and I was confused that you didn't want to talk about it. I didn't mean anything else.
I'll withdraw from the thread now because I don't have anything else to say.
What flavor of database is it? Relational, document, key:value, graph, something else?
What real world problems are you hoping to attack with it, and what does it bring to the table that existing products don't?
Hey Dian,
My Software adapts multiple types of Database systems namely Relational and Key-value.
The vision with this product is that if the idea of storing information in a way which can prove beneficial for the future is condensed into a Product that can be used by almost everyone then the amount of "knowledge"(knowing how and where to implement information) will also witness a increase in amount and quality, which can further lead to solving real-world problems having a wide range.
Real-World problems include anything from analyzing someone's eating habits and altering them so as to realize certain fitness goals to predicting the economic growth of a nation.
If these tools are made accessible to more people then we can have a plethora of useful data in the cloud.
Hope I could answer well.
Thanks for asking
I'm sorry but I don't really understand your answer. It sounds like it solves the problem of storing data in a usable way, which is basically the problem that any other database out there is solving.
Maybe you could explain a bit how the data is structured and how the API to query the data looks like?
Hi,
What I want to say is that my software adapts two database systems namely document and key-value. By establishing the relationship with the two can increase the usability of data.
I'm afraid I wouldn't be able to disclose the data structure just yet.
The Complete Software will be launched soon, I'll make sure that your queries will be solved when the actual product is out for practical use.
I'll get back to you once we're done with the release.
I'm sorry I wasn't able to answer you completely(I might sound silly I know)
I don't intend to be mean here, but I have to say that it gets less and less possible to take you seriously if you start an AMA and then duck, hand-wave, and ignore questions like this. You won't explain how you're blending document (or is it relational?) and k:v strategies, and it's unclear how x-with-k:v is distinguishable from x in the first place since primary keys and document ids already serve to uniquely identify records. You don't want to disclose how information is laid out, which is one of the most important questions that can be asked about any datastore. And you've ignored questions about querying, constraints, ACID compliance, replication, and even an outright softball asking what your project can do that other databases can't. There's almost nothing of substance in what answers you've given, so all you've got is a promise that a cool new database exists.... somewhere, and we can't see it, or get any substantive details about it. Best case scenario, you jumped the gun with the AMA; worst case, it's just another vaporware project, and given there are already millions of those lying around, the maximum harm done is a few people wasted a little time asking you questions :)
Hey there,
I totally understand your point of view here and I totally respect that.
But I really don't understand when did I duck or ignore questions. And It's true that I have opted not to disclose how info is laid out cause it will be a lot easier for people to understand the logistics of my product once the product itself is out and open for practical use(which it isn't as of now). I accept that I wasn't able to reply (due to time constraints) but I suggest review the post again I think I answered a question today.
I did not intend to use the AMA so as to "jump the gun" because I don't believe that it is me who has to be "the guy with the world's best software".cause it doesn't matter who the first person is to do something. what really matters is whether the people are getting good products to use it totally nothing has to do if someone does something first if his/her creation is fruitful people will use it.
I don't recall promising that I have the cool new database,I never said that what I said is that I've built something if it's treasure or trash it's totally upto the people who will use it.
Also, I don't understand how a project can be called a vaporware when you haven't even used it, I suggest using a product firsthand before forming a verdict.
I know that you're obviously older than me and more experienced so I want to be respectful in every way possible, I totally understand your opinions and will take this in the most productive manner possible.
but I really feel calling something "vaporware" without even using it is a tad bit judgmental.
anyways thanks mam (not being sarcastic or anything) I'll make sure that you're the first person to get the first copy when the product launches.
See ya'
From the Wikipedia article:
So technically, if we could use your software, it wouldn't be vaporware :P
We're not trying to get you down or anything, but personally I'm a bit disappointed. You claim that you've written a novel database engine and make an ask me anything post, but when we ask how your database works or how it is different from existing solutions, we get either a fluffy answer that doesn't really say anything concrete or a I can't talk about this until the software is published.
ask me about anything else I'll be more than happy to answer. but I don't think you get my point. You don't haven't used what I've built so it'll be just negativity pouring down all over if I just expressed everything through words without having my software out in the hands of people, everyone will just find a way to criticize anyway, cause I can't prove what I say just yet. (Try to understand) My intent for this post was different, I wasn't expecting the whole focal point of everyone to shift towards my software, the reason why I put 17 in the title was because I expected to get asked questions about my skills in database as I built an engine. This whole things got turned the other way. No I am not intending to tune this thing to a different frequency but that's the truth....
It's somewhat similar to saying "Hey, I built program in c++ AMA" that way people would ask question directed towards the skills of someone.
OK, maybe everyone just believes that I ain't got nothing and everyone has the right to think what they want I am here to learn and I will along my way, it's just another experience.
But think about it, this thread became something I didn't expect now please don't say that I am saying this cause I am just a piece of crap coder who ain't got anythin' and is trying to jump the gun and is trying to gain attention. No....
Try and switch shoes, you'll know.
I honestly feel like if everyone was brutally honest they would say - "You built nothing, you're just here to make a fuss, we know more than you do we've got more skills"
now everyone'll just turn around and say "hey we never said that or implied anything of that sort" but believe it looks something like that when I(the bad guy here, the attention-seeker, the disappoint-er, and a full of crap douchebag) read it on my screen.
OK People,
you want to prove that I ain't got nothing no skills no shit, FINE
Not angry not happy.
everyone trynna come at me
Stay Blessed People.
Sorry If I broke loose but man this shit gets to you after a certain point, and it's not pretty why don't everyone just say what they want to say in one sentence why waste your time by searching stuff online and then typing a hundred words. save you energy people. Just one line I'll take it.
It's fine :(
The part we're interested in is the database, though! It's great that you're developing your skills at a young age, and for all we're having to take your word for it at the moment it's legitimately impressive that you've seen a project of this scale through almost to release. But we've all been 17, and plenty of us were even programming at that age. There just isn't much to ask about that.
What are you worried will happen if you talk about the implementation details?
Thanks Mam,
I'm sorry that it came across that way. I think I was honest in what I said, I think it's cool that you've built a database engine and I want to know more about that and I was confused that you didn't want to talk about it. I didn't mean anything else.
I'll withdraw from the thread now because I don't have anything else to say.
OK, I know you were being honest. well, thanks! :)