What is rather odd is that I did not buy or sell anything for several years after that incident.
However, recently I have been buying a lot of stuff that costs $2-3 including shipping.
It really beats me how this sales model makes sense to anyone.
Many years ago I disclosed a vulnerability to Ebay to get any user's email.
It took 2-3 hours to talk to their tech support and convince them that this is a serious problem. I had to show multiple examples of telling them emails of users randomly picked by tech support. Eventually they closed the hole. Within 12 hours actually, which was not too bad.
Several years later, when I had some issues with Ebay, they did not want to take that help into account.
Ebay & Paypal had so many changes over the past 5 years and pissed off a lot of people as a result. No wonder someone went public with the issues. I used to have multiple power seller accounts, and after all these changes I stopped selling there.
If I saw a vulnerability now with either ebay or paypal, I'd not bother telling them. I'd actually just wait for a story like that and laugh at them from a perspective of what goes around - comes around.
Actually, I was laid off once because of a very similar situation.
1. Found a very expensive computer in a trash
2. Notified the manufacturer with all serial numbers.
3. Used work email
4. Half a year later some a*hole comes with a police officer to my work and accuses me of stealing it.
5. Next day I am laid off.
Had another somewhat similar issue where I disclosed a serious vulnerability to a company where any
user email could have been looked up through a certain web page. When I needed their help on an issue
I had with their services - I got nothing back.
The lessons I learned - if I first see some cooperation from actual developers and not management/support a*holes,
I cooperate as well and report any issues I find directly to developers. If I do not see such cooperation - I do not
tell anyone about issues. Coincidentally, the company I currently work for, cancelled the last service where I found
some issue, and the CTO of the company was rather negative about what I was doing. Hopefully he'll learn to be
more cooperative in the future.
I have been doing daily reports for a while.
The way I do them - I keep an excel file where I have a column for a short summary of what I worked on during the day.
If I had an issue and it needs to be fixed - I will write it there too.
At the end of the day I'd send an email to my managers with a summary of what I did. Usually no more than 2 3-line paragraphs.
What this really helps me with is to make sure management sees that I actually produce or research a lot each day.
This also makes me want to complete things by the end of the day as opposed to leaving them for the next day.
I worked there in 1998 as an intern. Had many issues with management.
Yet, inspite of all the problems, it is a REALLY GREAT PLACE TO WORK. From a developer's perspective, you meet extremely smart people. And their suggestions potentially influence your development many years after.
The best thing that I saw was that Microsoft really values smart people and they will keep them at any cost not letting them leave. Very few companies do that. Most today's companies are just concerned with the rate per hour and all this crap which results in insane turnover and crappy productivity. Microsoft actually gives generous raises to those who really produce. And employee turnover in 90's was much lower than any other company.
The werst problem that seemed at the time was an insanely redundant chain of PMs. One would be responsible for the product, another for graphics, another for future localization and who knows what. The guy responsible for UI layout (in my particular case) was there for at least 10 years. Paid a lot and design stuff completely inconsistent with any other Microsoft product. Every time I would mention multiple examples from the most popular products like Windows itself or Office, I would be told that it's not my job. Yet his "design" looked like sh*t. Another really smart developer (who eventually became architect and evangeliest) told me he had the same issues with him. That PM always "worked from home" and never showed up.
It is very likely that such PMs were the ones who brought all this mess to the company that we see now. Yet, purely from software development perspective and learning from co-workers it was an amazing place.
You are probably doing much more involved things than I do. I still have a full time contract making money. The stuff I described were just short-term projects. usually in C#. Worth just couple of K each.
But from the same perspective of having "first steps" - I suggest a lot of people to start with Elance/Odesk when they are looking for a cheap way to do a project.
The idea is - if you are lucky - you get something done. If not, for just $1-2K you learn what not to do in the future. So it's still an inexpensive way to learn how not to waste more money later.
They usually try to quote on a project at about $10-20/hr and say it takes several weeks. I usually offer a demo by the end of the day and then a discussion on the total project cost. Sometimes this does involve working a lot and really fast. However it really blasts India out of equation after the demo since the most important question that comes after the demo "why did they ask for several weeks when someone else did most of it in one day".
I only did it twice successfully, but if you feel like you are bidding on a small/medium project against India, keep in mind that the way they try to outsource is by extending the development time to bill more or account for slow developers.
That's what I thought because I was in an INSANELY SMALL NICHE on my full-time contract. It was a C++ COM Internet Explorer Plugin DLL programming. Guess what? My new contract is pure C#, not even a single line of P/Invoke, some minor reading of legacy C++ MFC app is needed. Pays more.
Although this goes along the lines of 3 other minor projects I was doing besides the main contract.
To me it looks like even if you are super specialized in some areas, but work on small projects in others - you are still super valuable.
do not necessarily have the exact skills needed for the job today.
Which, in turn, means taking less of a "Just In Time" attitude to hiring. Good workers are not items you can order off the shelf, along with a desk, a chair, and a PC.
There's a flaw in this logic. If everyone was trainable in the same way - it'd make sense. However, usually those who have more relevant experience and who want to be paid more because they have a lot of successful projects in the past are usually the ones that can train a lot faster. At my current contract, I was hired together with another guy at roughly the same rate (difference was only 10%). The project was speced for 3 months. Within the first week I already delivered an important component while the other guy couldn't even produce a demo of another part.
Eventually 3 weeks into the project we talked with the manager and he decided to get rid of the other guy because his lack of knowledge and learning abilities were quite bad. It took less than 2 days to do what he was trying to accomplish in 3 weeks.
I've seen the same before with a drastic difference in abilities between people paid similarly quite often. Usually those with more skills learned a lot faster or produced better code.
I just switched jobs and got a higher pay too. About 20% raise.
In fact, I wanted a raise at previous job, they decided to terminate my contract instead of paying. I thought of just staying home and relaxing for a while working on small projects. Got a call from 2 recruiters for 2 companies on the same day, and started working in whichever gave offer first.
The way I usually agree to work is first few months at mutually acceptable rate, and then at the rate I want in the first place. Worked OK so far.
One thing I also realized - if you see that you consistently produce more work that 2-3 other people in your team combined, and all of you are paid about the same - you are definitely worth the raise.
Glossy or matte is just part of the problem. The bigger problem that actually hurts eyes is increasing color temperatures of both colors and the backlights.
Effectively this leads all colors to appear more blue. Our brain perceives it as much brighter and from a distance we think the display with more bluish temperature looks a lot brigher. Now an older display with yelowish or reddish tint will look "old" right next to the new bluish one.
The problem is - when you sit infront of a screen with bluish colors - a lot of the times it hurts eyes because this is not quite the same as daylight that we are used to. You can go into graphics properties, adjust color temperature (or decrease gamma/brightness/contrast for blue) and see the difference. The colors will not be as good. If your TFT panel is a "thin-film" type you will also get different color reproduction in the vertical axis, but it will be much easier on eyes.
You can also download a program called PowerStrip (free evaluation), run it with any new laptop, assume whatever the default is at 6500K and lower color temperature to be 5200-5600K - you will find that your eyes don't hurt as much.
----
Regarding the colors on the stand-alone LCD monitors - you have to make sure that LCD/TFT you get is IPS or PVA. They have the same colors across the vertical viewing angle. Thin-Film (TF) doesnt. DELL 2405 and 2407 are good ones. Dell 247 is not. FRY's doesn't sell any non-TF monitors. Best Buy only has 3 PVA monitors and most others regular TF. It just happens that TF technology is a lot cheaper to manufacture. As such people who notice the problem - suffer. Some people who don't have to sit in front of the monitor for 4+ hours straight would never notice.
I didn't imply typing. Everyone can type on a keyboard. I meant more like help with anything that needs multiple apps at the same time. I.e. switching between windows, copy-paste, button clicks and so on during some of the "intense" and fast multi-app sessions.
Especially helpful when you have dual screens and a mouse move from left to right requires lifting it and moving again. This adds about 1 second to navigation. Then consider clicking and so on - every app switch takes about 2-3 seconds...
If it has API it will rock as a secondary input system to mouse. You will be able to scroll through text/code just by looking, switch windows, copy paste - it has an enormous potential. Again, if it can be trained to work with 99.9% precision like a mouse.
I am sorry I only watched the first 3 parts. But I noticed he talks about voltages about 70V and currents about 5A which makes me beleive this is a 300-500W motor... the coils he has there will in no way produce 300W. Thus it is not a machine that will run on its own. In my pessimistic opinion the motor has a heavy rotor which has a lot of inertia continuing the spinning. Also notice the rather large wheel with magnets - also contributing to inertia.
Slashdot Mirror
What is rather odd is that I did not buy or sell anything for several years after that incident. However, recently I have been buying a lot of stuff that costs $2-3 including shipping. It really beats me how this sales model makes sense to anyone.
Many years ago I disclosed a vulnerability to Ebay to get any user's email.
It took 2-3 hours to talk to their tech support and convince them that this is a serious problem. I had to show multiple examples of telling them emails of users randomly picked by tech support. Eventually they closed the hole. Within 12 hours actually, which was not too bad.
Several years later, when I had some issues with Ebay, they did not want to take that help into account.
Ebay & Paypal had so many changes over the past 5 years and pissed off a lot of people as a result. No wonder someone went public with the issues. I used to have multiple power seller accounts, and after all these changes I stopped selling there.
If I saw a vulnerability now with either ebay or paypal, I'd not bother telling them. I'd actually just wait for a story like that and laugh at them from a perspective of what goes around - comes around.
Actually, I was laid off once because of a very similar situation. 1. Found a very expensive computer in a trash 2. Notified the manufacturer with all serial numbers. 3. Used work email 4. Half a year later some a*hole comes with a police officer to my work and accuses me of stealing it. 5. Next day I am laid off. Had another somewhat similar issue where I disclosed a serious vulnerability to a company where any user email could have been looked up through a certain web page. When I needed their help on an issue I had with their services - I got nothing back. The lessons I learned - if I first see some cooperation from actual developers and not management/support a*holes, I cooperate as well and report any issues I find directly to developers. If I do not see such cooperation - I do not tell anyone about issues. Coincidentally, the company I currently work for, cancelled the last service where I found some issue, and the CTO of the company was rather negative about what I was doing. Hopefully he'll learn to be more cooperative in the future.
On the video she doesn't really look like a supermodel. So tapping wouldn't really be of any sexual nature anyway.
I have been doing daily reports for a while. The way I do them - I keep an excel file where I have a column for a short summary of what I worked on during the day. If I had an issue and it needs to be fixed - I will write it there too. At the end of the day I'd send an email to my managers with a summary of what I did. Usually no more than 2 3-line paragraphs. What this really helps me with is to make sure management sees that I actually produce or research a lot each day. This also makes me want to complete things by the end of the day as opposed to leaving them for the next day.
I worked there in 1998 as an intern. Had many issues with management.
Yet, inspite of all the problems, it is a REALLY GREAT PLACE TO WORK. From a developer's perspective, you meet extremely smart people. And their suggestions potentially influence your development many years after.
The best thing that I saw was that Microsoft really values smart people and they will keep them at any cost not letting them leave. Very few companies do that. Most today's companies are just concerned with the rate per hour and all this crap which results in insane turnover and crappy productivity. Microsoft actually gives generous raises to those who really produce. And employee turnover in 90's was much lower than any other company.
The werst problem that seemed at the time was an insanely redundant chain of PMs. One would be responsible for the product, another for graphics, another for future localization and who knows what. The guy responsible for UI layout (in my particular case) was there for at least 10 years. Paid a lot and design stuff completely inconsistent with any other Microsoft product. Every time I would mention multiple examples from the most popular products like Windows itself or Office, I would be told that it's not my job. Yet his "design" looked like sh*t. Another really smart developer (who eventually became architect and evangeliest) told me he had the same issues with him. That PM always "worked from home" and never showed up.
It is very likely that such PMs were the ones who brought all this mess to the company that we see now. Yet, purely from software development perspective and learning from co-workers it was an amazing place.
I have a non-technical video related website. It has more than 1mln visits per month according to Google Analytics.
My stats for the past month are:
Chrome: 49.06%
Firefox: 21.36%
IE 15.65%
Safari 6.14%
Windows 85.65%
Macintosh: 4.56%
iOS: 2.56%
Android: 2.54%
But I do remember seeing about 30% IE last year. So there's a chance different non-technical sites attract different browsers differently.
For example, you have 3 times more Apple users than me.
MEMTEST the server for 24 hours. If you see any errors - it may be a hardware issue.
You are probably doing much more involved things than I do. I still have a full time contract making money. The stuff I described were just short-term projects. usually in C#. Worth just couple of K each.
But from the same perspective of having "first steps" - I suggest a lot of people to start with Elance/Odesk when they are looking for a cheap way to do a project.
The idea is - if you are lucky - you get something done. If not, for just $1-2K you learn what not to do in the future. So it's still an inexpensive way to learn how not to waste more money later.
I find it very easy to compete against India.
They usually try to quote on a project at about $10-20/hr and say it takes several weeks. I usually offer a demo by the end of the day and then a discussion on the total project cost. Sometimes this does involve working a lot and really fast. However it really blasts India out of equation after the demo since the most important question that comes after the demo "why did they ask for several weeks when someone else did most of it in one day".
I only did it twice successfully, but if you feel like you are bidding on a small/medium project against India, keep in mind that the way they try to outsource is by extending the development time to bill more or account for slow developers.
Sadly critical thinking, reason, and adaptability are lower requirements then being a code monkey that spews code that "gets he job done".
My exact arguments with everyone copy-pasting sh*t all over just to get the job done 2-3 minutes faster.
That's what I thought because I was in an INSANELY SMALL NICHE on my full-time contract. It was a C++ COM Internet Explorer Plugin DLL programming. Guess what? My new contract is pure C#, not even a single line of P/Invoke, some minor reading of legacy C++ MFC app is needed. Pays more.
Although this goes along the lines of 3 other minor projects I was doing besides the main contract.
To me it looks like even if you are super specialized in some areas, but work on small projects in others - you are still super valuable.
do not necessarily have the exact skills needed for the job today.
Which, in turn, means taking less of a "Just In Time" attitude to hiring. Good workers are not items you can order off the shelf, along with a desk, a chair, and a PC.
There's a flaw in this logic. If everyone was trainable in the same way - it'd make sense. However, usually those who have more relevant experience and who want to be paid more because they have a lot of successful projects in the past are usually the ones that can train a lot faster. At my current contract, I was hired together with another guy at roughly the same rate (difference was only 10%). The project was speced for 3 months. Within the first week I already delivered an important component while the other guy couldn't even produce a demo of another part.
Eventually 3 weeks into the project we talked with the manager and he decided to get rid of the other guy because his lack of knowledge and learning abilities were quite bad. It took less than 2 days to do what he was trying to accomplish in 3 weeks.
I've seen the same before with a drastic difference in abilities between people paid similarly quite often. Usually those with more skills learned a lot faster or produced better code.
I just switched jobs and got a higher pay too. About 20% raise. In fact, I wanted a raise at previous job, they decided to terminate my contract instead of paying. I thought of just staying home and relaxing for a while working on small projects. Got a call from 2 recruiters for 2 companies on the same day, and started working in whichever gave offer first. The way I usually agree to work is first few months at mutually acceptable rate, and then at the rate I want in the first place. Worked OK so far. One thing I also realized - if you see that you consistently produce more work that 2-3 other people in your team combined, and all of you are paid about the same - you are definitely worth the raise.
Glossy or matte is just part of the problem. The bigger problem that actually hurts eyes is increasing color temperatures of both colors and the backlights. Effectively this leads all colors to appear more blue. Our brain perceives it as much brighter and from a distance we think the display with more bluish temperature looks a lot brigher. Now an older display with yelowish or reddish tint will look "old" right next to the new bluish one. The problem is - when you sit infront of a screen with bluish colors - a lot of the times it hurts eyes because this is not quite the same as daylight that we are used to. You can go into graphics properties, adjust color temperature (or decrease gamma/brightness/contrast for blue) and see the difference. The colors will not be as good. If your TFT panel is a "thin-film" type you will also get different color reproduction in the vertical axis, but it will be much easier on eyes. You can also download a program called PowerStrip (free evaluation), run it with any new laptop, assume whatever the default is at 6500K and lower color temperature to be 5200-5600K - you will find that your eyes don't hurt as much. ---- Regarding the colors on the stand-alone LCD monitors - you have to make sure that LCD/TFT you get is IPS or PVA. They have the same colors across the vertical viewing angle. Thin-Film (TF) doesnt. DELL 2405 and 2407 are good ones. Dell 247 is not. FRY's doesn't sell any non-TF monitors. Best Buy only has 3 PVA monitors and most others regular TF. It just happens that TF technology is a lot cheaper to manufacture. As such people who notice the problem - suffer. Some people who don't have to sit in front of the monitor for 4+ hours straight would never notice.
I didn't imply typing. Everyone can type on a keyboard. I meant more like help with anything that needs multiple apps at the same time. I.e. switching between windows, copy-paste, button clicks and so on during some of the "intense" and fast multi-app sessions. Especially helpful when you have dual screens and a mouse move from left to right requires lifting it and moving again. This adds about 1 second to navigation. Then consider clicking and so on - every app switch takes about 2-3 seconds...
If it has API it will rock as a secondary input system to mouse. You will be able to scroll through text/code just by looking, switch windows, copy paste - it has an enormous potential. Again, if it can be trained to work with 99.9% precision like a mouse.
I am sorry I only watched the first 3 parts. But I noticed he talks about voltages about 70V and currents about 5A which makes me beleive this is a 300-500W motor... the coils he has there will in no way produce 300W. Thus it is not a machine that will run on its own. In my pessimistic opinion the motor has a heavy rotor which has a lot of inertia continuing the spinning. Also notice the rather large wheel with magnets - also contributing to inertia.