Alexandervn
Joined 15 years ago
Joined 15 years ago
- Feature branch: do whatever you want
- Develop: should be good enough for the client (product owner) to look at
- Release branch: should be good enough to be tested by the test/QA team
- Master: should be good enough for website visitors
Branches are meant to be shortlived and merged (and code reviewed) into develop as soon as possible. We use feature toggles to turn off functionalities that end up in develop but can not go to production.
It would probably be easy to distinguish between the paying visitors and the regular ones. So you can also show paying visitors more content?
What would the Googlebot do with that?
For a long time I have a fascination for improving memory. It seems that visualization and memory are closely related, or even one and the same. Tony Buzan and Joshua Foer are authors that have written about this.
They write about techniques to learn a deck (or decks) of playing cards, names of people, long numbers, etc. The 'roman room' is one of these techniques, that is used for long speeches; and was also used by people like Seneca. See here a clip of how it works to learn a deck of cards: http://www.youtube.com/watch?v=X-xl7_hdWZo
The essence of these techniques is that you must create the most vibrant or bizarre imagery in your head about the subject. Not only visually, but by using all the senses: smell, taste, etc.
Da Vinci is also known for training his visualization skills by looking at an object for a moment and then trying to draw it from memory. I believe that is from Michael J. Gelb's book 'How to think like Leonardo'. (Which might not be the best source.)
For how consciousness and how we see things works this video by Susan Blackmore might be interesting, because it discusses with how much (or less) detail we can see with our eyes open in the first place: http://www.youtube.com/watch?v=sdMA8RVu1sk (from 40:00 or so)
In my projects (usually building websites or webapps) I therefore add a 'readme.md' to the root of the project and document general choices there.
Partly, it's a good thing if these sites look a bit amateurish, because they should look grassroots. It should look like: wow, I can join this. It should look authentic.
A nice example of this is www.drupal.org (where you can join) versus www.drupal.com (where you should "buy").
The new Git website is very nice. But is also a very mature project. It doesn't need help from thousands of people. It needs a lot of consumers and maybe some brilliant minds to share their ideas.
What the Go website tells: this is a very young project (not even a logo), we have some backing from Google (hence the name and the colours), we have something good (by calling it "easy" and "reliable"), but we could need your help (by still calling it "The Project") and you might want to try (look you can even try it top-left on our homepage) this if you are curious and want to have fun (see our goofy, eye-rolling, mascot).