I got rejected just this month and I can certify that there was no crazy bullshit in the process. I mean, I feel like you made a mistake rejecting me, but I also can imagine a valid process behind the scenes which would reject me based on my "ok but not great" performance. I do hear anecdotes from people I trust which sound crappy (being asked very specific technical questions on subjects that candidate doesn't have experience on and not being flexible about it, being rude etc).
1) His level of knowledge is reasonable for someone who does networking programming full time
2) We are getting description from him. When I interviewed at Google, they asked me to prove that P is equal to NP, and I did, but they said that it took me longer than allotted 45 minutes and I didn't get an offer.
Oh, cool. Can you expand on that? What kind of logic had to change? I mean, SQL queries are SQL queries? Is that because you were using low level C Oracle drivers of some sort?
Also if you could say a couple of words about the MySQL failure it would be rather helpful because I might have a friend who might be currently deciding on whether to migrate to MySQL or Postgres from Oracle.
it wouldn't have been 10 man years if they had less PL/SQL. I don't understand why people keep falling into that trap of putting complex logic in stored procedures.
I'm saying there was hope. I remember 2005. IE was getting better. Chrome/Firefox/Opera were close enough, once I got one of them working i barely had to do anything. So it was essentially targeting 2 platforms (IE and non-IE) and hoping IE would get fixed. Today that problem is largely solved, but we have created an unmanageable lasagna of complexity in the process.
ActionScript was all right, I don't disagree. Especially compared to JavaScript. But i think it would have been nice to have the same language on FE and BE.
it was a nightmare (because of the browser support), but it was a nightmare with a hope that it will get fixed (browsers will get better, there will be simple thin abstraction libraries added, etc).
Right, that too. For example, the amount of work that every serious web app puts into implementing some kind of hierarchical system for storing, naming and accessing objects and then allowing users to share them with each other is astonishing. If only there was a way to have the operating system provide some kind of similar abstraction to the users!
Sure, as said in other threads here -- large companies full of brilliant people can build good RIAs. Small companies full of OK people are suffering.
Java Applets security could have been solved. I'm not even sure what problem you are referring to exactly. With todays web we get insanity of XSSs, CSRF and who knows what else. The only reason these are not killing modern web development is because this hydra has too many heads.
Sure, that's possible, but not necessary. Devs might have been smart enough to stay away from extensions. Microsoft might have been smart enough to not push it too hard. Your example of ActiveX actual supports that -- ActiveX never became super widespread, remaining a niche thing. Also keep in mind that this was only few years before OS X was released bringing the 2nd consumer desktop OS back onto the market.
It is scary how most commenters here are missing the point. No, not all programming sucks. Yes, web programming sucks more than other things. No, it doesn't have to be like this. Yes, even web programming was better 10 years ago. No, I don't know how to fix it. Neither do I know exactly where we took the wrong turn.
One of my theories is this: had Sun not sued Microsoft over their extensions in JVM, MS would have kept working on their awesomely fast JVM implementation for Windows. That would make Java fast and not sucky in browsers. It would have kept Java Applets as a viable rich web app development option. Flash would have never risen. Java, being a significantly superior language to ActionScript, would have allowed us to build nice RIAs in an efficient, secure and portable way. Gmail and Google Maps would have been implemented in Java. Isometric Java. Get it? Get it? Back end and front end are written in the same language with strong typing and all that. JavaScript would have been dead by now. World would have been a better place.
I suspect they are talking about metadata pieces found in the Office documents. It could serve as a relatively strong proof that documents where processed by someone at least Russian-speaking.
What makes you think they failed terribly? We haven't seen full analysis (or much of anything yet), but there are mentions of potentially specially targeted malware. Very few organizations will withhold a direct targeted attack by a government which possesses zero days and resources to hand craft attack software and can find personal information of specific people attacked.
Oh totally. I assumed that unicode bs immediately. And anyone would make this mistake easily. That's the point -- gotta have it imprinted in the brains, that regexes are for finding things in files, not for your production code.
I've used them myself, but I'd like to think that when i type that regex in i stop and thing whether i will be feeding raw user inputs into it.
maybe it a cry for help? Someone "accidentally" left a single https request there, hoping google will redirect North Korean requests to an open proxy allowing them full access to the Web.
Frankly I don't understand what are these terrible secrets that people are comfortable sharing on a public web site for everyone to see, but not comfortable with everyone seeing them. I just fail to see the pain. Discomfort, sure, but pain and suffering?
Making something viewable by a group of selected people is one thing; making something viewable by millions of users of a website with a free and simple account creation mechanism should be equivalent to making it public in people's heads.
I dislike them as I dislike all human activity which doesn't produce useful good or services; probably more so as these are probably harmful and parasitic. But I'm not sure how this is related to the subject at hand.
Another bad analogy.
1) In public places I usually speak at the volume level at which others can't hear me; if I start yelling in a public place I should expect things that I yell to appear on youtube, in the local newspaper, in the police log
2) I come to the restaurant to eat. If after eating I fill out a survey which includes lots of personal possibly identifying questions, would I have the right to be surprised if next day I find my answers on the website of the restaurant? Have I read the fine print on that survey?
Terrible analogy. You are putting your money into the bank in order for the bank to preserve the money and perhaps pay you interest on it.
When you use a website like OKCupid, you are getting a service from them in exchange for ability to mine a sell personal information about yourself. And, amazingly, this will lead to... people getting your personal information. The lack of public understanding of this is precisely what makes a dump like this ethically gray. Sure, it's bad that people's information leaked, but at least it wasn't for profit and overall public is better off because more people understand how data works.