How to validate a given domain is owned by the user?@DougM You are still missing the point. Sometimes a company buys a domain and has someone else host it. Sometimes a company who owns a domain sells usernames@domain and doesn't reserve postmaster@domain. Both of these scenarios and others would allow someone other than the owner to confirm that they were the owner in your system because you are making a false assumption

Sep26

comment

How to validate a given domain is owned by the user?@MSalters technical ownership does not lie with the hosting company if the domain is registered to the actual company. The person who answers to postmaster@domain may not be the legal OR technical owner. So this method simply does not work.

Sep26

comment

How to validate a given domain is owned by the user?@MSalters postmaster often goes to an email hosting company that is NOT the owner of the domain. Many mail hosting platforms selling username@domain don't reserve it or stop people using it, so even as an optional method it does not prove ownership

What is the origin of the negative term “legacy code”@Kickstart i think the problem with that is that the negativity doesn't stem from the name, but the code. :) 'Legacy' in general terms is just as positive and the spin that changing to'Heritage' adds is likely to be temporary.

Jun10

comment

What is the origin of the negative term “legacy code”Pretty much any old code is a burden to add to or change because requirements change over time, developers move on or in hindsight you can always see ways it could have been done better. In business we don't have the luxury to refactor everything so there will always be a proportion of legacy code that we are encumbered with. This is the literal meaning of legacy.