I would counter-argue that any flash drive manufacturer is asking for massive RMAs when the device is clearly targeted for the laptop market (otherwise they would manufacture it in a 3.5" format) where the operating environment is guaranteed to be running on a battery for long periods of time. Any research in to battery operation would expose you to the vast differences in operating voltage as batteries discharge as well as the age of the battery. It is just bad engineering to not take this in to account.
Reformatting the drive was not an option because the drive wouldn't even detect in the BIOS unless the special factory jumper was set which is a non-operational mode for the drive. This problem was reproduced over 10 times with over 10 different drives of the same model Vertex. Slightly bad power caused the entire drive to be rendered unusable. Amazingly, none of the other hardware in the laptop had any problem with the power (i.e. screen, cpu, memory, other spindle-based hard drive, gpu, etc.). As I said, bad engineering.
I've had over 10 replacements on the original OCZ Vertex 160GB drives and an unnecessary motherboard replacement on my laptop that I eventually figured out was due to the laptop battery reaching the end of its life and not providing enough voltage. Unfortunately OCZ's engineers did not design the drives to handle loss of voltage and the drives absolutely corrupt. Eventually OCZ sneakily modified their warranty to include not providing warranty when the drives don't receive enough power rather than getting their engineers to just fix the problem. I'm actually running on a Vertex 3 and as of yet have not had that problem, but I am crossing my fingers.
There's actually a really fantastic chart in Chapter 1 pg. 10 that I magnified and printed out as a quick reference. I also drew the gate pictures at the top so I could more easily interpret the schematics.
Coincidentally I have been running through this course in my spare time and I have to say it is the best I have found in 10 years. I've been itching to build a homebrew cpu like http://www.homebrewcpu.com/ but lacked the basic skills to design a proper ALU and such. Most other courses either start way too basic and then shoot too far forward or they gloss over the basics and go right in to advanced concepts. So far I have made it through Chapter 2 and I'm proud to say that I've built all the basic components in HDL without looking anything up outside of the course material. Being able to build complex components on top of basic components I built myself is very rewarding. This is a must take course if you want a more intimate understanding of how computers work. And if building a computer from basic gates isn't nerdy enough for you, build your owntransistors.
The one difference between this video and typical hate crimes is that nobody is forced to watch it (at least not forced to by the people who manufacture or distribute it). Perhaps the middle eastern communities should do what American's do in this type of situation, socially shun those who proliferate the behavior they find distasteful. At most, I could see Google putting this under their adult section to protect Islamic children from being able to view the video, though that really is primarily the job of the parents to regulate.
The toddler/family was conducting neither criticism, comment, news reporting, teaching, scholarship, or research with the Prince music. In addition, the woman published to a public forum where others besides her family could view the video. People really need to start taking responsibility for their own actions and stop using children and the "awww, cmon...." mentality as defense for their lack of judgement.
Microsoft releases less secure copy of W3C Web Crypto API already implemented in Internet Explorer 10 called SecureXaml while citing the changes as "features".
I find that to be simply amazing that hand-held consumer devices are only now matching and exceeding computing hardware that was invented over 27 years ago.
Yes, although not specified on their website, OpenStack's goals have been to create a vendor agnostic public and private cloud system that is API compatible with Amazon EC2 and S3. Inviting VMWare to participate really has no bearing on this goal unless VMWare limit's OpenStack's ability to configure and manage VMWare resources in an EC2 and S3 compatible fashion. VMWare ESXi is freely available, but I believe to get API access to ESXi, you have to get the vSphere (or whatever it's called now) license component. If VMWare doesn't want to/can't open API access directly in ESXi, then they should probably be kicked out of the group.
You can dress it up any which way you like. Here, let me look up investment in the dictionary for you: "investment (noun): the investing of money or capital in order to gain profitable returns, as interest, income, or appreciation in value." So here's how this works. A company wants to spend a moderate amount of "money or capital" in order to ensure that the potential developer in question will produce "gaining profitable returns" from the work produced by said potential employee. Guess what, that "investment" can also be considered, in the current fair market, a standard business etiquette. It's amazing how two things can be the same and one doesn't have to discount the validity of the other statement to make the second statement true.
I'm not saying that a week of free labor is the right thing for me or you, but there are many other industries where potential employees have to practically slave away for little to no money and relinquish all credit to the work they do under the guise of internship. Working for a company such as Hashrocket can quickly get you in to the inner circles of developers from other well known shops or even the Rails and Ruby core teams and make your future skills, hire-ability, and salary requirements higher than coming from a no-name shop. If you're at a point in your life where a week's pay and time is more precious to you then the potential benefits such an opportunity presents, well then I say either good job or good luck to you.
That's highly doubtful. If you have interviewed people before then you must know what a great time suck it is for all people involved. I could possibly suspect foul play if they weren't doing pair programming. They're not only investing in you by purchasing travel arrangements, but they're also letting you significantly slow down at least one of their own developers who is going to have to take significant time explaining the project you're working on, what company coding standards are, and listen to you come up with some crappy ideas because you don't know the code base very well while they are already way far ahead of you on how to solve the problem. Hashrocket is very well known in the RoR community for being an early success, have/have had some high profile employees, and contribute back to the community http://hashrocket.com/open-source. On top of that, asking somebody to move their entire family and having to fire them 4 months later because they couldn't hack it or other more productive people just straight up didn't like them is destructive to everybody involved.
Claimer: I do not work for Hashrocket, have never worked for them, and actually have never even met anyone from there either.
Don't these scientists understand that there's no way we can remember all of these historical inventors? If we can just say the majority of things in the world were invented by Leonardo da Vinci, Galileo, Benjamin Franklin, and Nikola Tesla it would make all our lives so much easier. k thx bye
Don't they know men give up the first amendment right to free speech the second they get married, if not months or years ahead of time. Particularly when the mother-in-law is in town.
The prerequisites to making the switch is first and most importantly having an appropriate business case for OLAP. The second prerequisite is that you've tried doing analytics in a traditional RDMS, perhaps jumped on to the NoSQL bandwagon, and you've failed at it (i.e. success for a little while but then your data eventually brings your queries down to its knees). Don't worry, failure isn't necessarily wrong, it's just you and your team needed the experience before you could make the next leap.
The risks are a knowledge jump in to an OLAP mindset from a traditional SQL mindset. Invest in you and your fellow developer's knowledge. Push back on management and sales when they want more immediate results and let them know that it will take 3-5 months to replace your current system. Do your proper technology evaluations. Learn FoodMart and Adventureworks and let them guide you down the path of good fact and dimension design. Don't snub your nose at Microsoft as they absorbed the company in the 80's that basically pioneered this stuff and made billions, but also don't take their stuff too literally as there are several products out there and some that do things better.
Read The Data Warehouse Toolkit thoroughly and practice using Mondrian which is an open source Java OLAP engine that can sit on top of PostgreSQL, MySQL, and others. Find a good ETL tool rather than trying to write your own at first and don't be afraid to force your internal users to use this tool to create their facts. Don't worry if you don't get it the first time, but keep trying and keep discussing with your fellow developers as it takes a team to work out all the kinks. Later on you'll probably end up seeing how you did things wrong, but hopefully you can get most things right in the beginning.
It is not very often that a company gets software designed for exactly what their needs are. Put together a decent package, i.e. licensing terms, costs (licensing and buyout), feature list, benefit comparison, maintenance fees. Spend the time and put together an LLC (sole proprietorship would likely be a little too risky in this instance). Don't be lazy and put it in to a nice professional looking folder. You'd be surprised how differently people respond when they receive something that shows some effort and professionalism compared to some guy saying "hey I've got this thing, you want it then give me money". The best part is they already know you and know the quality of your work rather than the line of some sleazy sales guy.
Lastly, don't expect them to buy. Just because you see the need and it may be the perfect product for the company you work for doesn't mean they will want to buy it. At least you will provide a view of a compelling product and you're giving them the opportunity to consider things in a format that they are accustomed to and gives your supervisor something more tangible to give to his/her higher-ups. Don't nag and be sure to do some follow up in 2-3 weeks if you haven't heard anything from them. If they indicate they're not interested, don't bother pursuing, but if they say maybe or better just hold the line and keep following up every 2-3 weeks. Sometimes other cogs in the organization have to spin before a decision can be made and that can take time.
Also don't be unwilling to negotiate. Perhaps you can show them the maintenance fees and say that you'd be willing to waive them with a minor change in job description that fits the necessary duties and a modest raise to make up for the difference in cost (perhaps that raise matches the amortized maintenance cost over a 12-month period...) which would also allow for performing maintenance and minor feature improvement during normal working hours.
Although I wholeheartedly agree with all the people who are going to recommend Unity (which is also the platform I prefer), you might be better served with UDK when demonstrating to students. I'd say that Unity is a 3d game engine/platform made for programmers whereas UDK is a 3d game engine/platform made for level designers with support for programmers. You can get a lot of mileage from both platforms without much programming, but UDK is specifically designed so you can create an entire game without one stitch of programming (i.e. Jazz the Jackrabbit).
Also, I highly recommend the free training videos from 3dbuzz, here are the ones for UDK and here are the ones for Unity.
Slashdot Mirror
They must have found the same people off the street that looked at the iPhone 5 before it was released.
I would counter-argue that any flash drive manufacturer is asking for massive RMAs when the device is clearly targeted for the laptop market (otherwise they would manufacture it in a 3.5" format) where the operating environment is guaranteed to be running on a battery for long periods of time. Any research in to battery operation would expose you to the vast differences in operating voltage as batteries discharge as well as the age of the battery. It is just bad engineering to not take this in to account.
Reformatting the drive was not an option because the drive wouldn't even detect in the BIOS unless the special factory jumper was set which is a non-operational mode for the drive. This problem was reproduced over 10 times with over 10 different drives of the same model Vertex. Slightly bad power caused the entire drive to be rendered unusable. Amazingly, none of the other hardware in the laptop had any problem with the power (i.e. screen, cpu, memory, other spindle-based hard drive, gpu, etc.). As I said, bad engineering.
I've had over 10 replacements on the original OCZ Vertex 160GB drives and an unnecessary motherboard replacement on my laptop that I eventually figured out was due to the laptop battery reaching the end of its life and not providing enough voltage. Unfortunately OCZ's engineers did not design the drives to handle loss of voltage and the drives absolutely corrupt. Eventually OCZ sneakily modified their warranty to include not providing warranty when the drives don't receive enough power rather than getting their engineers to just fix the problem. I'm actually running on a Vertex 3 and as of yet have not had that problem, but I am crossing my fingers.
There's actually a really fantastic chart in Chapter 1 pg. 10 that I magnified and printed out as a quick reference. I also drew the gate pictures at the top so I could more easily interpret the schematics.
Coincidentally I have been running through this course in my spare time and I have to say it is the best I have found in 10 years. I've been itching to build a homebrew cpu like http://www.homebrewcpu.com/ but lacked the basic skills to design a proper ALU and such. Most other courses either start way too basic and then shoot too far forward or they gloss over the basics and go right in to advanced concepts. So far I have made it through Chapter 2 and I'm proud to say that I've built all the basic components in HDL without looking anything up outside of the course material. Being able to build complex components on top of basic components I built myself is very rewarding. This is a must take course if you want a more intimate understanding of how computers work. And if building a computer from basic gates isn't nerdy enough for you, build your own transistors.
The one difference between this video and typical hate crimes is that nobody is forced to watch it (at least not forced to by the people who manufacture or distribute it). Perhaps the middle eastern communities should do what American's do in this type of situation, socially shun those who proliferate the behavior they find distasteful. At most, I could see Google putting this under their adult section to protect Islamic children from being able to view the video, though that really is primarily the job of the parents to regulate.
The toddler/family was conducting neither criticism, comment, news reporting, teaching, scholarship, or research with the Prince music. In addition, the woman published to a public forum where others besides her family could view the video. People really need to start taking responsibility for their own actions and stop using children and the "awww, cmon...." mentality as defense for their lack of judgement.
Heh, the editors must have edited the excerpt after seeing my post.
Isn't Linus still the primary force behind the development of the Linux kernel or did I not get the memo?
what are you wearing right now?
I should point out that HDSDR is another software radio project.
Microsoft releases less secure copy of W3C Web Crypto API already implemented in Internet Explorer 10 called SecureXaml while citing the changes as "features".
I find that to be simply amazing that hand-held consumer devices are only now matching and exceeding computing hardware that was invented over 27 years ago.
Yes, although not specified on their website, OpenStack's goals have been to create a vendor agnostic public and private cloud system that is API compatible with Amazon EC2 and S3. Inviting VMWare to participate really has no bearing on this goal unless VMWare limit's OpenStack's ability to configure and manage VMWare resources in an EC2 and S3 compatible fashion. VMWare ESXi is freely available, but I believe to get API access to ESXi, you have to get the vSphere (or whatever it's called now) license component. If VMWare doesn't want to/can't open API access directly in ESXi, then they should probably be kicked out of the group.
The problem is that the school forgot to get iPads with the MacBook wheel option.
You can dress it up any which way you like. Here, let me look up investment in the dictionary for you: "investment (noun): the investing of money or capital in order to gain profitable returns, as interest, income, or appreciation in value." So here's how this works. A company wants to spend a moderate amount of "money or capital" in order to ensure that the potential developer in question will produce "gaining profitable returns" from the work produced by said potential employee. Guess what, that "investment" can also be considered, in the current fair market, a standard business etiquette. It's amazing how two things can be the same and one doesn't have to discount the validity of the other statement to make the second statement true.
I'm not saying that a week of free labor is the right thing for me or you, but there are many other industries where potential employees have to practically slave away for little to no money and relinquish all credit to the work they do under the guise of internship. Working for a company such as Hashrocket can quickly get you in to the inner circles of developers from other well known shops or even the Rails and Ruby core teams and make your future skills, hire-ability, and salary requirements higher than coming from a no-name shop. If you're at a point in your life where a week's pay and time is more precious to you then the potential benefits such an opportunity presents, well then I say either good job or good luck to you.
That's highly doubtful. If you have interviewed people before then you must know what a great time suck it is for all people involved. I could possibly suspect foul play if they weren't doing pair programming. They're not only investing in you by purchasing travel arrangements, but they're also letting you significantly slow down at least one of their own developers who is going to have to take significant time explaining the project you're working on, what company coding standards are, and listen to you come up with some crappy ideas because you don't know the code base very well while they are already way far ahead of you on how to solve the problem. Hashrocket is very well known in the RoR community for being an early success, have/have had some high profile employees, and contribute back to the community http://hashrocket.com/open-source. On top of that, asking somebody to move their entire family and having to fire them 4 months later because they couldn't hack it or other more productive people just straight up didn't like them is destructive to everybody involved.
Claimer: I do not work for Hashrocket, have never worked for them, and actually have never even met anyone from there either.
Don't these scientists understand that there's no way we can remember all of these historical inventors? If we can just say the majority of things in the world were invented by Leonardo da Vinci, Galileo, Benjamin Franklin, and Nikola Tesla it would make all our lives so much easier. k thx bye
Why make BILLIONS when you can make...millions!?!? Bwa-ha-ha-ha-ha!
Don't they know men give up the first amendment right to free speech the second they get married, if not months or years ahead of time. Particularly when the mother-in-law is in town.
What....too soon?
The prerequisites to making the switch is first and most importantly having an appropriate business case for OLAP. The second prerequisite is that you've tried doing analytics in a traditional RDMS, perhaps jumped on to the NoSQL bandwagon, and you've failed at it (i.e. success for a little while but then your data eventually brings your queries down to its knees). Don't worry, failure isn't necessarily wrong, it's just you and your team needed the experience before you could make the next leap.
The risks are a knowledge jump in to an OLAP mindset from a traditional SQL mindset. Invest in you and your fellow developer's knowledge. Push back on management and sales when they want more immediate results and let them know that it will take 3-5 months to replace your current system. Do your proper technology evaluations. Learn FoodMart and Adventureworks and let them guide you down the path of good fact and dimension design. Don't snub your nose at Microsoft as they absorbed the company in the 80's that basically pioneered this stuff and made billions, but also don't take their stuff too literally as there are several products out there and some that do things better.
Read The Data Warehouse Toolkit thoroughly and practice using Mondrian which is an open source Java OLAP engine that can sit on top of PostgreSQL, MySQL, and others. Find a good ETL tool rather than trying to write your own at first and don't be afraid to force your internal users to use this tool to create their facts. Don't worry if you don't get it the first time, but keep trying and keep discussing with your fellow developers as it takes a team to work out all the kinks. Later on you'll probably end up seeing how you did things wrong, but hopefully you can get most things right in the beginning.
It is not very often that a company gets software designed for exactly what their needs are. Put together a decent package, i.e. licensing terms, costs (licensing and buyout), feature list, benefit comparison, maintenance fees. Spend the time and put together an LLC (sole proprietorship would likely be a little too risky in this instance). Don't be lazy and put it in to a nice professional looking folder. You'd be surprised how differently people respond when they receive something that shows some effort and professionalism compared to some guy saying "hey I've got this thing, you want it then give me money". The best part is they already know you and know the quality of your work rather than the line of some sleazy sales guy.
Lastly, don't expect them to buy. Just because you see the need and it may be the perfect product for the company you work for doesn't mean they will want to buy it. At least you will provide a view of a compelling product and you're giving them the opportunity to consider things in a format that they are accustomed to and gives your supervisor something more tangible to give to his/her higher-ups. Don't nag and be sure to do some follow up in 2-3 weeks if you haven't heard anything from them. If they indicate they're not interested, don't bother pursuing, but if they say maybe or better just hold the line and keep following up every 2-3 weeks. Sometimes other cogs in the organization have to spin before a decision can be made and that can take time.
Also don't be unwilling to negotiate. Perhaps you can show them the maintenance fees and say that you'd be willing to waive them with a minor change in job description that fits the necessary duties and a modest raise to make up for the difference in cost (perhaps that raise matches the amortized maintenance cost over a 12-month period...) which would also allow for performing maintenance and minor feature improvement during normal working hours.
Although I wholeheartedly agree with all the people who are going to recommend Unity (which is also the platform I prefer), you might be better served with UDK when demonstrating to students. I'd say that Unity is a 3d game engine/platform made for programmers whereas UDK is a 3d game engine/platform made for level designers with support for programmers. You can get a lot of mileage from both platforms without much programming, but UDK is specifically designed so you can create an entire game without one stitch of programming (i.e. Jazz the Jackrabbit).
Also, I highly recommend the free training videos from 3dbuzz, here are the ones for UDK and here are the ones for Unity.
I guess you've never heard of Gentoo...