akshay kadam (a2k)
@deadcoder0904
That might work too.
because why ask the same question twice?
It will happen because there is no search yet so it depends when you will implement it. But again nobody searches because its harder than directly asking (personal opinion because that's what I do all the time on StackOverflow 😂)
For it not to happen you will need a similar questions functionality like StackOverflow
Slug-ID or the one like Medium does (Slug-BigUniqueID). The advantage is that 2 questions can be same so only way to differentiate is by unique IDs :)
Thanks! I think having duplicate questions won't happen too often (because why ask the same question twice?), but I do indeed need to keep it mind for when it does happen.
I'm thinking of just adding an incrementing number to the end of the slug (e.g. "foo-bar" for the original question, and "foo-bar-2" for the duplicate question)
That might work too.
because why ask the same question twice?
It will happen because there is no search yet so it depends when you will implement it. But again nobody searches because its harder than directly asking (personal opinion because that's what I do all the time on StackOverflow 😂)
For it not to happen you will need a similar questions functionality like StackOverflow
Yep, I sometimes cut out from all social media so that's when I am not active. So will need it then. Also, graphs are better than showing all the todos. Sometimes todos will be a lot. Or a personalised newsletter would be much better. Like we choose if we want to see new products or todos.
Wow so Video Engagements are greater than Pics. Good to know. I always thought it was the opposite 😂
/r/startups
/r/entrepreneurs
/r/sideproject
And anything related to your niche
Thank you 🙌
I have no doubts now & if I have any when I actually build it, I will ask you later on. Thanks Max :)
Thank you for such a wonderful answer, Max 👏
Can you answer the question about the app in which I mention the 6 steps above❓
I think its good for Serverless but not sure. Up is very good & I maybe use that or use Serverless Framework.
Also, regarding Databases I read during my Engineering that if 2 people perform the write operation simultaneously then it will probably have a race condition with incorrect values. How to solve that❓ I don't think its a serverless problem but if you can answer that :)
Also, whats the harm in keeping the database open❓Does it have any cost if I keep it open❓
You can implement any service you want fully on serverless unless you need to use Websocket (then you'd need to combine serverless API with a traditional server). To avoid race conditions you can look into transaction locking (ex: in Postgres): stackoverflow.com/questions/4… or you can set flags with a Redis caching layer. The reason why you should always close your DB connections is that functions create a new connection on each invocation. Considering that it's infinitely scalable, we get a bottleneck at the DB level. So your database solution should be ready to handle thousands of connections at the same time.
Thank you 🙌
I have no doubts now & if I have any when I actually build it, I will ask you later on. Thanks Max :)
Isn't that done through System Preferences > Notifications excluding the regex part?
You can disable them altogether forever and I don't want that.