I think the sentiment for the pet peeve is commentary on the perceived inefficient sequence of the data input and a hope for reducing the number of fields entered from 3 to 1.

>I have a pet peeve for having to enter my zip code AFTER I've already had to type in the city and state.

The city and state can be derived from the zipcode - so why not simply ask for the zipcode to be typed and then auto-populate the associated city and state.

▲

cwmma 3 days ago | parent | next [-]

There are multiple zip codes in my state (Massachusetts) that cover multiple towns some examples include 01002 which is Pelham and much of Amherst, 01027 which is both Easthampton and Westhampton (different towns) etc.

	▲	pseudosavant 3 days ago \| parent [-]
		Thanks for the heads up. It definitely used to include the 0xxxx ZIP codes. It is supposed to just naively fetch everything between 00000 and 99999 and record the USPS response. I'll have to re-run it and update it.

▲

dfxm12 3 days ago | parent | prev | next [-]

The city and state can be derived from the zipcode

A few comments here suggest this isn't true.

If you want to reduce input to one field, the autocomplete based on the street address that I brought up is the best experience I've come across.

	▲	shagmin 3 days ago \| parent [-]
		I'm in a zip code that spans two cities and I can think of other ways it gets complicated in different scenarios. There are places where I can throw a ball across multiple zip codes, sales tax jurisdictions, municipal lines, county lines, etc., with varying degrees of overlap. The problem I've anecdotally seen with autocomplete is there's another property with the same street address as mine but in a different city and different zip code (granted only last digit is different IIRC) about ~15 miles away and on more than one occasion it's caused a few mix-ups.

▲

jandrewrogers 3 days ago | parent | prev [-]

> The city and state can be derived from the zipcode

False. Some ZIP codes even cover multiple States.