dibbo

"Small meshtags have lifespans that depend on their complexity. A simple tag might only last for a week, while a more complex one might last for 6 months or a year. Very complex tags will never expire. This prevents the simple tags from being used up." So the mantra is, i guess, make it complex. Also leave it to the imagination of a street painter, i am sure they will make art out of it.

hey, this is wonderful. it would be great if street painters adopted this to communicate with their audience. i would love to go into a tunnels with cool street paintings and scan these signs and get access to playlists, videos and messages that the painter wants us to visit. these cool triangles could become symbols of an underground movement if promoted in these communities.

I personally prefer looking at the relevant parts of the documentation and getting shit done.

Advantages:

1. shit gets done 2. concepts that you learn get applied immediately, so the concepts stick in the brain better 3. harder to lose motivation since shit is getting done 4. it is harder to understand certain concepts abstractly, after all we are talking about programming, not theoretical physics; most programming concepts are better understood in practice esp. web based stuff. So reading and applying immediately is most often the right way to go.

Disadvantages:

1. there might be advanced functionality that you might miss if you skim through and apply, however most advanced functionality are optimizations and as we all know 'premature optimization is the root of all evil'. Donno who said that but it was someone famous. So this isn't a real disadvantage at all.

In summary, I would recommend a depth first approach, with the caveat that you go really deep into the things that you do need in the project and ignore the things that you don't need at the moment.