Alexandervn

From their about page, it's 'Surinamese for “Start over again”'. It seems to be pronounced as "Ah-dee-yen".

There is also ngForward, which is Angular 1 with Angular 2 syntax.

Yeah, we also use something like this for building a website/webapp (for a client) with 5-10 people.

- 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.

Link goes to this page.

It's still kinda waste to show paying visitors an empty ad.

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?

Very interesting!

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)

The problem is that the implementation of the 'why' can be scattered over many files, classes, functions, etc. So where to put the comments?

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.

No so clean to me, without an 'alt'-attribute..

It's not about being "ugly" and needing help to become "beautiful". It's what you are trying to tell people.

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).

The new Git website is awesome. It makes you think: if they spend that much attention to every detail, this product must be really good..

And if Google can index this, it probably values all text the same; it's just plain text.

Addy Osmani has a nice excercition [1] on the history of MVC in Developing Backbone.js Applications, where he states:

"Developers are sometimes surprised when they learn that the Observer pattern (nowadays commonly implemented as a Publish/Subscribe system) was included as a part of MVC's architecture decades ago. In Smalltalk-80's MVC, the View and Controller both observe the Model: anytime the Model changes, the Views react."

So, not really new actually.

[1] http://addyosmani.github.com/backbone-fundamentals/#mvc

My DNS provider (also on my VPS) can't resolve both domain names.

I can 'dig' the domain names though and at least visit http://ac/ through it's IP-address in the A-record (http://193.223.78.210/).

Nice venue! http://www.dotjs.eu/venue

Do you mean companies using it? Look for SimpleGeo. Do you mean librairies? Look for Express or Restify.

It removes the top million in general, not per query.

Have you considered Mongrel2 or ZeroMQ for your stack?

"Generalists like Hillman Curtis, Steve Jobs and Bill Gates are becoming more and more uncommon." "Nobody cares anymore."

Where I am coming from this is certainly not true. At a small company I know they (still, traditionally) hand out copies of MTIV if you succeed for your internship. And I am coming from a school where you can also specialize in Experience Branding and Nathan Shedroff. A lot of young people want to become the next John Lasseter, _why or Kevin Kelly.

The names you are talking about are special though. They were pioneers, but not only because of their own merits but also because it was just the right time.

"24. [..] Learned about the Python requests library. I will now judge all libraries based on this work of beauty."

Completely agree. As if you are writing pure HTTP.

Starting with Node is a very poor choice if you want to learn front-end. But you can't go wrong with The Good Parts and you at least now know what's all the fuss about Node. But now let's really start learning front-end.

Begin with semantic HTML. It's really the basis. The best front-enders I know first write all the HTML for a project, and only then start adding CSS and JS. Learn why <b> is wrong and <strong> isn't. Make sure you're HTML validates.

Now go to CSS. It's really easy to add some colours or fonts. You learn CSS as you go. But there is one hurdle here: the box model. Learn about float:left, position:absolute, display:block and how they entangle.

This will be harder than you think. You will need to learn some tools to debug this. Install Firebug and the Webdevelopers Toolbar in Firefox and see how you can fix your layout. Browsers aren't that scary.

We're only learning here, so skip IE for now. That one is actually kinda scary. Though if you really want to learn front-end, it's all about browser differences.

And then Javascript. Now it will be easy. Stick with jQuery and connect with your Node instance with socket.io. Learn Backbone if you want to make snappy web apps. There's a lot to learn in this 'grey field' between back-end and front-end. But at least you now know front-end.

Does anyone have a clue of what he is building right now? What are the pyramids?

Maybe you would want to elaborate on that?

There is always a tendency by people to place more content on the frontpage or above the fold to give it 'more attention'. This is a fallacy.

An extra column clutters the homepage and adds no functionality to what a simple click on 'new' (which is the most important link, right next to the brand name) would also do.

If it is the case that too few good articles arrive on the homepage, since everyone is ignoring the new ones, then the algorithm should be changed. But I don't think that is the case at all.

As an extra, I like reading HN on my mobile phone. And with the current one column design this works very neatly. An extra column would complicate that. You might handle that with CSS media queries, but I still think it wouldn't be elegant.

Do you have a source (video, transcript) to that talk of Alan Kay in Germany?

That's a really interesting article. Too bad the <title> of that document is 'Test page', making it practically unfindable with Google, SEO-wise.

Based on the title of your post I was assuming to read something like '..and I picked up Ruby on Rails, a few tutorials, and just started coding..'

How much technical knowledge did you have before starting this project? And how much did you learn in the process? Doesn't it feel awkward to say you have 'built' it?

It also made me think about post-scarcity economics. http://en.m.wikipedia.org/wiki/Post_scarcity

He does know how specificity works, I guess. But he is talking about reusability and inheritance. Still I find the claim way too harsh. I use id's in my CSS occassionally. For #wrapper or #carroussel maybe. It it premature optimization to (re-)write everything to classes. Your HTML should be leading.

Nice, I didn't know Ctrl-T. I usually use ^ or g; to go back.

If it really sucks, people will tell you. So build something and ask for feedback.