You are both too normal so the product works as intended for you. Unfortunately however, real engineering means making it work in all likely cases. Anyone outside of upper-middle class suburbia has an absolutely terrible experience with computers. The browser takes a minute or more to start. Button clicks take 10 seconds. You wouldn't know this because they are not your target market. But don't get confused and think I'm appealing to feelings. I'm saying software should be acceptably performant, when currently most is not, especially not websites. I'm saying that 99% of people get a terrible experience with software, once you step outside your bubble world. Real software should work on only 1000Mhz when performing trivial tasks like displaying text and forms (to say the least). Real software should not break down because of certain attributes about your IP address, user agent, etc.
I can't tell where you're coming from without getting to know you, but all these "works for me" forum posts are invalid for the simple fact that if I have a real conversation with someone in person, 99 times out of 100 it will just turn out they are acclimatized to slow half working bullshit. On forums the only reason they get away with spouting this nonsense is due to the upvote system and their cliques. Like if I complained about battlefield 2 taking 20 seconds to load the menu mid game back in 2004, a group of stupid forum posters will all either have a $2000 rig (in current dollars) that was able to bypass this bottleneck, or they're just some casual who played the game for 10 minutes in their life so they haven't had to open the menu a lot yet.
In the case of a signup form, it could and should have a standard solution that doesn't require amateurs to code it themselves, 20 years ago. Like a standard authentication protocol. And of course it should not rely on flaky communications like a verification email. All these things work for you because you're too normal, despite being terrible misconceived ideas. Since the web as a platform is a misconception, you could not make an application that uses a standard authentication protocol because the web introduces all kinds of problems due to its weird way of operating like the fact that you're vulnerable to CSRF by default and asinine nonsense like JSONP, and the fact that web applications aren't really a real mode of software but a bunch of hacks like embedding a script tag, setting the doc type, and fiddling with strange headers, and you can't really have libraries without all these fixes from 5 minutes ago like pinning hashes of resources and building some giant half working external dependency management system. Then at the end of the day it's still each website pulling the authentication code with whatever implementation of their choosing so you still can't trust it as well. Your "working" system is built out of a compatible stack of misconception-compatible software. The moment you misstep, for example if you want some privacy and put on a proxy, you will be severely punished since that breaks half of the web and leaves you with the overhead of doing workarounds for every single interaction.
I can't tell where you're coming from without getting to know you, but all these "works for me" forum posts are invalid for the simple fact that if I have a real conversation with someone in person, 99 times out of 100 it will just turn out they are acclimatized to slow half working bullshit. On forums the only reason they get away with spouting this nonsense is due to the upvote system and their cliques. Like if I complained about battlefield 2 taking 20 seconds to load the menu mid game back in 2004, a group of stupid forum posters will all either have a $2000 rig (in current dollars) that was able to bypass this bottleneck, or they're just some casual who played the game for 10 minutes in their life so they haven't had to open the menu a lot yet.
In the case of a signup form, it could and should have a standard solution that doesn't require amateurs to code it themselves, 20 years ago. Like a standard authentication protocol. And of course it should not rely on flaky communications like a verification email. All these things work for you because you're too normal, despite being terrible misconceived ideas. Since the web as a platform is a misconception, you could not make an application that uses a standard authentication protocol because the web introduces all kinds of problems due to its weird way of operating like the fact that you're vulnerable to CSRF by default and asinine nonsense like JSONP, and the fact that web applications aren't really a real mode of software but a bunch of hacks like embedding a script tag, setting the doc type, and fiddling with strange headers, and you can't really have libraries without all these fixes from 5 minutes ago like pinning hashes of resources and building some giant half working external dependency management system. Then at the end of the day it's still each website pulling the authentication code with whatever implementation of their choosing so you still can't trust it as well. Your "working" system is built out of a compatible stack of misconception-compatible software. The moment you misstep, for example if you want some privacy and put on a proxy, you will be severely punished since that breaks half of the web and leaves you with the overhead of doing workarounds for every single interaction.