gprisament

The movie Idiocracy explains it all.

I was thinking the same thing. I'd consider removing the "500 kLOC" line. Makes me suspect your code is verbose rather than elegant.

I've found that the best compromise is to use verbose "n00b-style" commenting in header files (or wherever your interfaces are defined), and sparse commenting in the implementation. Interfaces are like contracts, so you want to make sure everything (including how corner-cases are handled) are explicitly described. With well-designed and fully-documented interfaces, the implementation code can usually be quickly understood even if it lacks comments and is written in a more "advanced" style.

I haven't actually played it, but "blueberry garden" looks pretty sweet from the trailer and won top prize at the independent games festival. http://eriksvedang.com/blueberrygarden/

I'm a huge proponent of C programming, but I have to say this article is not very compelling. Object-oriented programming is just as important in C as it is in C++, it's just the syntax is different.

I think my high regard for C comes from work experience: the C projects I've worked on have been less of disastrous messes than the C++ projects I've worked on. It's hard to pinpoint why, because on a small scale C++ is very nice. But I've noticed that once > 10 people get involved, C++ projects become more bug-prone and difficult to understand and fix.

I especially love ADTs in C. C++ encourages you to declare public and private and protected class members in a single class declaration in a single header file. Yes, you can work around this (ie, have a single private member m_priv), but I haven't seen it done much in practice. In C, on the otherhand, it's much easier to separate implementation details from the public interface. Put "typedef struct Foo * FooHandle" in the public header and the structure definition in the .c file. This is common practice in C and very elegant. As a coworker once put it, "I don't like the way people put private members in header files in C++... it's like seeing the class's underwear".

Sometimes it helps to look at examples of bad resumes. Some real gems here: http://resumedoctor.com/WorstResumes.asp.

Also, does anyone else think that this accredited investor stuff is BS? Why is it darn-near-impossible to invest in private companies unless you have $1mil?

This got me thinking: it'd be nice if there were something like sharespost for startups at the seed stage. For instance, a site where you can post your pitch and sell equity in your startup to raise initial capital. With low enough valuations I'm sure it would attract buyers, especially if there were easy diversification options (kinda like lendingclub has) for buyers.

Is there anything like that?

Any good examples of this paradox from your lives?

Does anyone else think that Twitter-based comment sections are just plain broken:

158,616,176 reasons why Google Chrome OS won’t fail @SiliconANGLE. http://bit.ly/7TDjDp

158,616,176 reasons why Google Chrome OS won’t fail @SiliconANGLE. http://bit.ly/7TDjDp

158,616,176 reasons why Google Chrome OS won’t fail @SiliconANGLE. http://bit.ly/7TDjDp

... ad infinitum

The big appeal of C for me is that it's portable (as long as you know to avoid the non-portable parts, anyway). Sorry, but I won't be using any language extension that will only compile on mac. And anyway, function pointers aren't that hard to groc.

Chrome OS will presumably include Google Native Client support so that native code can run (with some limitations) (long but good video on Google Native Client: http://www.youtube.com/watch?v=zgng4C18nNk).

I'd much rather have an OS with the capabilities to sandbox applications, but that can still run an arbitrary binary. For example, I cannot imagine hardware device manufacturers writing drivers that are "cloud apps".