It does rather depend if you are already experienced enough to know what IP addresses, subnet masks, gateways and DNS settings actually mean.
Remember if the router and the laptop both come preset with DHCP on it just creates additional work and admin to change all that to get a working setup. It also complicates the setup if you want to take your laptop and get online elsewhere.
Static configuration also mulitplies up the work if you have more than one thing to connect to your network. If you want the same IP every time that is what DHCP reservation is for and still manages all the addresses in one place.
You can test DHCP is working by leaving everything on default settings and plugging in an ethernet cable so that is relatively trivial, then you know it's only the wireless bit to sort out.
If the wrong wireless password is used with static IP the status icon may show connected regardless, with auto IP it will show either no connection (WPA) or limited connectivity 169.254... (certain WEP setups) so at least you have a clue.
Static IP will be fine for some people.
But I do find E7er pops up saying changing to static IP (without adapting it to suite the OP's setup) is the answer to every networking problem when in fact the advice usually has nothing to do with solving the problem (wireless question in this case) and in worst cases following that advice can prevent the OP from reaching a working setup.
prompt $P - Invalid drive specification - Abort, Retry, Fail? $G
prlzx on n e w n e t Max ADSL