I think you'll need to implement a queue of some sort. if it's locked while the message is being edited, then any amount of serious traffic will block the whole thing and turn people away.
So instead of leaving a message for the next person, put a message in the queue, and each time somebody visits grab the next message in the queue.
I respectfully disagree and stand by my design decisions.
I've seen projects like the one posted to HN somewhat recently where the guy would accept any PR on a GitHub repo.
This way, you get to leave a message for only one single person in the world. (This also takes care of people posting terrible things on my own website :-)
Yes, while there's a significant traffic, the site is basically unusable, but at the same time this was inevitable if I wanted to let people know about this project.
I recommend saving the link and coming back when the crowd clears up :-)
I'm still confused why that happened. I walk in lots of crowded places and am perfectly capable of not "trampling children" without a need to vocally warn them about my movement... Like, just if you're going to run into a kid... just Don't do that?
You say a lot that startups should collect revenue very early. If my startup is currently just a side-project and I haven't yet incorporated, what's the legal concern of collecting payment?
I feel like startups like Door Dash have dealt with this, but I was just wondering if there's anything I should be aware of.
This is great! I was just thinking about something similar, perhaps you'd like to work it in.
basically, it would automatically assign meeting times, based on who's meeting, for how long, except that it would be scheduling several meetings, and take those into account.
I.e. throughout the week various employees in an office would simple set meetings for "friday"
The system would compile all the meetings that take place, and schedule them, to the best of their ability, so that no two meetings would conflict. On thursday night, the times are finalized and the meetings are placed on attendees calendars.
You'd need some sort of conflict resolution, but if you ran it each time for each meeting request came in, you could alert the involved parties immediately.
This looks fantastic. Would love to see what it looks like when volume increases.