Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "state"
"my greatest fear in life is my best not being good enough."
Currently, I am building my second business around blockchain.
I am stacking on using the popularity of cryptocurrency and it's novelty to push the product universal.
My limitation (what I think):
1. My environment - unfortunately I live in a third world country
2. Naivety: I have never scaled a business, failed in my first attempt(this is my second).
3. Lack of fund: my budget is pretty low, and no I dont have a family support to raise any for marekting and promoting the business, so I am let with option of scaling it organically ( what "organically" means is spamming social media, forum's comments section to grow customers
4. Really the only option present: most folks here wont know what it means to be in a state of "survival", failing will cause you suffering.
5. Poor network: My friends, or the people around dont understand, cant comprehen what this means.
1. I get to know what it means to carry your idea to the world again, this I hope will improve my knowledge base on business and make me less naive.
2. Portfolio boost: "wow!" that should be people's reaction when I tell them about the project.
3. If I succed, I hope the incentive will take me out of this shit hole.
4. I really want to get out of this shit hole - this should work!
I'm going insane.
So let's say you have an object in database, with 20-30 related objects (Or lists of objects) (All related objects have a foregn key to the "main" object).
Now, as long as you just edit/create thinga everything is fine.
But the deletion... Oh MY GOD
"Just put on delete cascade", right ? RIGHT ?
WRONG ! presence of some objects should block delete, while others can be deleted and some are "situational" depending on the first object state.
So delete operation with all the checks takes .... 1 - 2 seconds.
Seems fine ? WRONG ! When you have 40 or more objects to delete, even 1 second is too long.
Should I say "fuck it" and just write a stored proc which will crash if object cannot be deleted for any reason ? because with Entity Framework, I don't see how I can do it effitenly.
But I HATE stored proc, after couple of month/years noone remembers how they work...
Ok I feel better.8