What does the desktop SDK do badly? How is this handled in linux/mac?
426 karma · joined June 9, 2008
What does the desktop SDK do badly? How is this handled in linux/mac?
I've got a lump in my throat right now.
If Apple can't market it's products on their own features and has to rely on this kind of negative adverts I'd say it's really hitting a low-point. The ad kind of pisses me off actually.
Plus it takes balls to venture into a space that's dominated by the mighty Google :-)
FEEDBACK:
* The name sucks - especially the "go" at the end. "Duck duck" I can live with. "Duck duck go" somehow doesn't feel right.
* Fonts/Colors etc - I really wouldn't worry about it. People get used to almost anything once they get good enough results. The hue and cry at reddit when the new version came out is proof enough of that. A few months on everyone has forgotten completely what the old version looked like and it hasn't hurt them any.
Heck, when Google came out their interface wasn't anything to sing and dance about. But now everyone thinks it the bee's knees and the cat's whiskers :-D. Just get good results and worry about the font/logo/colors some other day.
* For a few searches, the results were impressive and I liked the flow (I searched for "Haskell" and "Dragonfly" (the movie) plus my name etc).
I was really getting into it when my search for "Indian Recipes" returned recipes from Karnataka. The "more links" didn't seem to return very good results either. I had to go back to Google (which returned really good results).
* URL's of results - This is another big one. The way the URL's are currently returned is really bad - it looks like part of the text and is difficult to quickly scan for. It's really important for most users to be able to quickly scan the urls of the results. In your current interface we have to depend on the title, which is not half as useful.
Overall - it's a great job! I'm VERY impressed.
All the best!
I read the article he's bashing and I thought the code was nicely written and quite an enjoyable read. It certainly wasn't that hard to understand.
Answering his points in brief:
>No complete declarations of complete types, even though it would be (kind of) possible with JavaScript. So I can't start by visualizing the data structures.
Type declarations are not mandatory to understand code.
>No type declarations, but lots of confusing variable names, so I'm constantly going back trying to figure out what's what.
The variable names are reasonable (symbol_table, scope, expression, etc). The most confusing were "nud" and "led" but those were explained in detail later ("null denotation" and "left denotation" - used for binding operators during precedence).
>Dynamic modification of fields in objects. For example the function advance() adds the field arity to the token object, which was not declared anywhere, so you only find out about this by reading this function. This goes against everything sane in programming.
Goes against everything "sane" in programming? It's just something the author isn't used to. It's perfectly valid programming technique and I've used it in python.
>Going completely overboard, the field arity is used to store whether a token is a "name", "literal" or "operator" but later, for operators, changes this field to "unary", "binary", etc. (Truly bad programming, but not related to my argument about typing.)
I can't make any sense of this rant.
>To deliver the final blow to understandability, in functional style, the member functions of the objects are dynamically added and modified. At this point, if I see an object, I don't know its "type", but even if somebody tells me that, I don't know what state that "type" is in: what the data fields are, what they are used for and what the member functions do.
I get the feeling this guy just has a mental block about the way programs should be (C++/Java yay! Anthing else - boo!) and is unwilling/underexposed to other programming paradigms.
>Given the cognitive difficulties above, how does one look over the code to verify that it's correct? It's hard enough with static languages, here it seems quixotic. How about finding bugs?
The same as with typed languages except that the compiler doesn't do one level of verification for you.
I understand pg's argument that you have to work at being popular. In my (Indian) school, I was a typical nerd - I was poor, often wore uniforms from my previous years, I loved to read, and couldn't bother to spend the time socializing. There were a few others like me and a few widely popular, athletic, rich kids.
But we never got picked on for "being nerds"! Never! If anything, we got respect for being good at our work. It didn't make us popular but we had good friends (hell I had my share of girls in high school) and overall an enjoyable experience.
Sure there were cases of bullying, but they were one-off. It was not nerd==target and even the bullying was handled pretty soon, either by us (as a group) or the teachers.
I really would like to know where this animosity towards nerds comes from. I think that's the interesting (and painful) part of American culture that needs probing. It's definitely not universal. Any ideas?
Outsourcing works. Most reputable outsourcing companies are looking for long-term relationships and they are usually very serious about feedback and customer satisfaction. However, like anything else, it takes work and research. You wouldn't hire a single developer without rigorous interviews and even so it would take a while before he/she was up to speed. How then can you expect there to be no overhead with the 5-10 outsourced developers?
I've personally worked on projects for Yahoo (US and UK) and Merck and my experience was that the biggest problems were always at the beginning - and they usually were communication problems.
What I'm saying is successful outsourced projects tend to work things out as the teams adjust to each other. In no case will it work if you just throw some documents at each other - there needs to be face-to-face and key people need to know each other in any team. The payoff is, of course, the work then continues at a much lower cost.
Outsourcing may not be for everyone, but it does work well in a lot of cases. Just my two cents.
After that I kinda got lost until I discovered "The Info Directory" (C-h i). I just went through each item step by step and read most of it. Kinda painful but it gave me a really good feel for the entire system.
IMHO, though, there's not much point in switching from Vi to EMacs unless you do ELisp. Vi is a beautiful environment to work in but, with EMacs, you can make your environment behave practically in any way you want.
I've used this format when forming new teams and the 10 minutes the meeting typically takes is more than paid for by the increased communication. Plus it helps motivation - everyone can share daily progress and trouble spots.
The key to this working correctly is you've gotta drive it. There is a general agenda (share progress and discuss issues) but no minutes or note taking. This means you've got to keep track of everything in your head (the big picture). Then you get to decide - "Hey this is taking too long" or "We need in-depth discussion of this" or "X isn't communicating/contributing enough" etc etc...
Looking around my current office I see a lot of men and much fewer women. Of the men, I know quite a few who don't enjoy their work but stick it out cause they are the breadwinners and need to provide for their families. Maybe if they were given the option (socially and biologically?) of staying home with the kids they would do just that.
I went through the death of my brother many years ago and it was hard. Looking back, I did some stupid things and some good things. From my experience these may help you:
* Acknowledge your emotion. Cry when you need to. * Talk. The face-to-face conversations I had with my friends were truly life-saving. Even the times they didn't say anything. * Talking a stranger on a bus journey also helped in my case. There was something about it that also helped. * Spend some time alone in a place that you love. * Writing also helped a lot. I wrote a lot. Most of it without really thinking - just pages and pages of anything and everything. It was a great release.
Take care.