2012. május 10., csütörtök
2012. január 28., szombat
Facebook interview
I don't want to whine, but this bugged me so fucking much that I could not let it go. Let's hope this post gets it out of my head.
Short background: One of my friend got into facebook, and relocates to Dublin. He gave the word to the HR inside, to call me up. Knowing how good this'd look in my resume I said yes.
The interview: Next day after sending my resume, I got contacted by a guy on the phone. He had a horrible, horrible mic, even after we switched to skype. We negotiated a tech interview, there were very basic pre-screening questions. I had absolutely NO IDEA what I was going to do at facebook, even though I poked around and eyed a pretty sweet-sounding ITSEC-related position. I told this to my friend, who said that I should not worry, they'll help me figure it out. With the HR person we concluded that he did not even heard of the ITSEC position (wtf), and he's going to ask around. He suggested that we should move forward with an Operations position, and he'll come back to me. I'm absolutely NOT an Operations guy, even though I used to work as one. Well, hell - I thought - what bad could happen managing these servers. At least I can be with my friend, see the World somewhat and spend time on what I like doing (no, not really, I'm over apache.conf). At least it'd look good in my resume. Oh, by this time I was really hoping that I'd get in, my friend really brought my hopes up, how great it'd be and all that (fell for it like the idiot I am).
Well the second interview came, with a completely different person, never heard from the first one again, not to mention the ITSEC position. I said I prefer skype (because of the bad microphone incident - skype was somewhat better), to which they said, ok, but with skype I'll need a webcam (double handed facepalm).
I was online at the given time, being a little sleepy, I knew it was a BASH & Python interview. I was a little dumber than I usually am, possibly because I wasn't warmed up and a little nervous, no clue why. Anyway, the nice young engineer introduced himself briefly and asked me to not use google nor man nor anything (wat?). Ok, I said, how hard could it be? He asked pretty straightforward questions, to which I mostly gave the good answers... eventually. We shared a collab text editor where he could see what I was typing and all that. I usually don't like people staring at my screen and watching me work, so this naturally made me extremely uncomfortable. To be able to understand this, you have to know that my process is this: I put together the first workable - buggy as shit - first solution. This helps me understand the problem better. I test it, and then refactor it until I arrive at a solution that I'm comfortable working with and what works correctly for all use cases. I sometime add features at the very end. So I started to work out the solution to each problem in a hurry as I could see that he was very nervous and this was the last place he wanted to be right now. Well let's say this did not help me at all, but eventually we arrived at the correct solution. Oh, the questions were to be best solved in BASH, so I went with it, even though python would've been a much better alternative. I have to say, what bugged me most is that he made a scorning face every time I typed in my initial drafts. He was fucking condescending and arrogant about it, he even tried to convince me that subprocesses are spawned EVERY time bash runs a loop body. Oh, and the file field parsing problem' scalability issue's solution was not writing it in C (which I suggested, as you'd have to look at every byte eventually), but using mapreduce. "Have you ever heard of MapReduce?" - was the original sentence if memory serves well. Well, imagine why I did not jump to that conclusion immediately.
Although I lived this as a Huge Fucking Personal Failure I learned a lot from it I guess. So a few advices for interviewers (I conducted quite a few interviews recently, so I'm not just babbling like a 1-year old).
- Don't go to an interview if you're not absolutely DYING to get in. They'll be usually offended by that fact that they're not the centre of the World.
- If they don't know about a position and offer another one, don't fall for it, they're just after whatever the BIG MAN said, or they're after commissions.
- Don't get your hopes up. Helps with the interview, helps if you get rejected. You can be hyped up once you're there.
- If they're looking for a webcam or a picture resume, turn them down. It's to discriminate you. They're not looking for fashion models are they? If they say that they don't discriminate, don't believe it. Do you trust your program's inputs? Yeah, that's what I've tought. The best approach - which I admire - here is Google's: they ask you to remove all details that might get you discriminated (age, name, nationality, languages spoken, gender, etc...). They say, that if you're good they don't care. Exactly as it should be.
- If they ask you to code on paper and not use help, that just might be a very bad sign of Elitism/Snobbism. Don't get me wrong, they're entitled to gauge your performance using any way really. This will not get them the best people though and will leave a lot of applicants with bad feelings. The point in REAL programming (not the robotic, boring kind) is not knowing the most trivia. Also not about answering (in the shortest time possible) the most of the interviewer's favourite question's about your language's most intricate implementation details. (This is actually a HORRIBLE, INSANE method, seen it's potential before - at scaring away every talented individual.)
- If they're Snob, fuck them. Let me reiterate. You simply don't want to work somewhere where the Seniors go to sleep every night knowing that they have the people who could do an arbitrary test in the best way. Tests are just that: tests. They can not possibly cover every scenario. Not even counting the people who make lots of silly mistakes, but every now and then make it up with a HUGE idea. Those are the valuable people, not the robots that know the manual by heart. They are cogs in the system that are not creative, but are obedient and easily replaceable. Don't be a cog. Think of Einstein the next time you make a silly mistake, he made them all the time. It didn't kept him from changing our view of the universe.
Facebook: If you really choose an Engineer to do the interview, at least train him to communicate, be polite and not arrogant. If he makes faces, asks ambiguous questions, and interrupts my sentences/tasks early, I will not make be a happy camper. Oh, if he flat-out knows after the first question that I'm not a fit don't do the long dance of uncomfortable questioning, just tell me: I'm out.
Other interviewers: Don't be assholes. If I learned one thing, is that I remembered how does it feel when one is looked down on. Doesn't feel good. Don't make the mistake of not respecting your interviewees, even if they're clearly not a fit.
(Special big middle finger goes to those agents and headhunters that promise to call you back but do not. This in my opinion is one of the most illogical, yet bad insult that these people make all the time. If you don't make money off of me then I'm unimportant? Ok, let's make the fireman and the doctor think this the next time you're in trouble. Also I will not forget to keep your phone ringing at 2am for a week after an incident like this. Or dragging your ass out of town for a 45 minute ride to get an extremely good deal.)
My lessons: If a guy looks dumb and can't solve a simple task, don't immediately label him as an idiot. I sometimes do that. I needed to stand on the receiving end to realize that this is VERY bad. One not being able to do a task satisfactorily might not mean that they're just that. Both incentive and intention are important. The guy might just have a bad day. I'm not saying to keep such a person on if it's not working. Merely stating that thinking negatively of someone will put pressure on them which in turn will result in more negativity. It's a spiral of hostility and misunderstanding.
Guys, sorry about this I may have just got my period. What do you think of all this, I'm really interested in your opinion. Also would be cool to find out that I'm not just a rambling madman talking to himself. Thanks.
synapse
Short background: One of my friend got into facebook, and relocates to Dublin. He gave the word to the HR inside, to call me up. Knowing how good this'd look in my resume I said yes.
The interview: Next day after sending my resume, I got contacted by a guy on the phone. He had a horrible, horrible mic, even after we switched to skype. We negotiated a tech interview, there were very basic pre-screening questions. I had absolutely NO IDEA what I was going to do at facebook, even though I poked around and eyed a pretty sweet-sounding ITSEC-related position. I told this to my friend, who said that I should not worry, they'll help me figure it out. With the HR person we concluded that he did not even heard of the ITSEC position (wtf), and he's going to ask around. He suggested that we should move forward with an Operations position, and he'll come back to me. I'm absolutely NOT an Operations guy, even though I used to work as one. Well, hell - I thought - what bad could happen managing these servers. At least I can be with my friend, see the World somewhat and spend time on what I like doing (no, not really, I'm over apache.conf). At least it'd look good in my resume. Oh, by this time I was really hoping that I'd get in, my friend really brought my hopes up, how great it'd be and all that (fell for it like the idiot I am).
Well the second interview came, with a completely different person, never heard from the first one again, not to mention the ITSEC position. I said I prefer skype (because of the bad microphone incident - skype was somewhat better), to which they said, ok, but with skype I'll need a webcam (double handed facepalm).
I was online at the given time, being a little sleepy, I knew it was a BASH & Python interview. I was a little dumber than I usually am, possibly because I wasn't warmed up and a little nervous, no clue why. Anyway, the nice young engineer introduced himself briefly and asked me to not use google nor man nor anything (wat?). Ok, I said, how hard could it be? He asked pretty straightforward questions, to which I mostly gave the good answers... eventually. We shared a collab text editor where he could see what I was typing and all that. I usually don't like people staring at my screen and watching me work, so this naturally made me extremely uncomfortable. To be able to understand this, you have to know that my process is this: I put together the first workable - buggy as shit - first solution. This helps me understand the problem better. I test it, and then refactor it until I arrive at a solution that I'm comfortable working with and what works correctly for all use cases. I sometime add features at the very end. So I started to work out the solution to each problem in a hurry as I could see that he was very nervous and this was the last place he wanted to be right now. Well let's say this did not help me at all, but eventually we arrived at the correct solution. Oh, the questions were to be best solved in BASH, so I went with it, even though python would've been a much better alternative. I have to say, what bugged me most is that he made a scorning face every time I typed in my initial drafts. He was fucking condescending and arrogant about it, he even tried to convince me that subprocesses are spawned EVERY time bash runs a loop body. Oh, and the file field parsing problem' scalability issue's solution was not writing it in C (which I suggested, as you'd have to look at every byte eventually), but using mapreduce. "Have you ever heard of MapReduce?" - was the original sentence if memory serves well. Well, imagine why I did not jump to that conclusion immediately.
Although I lived this as a Huge Fucking Personal Failure I learned a lot from it I guess. So a few advices for interviewers (I conducted quite a few interviews recently, so I'm not just babbling like a 1-year old).
- Don't go to an interview if you're not absolutely DYING to get in. They'll be usually offended by that fact that they're not the centre of the World.
- If they don't know about a position and offer another one, don't fall for it, they're just after whatever the BIG MAN said, or they're after commissions.
- Don't get your hopes up. Helps with the interview, helps if you get rejected. You can be hyped up once you're there.
- If they're looking for a webcam or a picture resume, turn them down. It's to discriminate you. They're not looking for fashion models are they? If they say that they don't discriminate, don't believe it. Do you trust your program's inputs? Yeah, that's what I've tought. The best approach - which I admire - here is Google's: they ask you to remove all details that might get you discriminated (age, name, nationality, languages spoken, gender, etc...). They say, that if you're good they don't care. Exactly as it should be.
- If they ask you to code on paper and not use help, that just might be a very bad sign of Elitism/Snobbism. Don't get me wrong, they're entitled to gauge your performance using any way really. This will not get them the best people though and will leave a lot of applicants with bad feelings. The point in REAL programming (not the robotic, boring kind) is not knowing the most trivia. Also not about answering (in the shortest time possible) the most of the interviewer's favourite question's about your language's most intricate implementation details. (This is actually a HORRIBLE, INSANE method, seen it's potential before - at scaring away every talented individual.)
- If they're Snob, fuck them. Let me reiterate. You simply don't want to work somewhere where the Seniors go to sleep every night knowing that they have the people who could do an arbitrary test in the best way. Tests are just that: tests. They can not possibly cover every scenario. Not even counting the people who make lots of silly mistakes, but every now and then make it up with a HUGE idea. Those are the valuable people, not the robots that know the manual by heart. They are cogs in the system that are not creative, but are obedient and easily replaceable. Don't be a cog. Think of Einstein the next time you make a silly mistake, he made them all the time. It didn't kept him from changing our view of the universe.
Facebook: If you really choose an Engineer to do the interview, at least train him to communicate, be polite and not arrogant. If he makes faces, asks ambiguous questions, and interrupts my sentences/tasks early, I will not make be a happy camper. Oh, if he flat-out knows after the first question that I'm not a fit don't do the long dance of uncomfortable questioning, just tell me: I'm out.
Other interviewers: Don't be assholes. If I learned one thing, is that I remembered how does it feel when one is looked down on. Doesn't feel good. Don't make the mistake of not respecting your interviewees, even if they're clearly not a fit.
(Special big middle finger goes to those agents and headhunters that promise to call you back but do not. This in my opinion is one of the most illogical, yet bad insult that these people make all the time. If you don't make money off of me then I'm unimportant? Ok, let's make the fireman and the doctor think this the next time you're in trouble. Also I will not forget to keep your phone ringing at 2am for a week after an incident like this. Or dragging your ass out of town for a 45 minute ride to get an extremely good deal.)
My lessons: If a guy looks dumb and can't solve a simple task, don't immediately label him as an idiot. I sometimes do that. I needed to stand on the receiving end to realize that this is VERY bad. One not being able to do a task satisfactorily might not mean that they're just that. Both incentive and intention are important. The guy might just have a bad day. I'm not saying to keep such a person on if it's not working. Merely stating that thinking negatively of someone will put pressure on them which in turn will result in more negativity. It's a spiral of hostility and misunderstanding.
Guys, sorry about this I may have just got my period. What do you think of all this, I'm really interested in your opinion. Also would be cool to find out that I'm not just a rambling madman talking to himself. Thanks.
synapse
2012. január 7., szombat
Odesk programming test review
Hey guys,
Today I did an Odesk programming test (C). 40 question multiple-choice test in 40 minutes.
I scored 3.5 out of 5. Pretty lame huh?
It required to know a lot of trivia, which is fine as long as it asks the right questions. Mostly it did not, some questions were straight outrageous and would not compile with -Wall. Why is that bad you ask? Because it is Undefined Behavior, and you can NOT give a definite answer to it (at least a portable one), mostly it works consistently and predictably on x86 but is not guaranteed to work on another machine architecture.
All in all it was not so bad, but it proved once again that using multiple-choice tests to evaluate programmers is worthless. It can not measure the thinking ability and creativity of the person, it can only measure how much trivia one knows about the subject. Trivia that can be looked up in seconds...
synapse
Today I did an Odesk programming test (C). 40 question multiple-choice test in 40 minutes.
I scored 3.5 out of 5. Pretty lame huh?
It required to know a lot of trivia, which is fine as long as it asks the right questions. Mostly it did not, some questions were straight outrageous and would not compile with -Wall. Why is that bad you ask? Because it is Undefined Behavior, and you can NOT give a definite answer to it (at least a portable one), mostly it works consistently and predictably on x86 but is not guaranteed to work on another machine architecture.
All in all it was not so bad, but it proved once again that using multiple-choice tests to evaluate programmers is worthless. It can not measure the thinking ability and creativity of the person, it can only measure how much trivia one knows about the subject. Trivia that can be looked up in seconds...
synapse
2012. január 6., péntek
Python for humans
Remember that I was bitchin' about Python's HTTP support?
Along came Python for Humans from Kenneth Reitz. Enjoy!
If you're reading this Kenneth: Thank you very much!
synapse
Along came Python for Humans from Kenneth Reitz. Enjoy!
If you're reading this Kenneth: Thank you very much!
synapse
2011. november 10., csütörtök
Python3 list of lists or multidimencional lists
Well, I'm not proud. I've successfully spent half an hour debugging a small code snippet and narrowed the problem down to this:
>>> a=[["X"]*2]*3Printing it is fine as you can see, but after assignment you get this:
>>> a
[['X', 'X'], ['X', 'X'], ['X', 'X']]
>>> a[1][1]="Y"As it turns out the asterisk/star operator does not create a new list, but only a reference. Instead, to stay sane you can do this which works as expected:
>>> a
[['X', 'Y'], ['X', 'Y'], ['X', 'Y']]
>>> a=[["X" for x in range(0,2)] for y in range(0,3)]Not that pretty, but it gets the job done. Now, back to work.
>>> a
[['X', 'X'], ['X', 'X'], ['X', 'X']]
>>> a[1][1] = "Y"
>>> a
[['X', 'X'], ['X', 'Y'], ['X', 'X']]
2011. november 9., szerda
Python SSL [UPDATED]
Fuck me running. No version of Python (nope, not even 3) supports proper SSL and TLS. Not checking with OCSP is one thing (though bad enough), but that the default http libraries doesn't support it is a complete clusterfuck. The ssl module is good for it, but httplib and urllib have no means of using proper HTTPS, instead they opt for: "This does not do any verification of the server’s certificate.". Well Holy Crap. How anyone in their right minds would use THAT for security?
Though not everybody in the Python world is an idiot: http://packages.python.org/HttxLib/httxlib.httxs-pysrc.html
synapse
UPDATE:
I quickly hacked together a seemingly better HTTPS object, which you can use with httplib. It checks the cert's hostname and notAfter, so it should be more secure. I did not implement OCSP though.
UPDATEUPDATE: Thanks to blogger this is the proper link! http://pastebin.com/49zfGg9h
Though not everybody in the Python world is an idiot: http://packages.python.org/HttxLib/httxlib.httxs-pysrc.html
synapse
UPDATE:
I quickly hacked together a seemingly better HTTPS object, which you can use with httplib. It checks the cert's hostname and notAfter, so it should be more secure. I did not implement OCSP though.
UPDATEUPDATE: Thanks to blogger this is the proper link! http://pastebin.com/49zfGg9h
2011. november 2., szerda
Resumes and programmers
As I promised I'm back. Well, not quite yet as I have tasty things brewing, but will try to make more time for the blog. Having said this let's move along:
Today's topic is resumes. I had the fortune to help out in a venture where looking at a LOT of resumes is essential. I'm not an HR person, but from looking at more than a thousand resumes so far I have a few points to make in retrospect.
#1 Don't make grammar / formal mistakes
Please take the time to double-check for grammar and spelling. Nothing looks worse than your life on paper riddled with misspellings and faulty grammar. If you're English is not native (as with my case) just use spellcheckers and proofreaders (preferably whose native language is English).
#2 Put your CV online
I know this sounds insane, but as long as you omit details such as phone, full name and street address, you should be fine. If you have signed NDAs, be careful not to violate them. A lot of people can find you this way, with easy searches. Make sure you create a separate mail for that if you want to tackle spam.
#3 Make your CV concise and detailed at the same time
First, introduce yourself nicely. For the person looking at your skill set it is much MUCH easier to figure you out by looking at a short bullet-point skill set. The is the first thing they'll look for. If they want to gather more info on a skill, they should have the option to look at a more detailed section, where you describe your past experiences. This doesn't have to be short, but it should be very concise and to the point.
#4 Make it as detailed as needed
Don't make a resume 12 pages long. Also don't make them 1 page long. A LOT of people omit very crucial details, like what they did and how. Being a "Senior Consultant" doesn't bring a lot of clarity. Even if you worked for Cisco. Everyone has seen idiots in leading roles so please don't rely on your fancy title to get a new job of that caliber. Need proof? For a while I was a "Lead of Media Platform Development" and before that an "IT-Security Specialist" for a tech company whose HR lady could not distinguish Java from JavaScript. Don't be like that. In the detailed section put in all the details necessary.
#5 Have a good karma
Be on linkedin, twitter, stackoverflow, quora and write a blog. If you work on something interesting, it is bound to be found. This is not completely necessary but ups the odds of being presented with opportunities and also helps you to be credible. If you are not exactly the George Clooney of the blogosphere, you should not worry. After a while people with similar interests and jobs will follow you and you'll make friends in no time. The next job offer will be from them.
#6 Write down what you're looking for
If you're looking for part-time offers or freelancing, make this very clear. If you're very good they'll harass you nonetheless, but it'll probably worth it.
#7 Forget LaTeX
Seriously. It is ugly. I can tell any PhD guy from the rest. It is called LaTeX. Get rid of it. I know this is a highly personal point (the whole post is), but I find it repulsive.
#8 Prettify
If you're a coder you don't have to make a resume full of nice pictures and pretty graphics. You're not a designer after all, you should sell yourself with your skills. But if you make it pleasant to look at (don't go overboard) you'll have a much higher chance of standing out. This is good if they're looking for someone who's creative. If you're in doubt, just leave it plain black and white, but make sure that it looks good. At least typography-wise. If you want to spice it up a bit, try different ideas and have a designer friend look at it. You can buy him/her a beer after.
Today's topic is resumes. I had the fortune to help out in a venture where looking at a LOT of resumes is essential. I'm not an HR person, but from looking at more than a thousand resumes so far I have a few points to make in retrospect.
#1 Don't make grammar / formal mistakes
Please take the time to double-check for grammar and spelling. Nothing looks worse than your life on paper riddled with misspellings and faulty grammar. If you're English is not native (as with my case) just use spellcheckers and proofreaders (preferably whose native language is English).
#2 Put your CV online
I know this sounds insane, but as long as you omit details such as phone, full name and street address, you should be fine. If you have signed NDAs, be careful not to violate them. A lot of people can find you this way, with easy searches. Make sure you create a separate mail for that if you want to tackle spam.
#3 Make your CV concise and detailed at the same time
First, introduce yourself nicely. For the person looking at your skill set it is much MUCH easier to figure you out by looking at a short bullet-point skill set. The is the first thing they'll look for. If they want to gather more info on a skill, they should have the option to look at a more detailed section, where you describe your past experiences. This doesn't have to be short, but it should be very concise and to the point.
#4 Make it as detailed as needed
Don't make a resume 12 pages long. Also don't make them 1 page long. A LOT of people omit very crucial details, like what they did and how. Being a "Senior Consultant" doesn't bring a lot of clarity. Even if you worked for Cisco. Everyone has seen idiots in leading roles so please don't rely on your fancy title to get a new job of that caliber. Need proof? For a while I was a "Lead of Media Platform Development" and before that an "IT-Security Specialist" for a tech company whose HR lady could not distinguish Java from JavaScript. Don't be like that. In the detailed section put in all the details necessary.
#5 Have a good karma
Be on linkedin, twitter, stackoverflow, quora and write a blog. If you work on something interesting, it is bound to be found. This is not completely necessary but ups the odds of being presented with opportunities and also helps you to be credible. If you are not exactly the George Clooney of the blogosphere, you should not worry. After a while people with similar interests and jobs will follow you and you'll make friends in no time. The next job offer will be from them.
#6 Write down what you're looking for
If you're looking for part-time offers or freelancing, make this very clear. If you're very good they'll harass you nonetheless, but it'll probably worth it.
#7 Forget LaTeX
Seriously. It is ugly. I can tell any PhD guy from the rest. It is called LaTeX. Get rid of it. I know this is a highly personal point (the whole post is), but I find it repulsive.
#8 Prettify
If you're a coder you don't have to make a resume full of nice pictures and pretty graphics. You're not a designer after all, you should sell yourself with your skills. But if you make it pleasant to look at (don't go overboard) you'll have a much higher chance of standing out. This is good if they're looking for someone who's creative. If you're in doubt, just leave it plain black and white, but make sure that it looks good. At least typography-wise. If you want to spice it up a bit, try different ideas and have a designer friend look at it. You can buy him/her a beer after.
2011. szeptember 15., csütörtök
Samba
Wasted 3 hours of configuring samba, only to find that you need you need to set "encrypt passwords" to yes, otherwise:
1) your server will not be found
2) you will not be able to access it using \\servername
3) you will get incredibly annoyed by iexplore.exe locking up while browsing the network
makes sense.
1) your server will not be found
2) you will not be able to access it using \\servername
3) you will get incredibly annoyed by iexplore.exe locking up while browsing the network
makes sense.
2011. szeptember 13., kedd
Oh for fuck's sake
The spare parts arrived (I had to pay $120 in taxes). Two hours later I completely repaired the laptop, now the touchpad works and with the new battery I can run for 4 hours. Only one thing is missing. The last hole where I were supposed to screw in the one screw I hold in my hand. I did everything right (at least I tried), but this little sucker remains. I hope it's from the previous backpanel, and I didn't forget something. Now that I come to think of it I didn't mess with important stuff (think heatsink), so I hope it'll be fine.
Oh, one last important note. This little journey took me $490 usd, the price of a lowend notebook. If you need to do this, try to bid on a broken notebook on ebay. I didn't have the time and patience, and as you can see I've paid the price.
synapse
Oh, one last important note. This little journey took me $490 usd, the price of a lowend notebook. If you need to do this, try to bid on a broken notebook on ebay. I didn't have the time and patience, and as you can see I've paid the price.
synapse
2011. szeptember 7., szerda
Dell laptop lifetime
Years ago I've bought a dell inspiron 1525. It was great until the point the touchpad stopped working after about a year (the buttons still work, design fail). Today the whole display fell apart, the METAL screws' holders were attached to the backside PLASTIC. These holders broke after about 3 years of (not so heavy) usage. The touchpad itself was an engineering failure, but for this solution I'm out of words.
SCREW YOU, Dell! I'm not buying any of your crap ever again. Yeah, and guess what? The wifi sucks bad, too (broadcom piece of crap). On top of all this I had to buy new hdd months ago, and my battery is on the verge of demise but these I can understand.
Just that I'd expect something more from a $2000 laptop and a company like that. I could get this quality from a manufacturer like Fujistu-Siemens for half the price. Hell, if it breaks I'll just buy another one. Really giving some thought of buying a unibody mac now...
synapse
PS: I'd really like this get to the first page of google, so you'd lose some real money assfaces.
SCREW YOU, Dell! I'm not buying any of your crap ever again. Yeah, and guess what? The wifi sucks bad, too (broadcom piece of crap). On top of all this I had to buy new hdd months ago, and my battery is on the verge of demise but these I can understand.
Just that I'd expect something more from a $2000 laptop and a company like that. I could get this quality from a manufacturer like Fujistu-Siemens for half the price. Hell, if it breaks I'll just buy another one. Really giving some thought of buying a unibody mac now...
synapse
PS: I'd really like this get to the first page of google, so you'd lose some real money assfaces.
Feliratkozás:
Bejegyzések (Atom)