If we're not able to attend but would like to submit our resume to the YCombinator companies, is there a good place to do so? I'd be tempted to submit my resume via the application, but it doesn't seem fair to the startup companies to have to sift through resumes from people unable to attend.
HN user
bluefish
Where does this nonsense come from? I can't take being silent and just flagging anymore. This is exactly The kind of story that made me stop reading digg then reddit... I really don't want to finish that sentence with Hacker News. I don't care if these stories are submitted but I do care that there is an opaque process around how I can make my actions against these stories more effective. I would also like to know the general stats about the community. I wonder if this is just a natural communal process as the community grows or a flaw in the structure of the community design.
Thank you. I'm glad I'm not the only one annoyed by the "7 degrees of hacker news" story stretch.
While interesting speculation, I don't understand why we've frontpaged this story on a community site generally focused on technology, startups and hacker culture. I'd love to see this on a community site called UnsolvedMysteryNews, but until one exists, flagging for relevance.
Have to agree. In general, as much as I like most of these alt stories that have been posted to HN lately, I came to HN to escape this sort of posting. I'm sure we could expand the term 'hacker' to apply to anyone who was a creative misfit in their field; ingenious doctors, writers ahead of their time, one-handed clock makers, etc but that's not what I consider a hacker in the context of this community. Still, would love the alternative with links like this as a companion site to HN.
Minor quibble from my 1st impression: Not really into the signin / signup form. From a usability perspective it just seems like it deviates a lot from what most users are familiar with. I like the narrative take on signin / signup but I think it would work better if the underlined sections were typical input boxes.
use it yourself, "eat your own dogfood" or however you would like to describe it. That's the most important one for me. If you're not using it to solve your own problems then what are you building it for?
Agreed. You really need to read the CL TOS and make sure you're working with CL to use their data.
Your tough-love approach "...that's life, life is not fair, deal with it" is completely misguided and naive. I certainly hope that if you ever have children you don't use that mindset on them when they come home bullied, frustrated or upset.
As someone who works on a project with a team of dedicated engineers under fairly strict code guidelines including code reviews, I can tell you from experience none of these factors have to do with "code cleanliness" (as ours is not, at least in my opinion).
It would be an interesting legal case to say the least, especially because they do not indicate that they will provide further information about the warrant, or how to act other than individuals should "take special notice".
Still I believe you are correct, by having a publicly stated policy about their planned inaction when served a secret warranty is effectively the same as making a public announcement. Ballsy, but kudos to them for making a statement about their privacy beliefs.
Anyone use(ing) Potion for something other than just playing around with the source?
Have to agree. I really like the new Apple keyboards. They feel minimalist but with enough key travel that I know when the button has been fully pressed.
Frankly, it's what you would expect from them. An abuser doesn't stop beating when you confront him; he stops beating you when you leave.
I'm not an iPhone developer, nor have I ever developed anything for the Mac platform specifically. Based on the stories I've read online it does sound like Apple isn't handling their iPhone app store well, but I do take issue with the part of your comment I've quoted.
I'd like some examples about why you would expect to be treated poorly (or as you put it abused) by Apple. Is it only based on their track record with app developers? If so perhaps it's a problem rooted in the iPhone app process itself and not systemic to the whole company, as you imply. I would need more examples of Apple's abusive policies to understand your statement, for now though I'm not going to write off Apple as horrible corporation because some app developers cry foul (to which, according to the blogger's own admission, Apple attempts to promptly respond to and rectify).
Agreed. My "real world" view involves avoiding Outlook any time I can, including business contexts.
If you think it's a dup, flag it. I'm tired of seeing these digg like dup comments. They come across as a power grab for community recognition and karma, not for bettering the content on the site.
I played around with node last night a bit more. Here are one noob's observations:
For most things it feels pretty fast. A simple timer output showed less than 1, 1, 2 or 3 milliseconds for most operations including File I/O.
Importing files via node's 'import' and 'require' functions is, for lack of a better adjective, Erlang-ish. You must declare in the file you are importing which functions you would like to expose by making them members of a special object called 'exports'. For example if you have a factorial function in a file called factorial.js you must declare it as 'exports.factorial = function() { ... }'. This seems 1) strange, 2) not very Javascripty and 3) like it can severely limit the reuse of server-side js libs with other server-side and non-server-side js implementations. This was the biggest let down for me, since my dream is to be able to write libs that work on both the client and the server.
There was a weird bug I found when writing to a file. If I created a loop like so:
var times = []; for (var i=0,j=1000; i<j; i++) { var t1 = Date.now(); var file = new node.fs.File(); file.open('test.log', 'a+'); file.write(i + ' ' + new Date() + ' Hello World!\n'); file.close(); times.push(Date.now() - t1); }
'file' would contain only 250 new lines of text, while the array times would show it's length to be 1000. I'm assuming this is some kind of bug, as the number of new lines added to the file seems fixed at 250. Setting the loop to 249 produced a times array with 249 items and a file with 249 new lines. Setting the loop to 251 produced a times array with 251 items and a file with 250 new lines. My C++ is very poor, but my guess is that each event has a queue which is hard coded at 250 and my loop over flowed the queue. This could also be a potentially huge issue with writing libraries around node.
It would be nice to see those two issues resolved or explained in better detail, particularly the import / export functionality.
Built it without a hitch on a Mac. Ran the demo which seems clean and pretty snappy.
I'm not familiar with how other libraries might be implemented, like mysql, sqlite, etc so I guess I'm wondering if this implementation will eventually support external libraries. Also wondering how node compares to, say, narwhal:
http://github.com/tlrobinson/narwhal/commits/master
which seems to be more of a std lib than a full runtime. Also, can narwhal be imported by node?
All in all, really exciting. I've been wanting js on the server forever.
This is something I've wanted to work on for months, but I lack the EE experience to do the physical side of things. Great to see it happening though.
Some people really need to be on the offensive to get things done. They need to feel like someone else is the enemy and they are going to defeat them. It seems to me like Zed puts himself in the position of David vs the open-source-community-Goliath on purpose so that he can be on the offensive. He gives himself an enemy, throws down the gauntlet and declares that he can and is going to make things better. I'm not one to argue that he picks the best motivational targets, calling people out and demeaning a hard-working community seems pretty negative, but damn when Zed says he is going to deliver, Zed delivers. Laser focused, intelligent and hard-working. I would love to work with Zed, hire him or have him contribute to one of my projects, but damn, I'd be terrified of pissing him off.
Why working at a startup? You have an image of an ideal that may be a fallacy. I work at a startup and it's not all fun and games. 1) It's a lot of work, 2) there is a lot of bureaucratic red tape (just like any real world business environment) 3) startups are more fluid and flexible, meaning they can succeed quickly, but fail just as fast. My point being that it's not fun to watch your friends get fired because the startup suddenly cannot pay them anymore.
Perhaps what you meant was "Working on my startup." To which I would agree. If I could be doing anything right now it would be working on my own projects and working towards being able to sustain myself through the application of my own skills. Perhaps that's not what you meant, but heed my warning, startups are not a panacea for programmers.
This is all typical technology-is-killing-society-and-making-you-stupider bombastic drivel. When the mail system was instituted in the US a part of the population claimed it would be the end of modern society. That it would eliminate face to face interaction and increase indecency as a delivery method for porn (it did do the latter). Same with the telephone. But here we are, Twitter isn't going to destroy society, make us stupider or less passionate. It's just another way of receiving information. In 140 characters.
The article was posted on Sept 11, 2006. Let's let it go.
> Rails stuff is almost, but not quite, entirely unlike Ruby.
I really like Python and have the exact opposite opinion as you. That is, to me, Rails is very like Ruby and Django is unlike anything else done in Python. Django has hindered me every time I've tried to use it. By comparison, Cherrypy, storm-orm, SQLAlchemey, Mako, etc are all pretty straight forward. Django is out in left field for me.
For me, there are two qualities I look for when hiring an outside service provider like an accountant which go beyond the $/hour perspective.
1) I assume my time is essentially priceless. If I've ever had complex finances, for example, I hire an accountant because it's not worth me trying to decode some obscure tax law (which commonly changes year to year btw) for several hours just for the satisfaction of knowing I've DIY'ed the situation and maybe saved a couple of $ in the long run, while quite possibly also having had made mistakes.
2) Speaking of mistakes, the second reason is that often times hiring someone else comes with some kind of guarantee or warranty. Hire an accountant and if your taxes aren't right you're liable to make up the error, but you're not going to jail for tax fraud. Hire an electrician and (usually) they'll stand by their work and come fix errors within a given amount of time.
Not saying I disagree with your statement, just offering a perspective on why $/hour doesn't always evaluate so clearly as a meaningful metric.
Your argument is ineffective. The point is not to swap one potentially controversial topic for another in a presentation, the point is to attempt to appease a majority of the audience in an entertaining way precisely by avoiding abrasive topics.
Using POST doesn't necessarily make it simpler to defend against CSRF. You still need to use some kind of exclusive token shared between the client and server (e.g. a session id stored in a cookie). Imagine a poorly implemented site that doesn't prevent users from uploading js script blocks into the comments. A user could upload a script that creates a form and submits it via POST to your POST restricted endpoint, thus circumventing POST only protection. I'm assuming I've misread your comment as you use POST only and you're also doing proper CSRF protection right?
This is also known as Cross Site Request Forgery or CSRF: http://en.wikipedia.org/wiki/Cross-site_request_forgery
Very very helpful, especially as someone who still has to work in ie6 and 7. I've been trying to set this up for some time and have never found a good, straightforward tutorial regarding how to get this working.
Having a background daemon running to automatically update software without informing the user is a poor solution, but trying to solve the problem introduced by checking for updates on startup and thus interrupting the workflow of the user is a good idea.