I recommend reading the description in the link that mentions that concern is acknowledged.

I did read the description, but that doesn't make the criticism any less valid.

Makes it less valid because it was already answered.

I’m a front end engineer. I go to Defcon, i read CVEs and exploit news. It’s a hobby but I feel like it also helps to bring a different perspective into the application world because my peers don’t seem to care much.

I agree in most cases. I think they should be avoided in hero scenarios but a small flickable carousel to show product photos or something below the fold is reasonable.

If docs don’t exist for one reason or another, what are a few ways team members could assist you in better understanding the code base?

When I read the hn title I thought the direct reports wrote a readme about the manager. That made a whole lot more sense to me. How many coffees does (he/she) need to drink before it’s ok to approach their desk. How much detail do they require when explaining an issue. These are the features I’d like documented for new hires.

iPhone users can always use a plug. http://appleplugs.com/