I never respond to recruiters unless I find proof they actually read my resume.
Lately I have been doing the selections. Boy. I wish people would simply pass the Codility test, find the nullpointer in our test and understand sql injections. I never trust a resume again; have to verify it.
Remember we are still in the pre-industrial era, computer wise ('everything is still manual labour'). That's why IT costs so much compared to the bare-bone costs. That's why we have QA issues....
There are two issues with all this multi-core speak we've been hearing:
There is hardly any code, other than a few optimized libraries, that use multi core processors. They try to make it sound unimportant but it is the largest hurdle. There is a reason people don't think of a 3930k as being 50% faster than a 3820! Other than some failed libraries like OpenMP; there are no valid programming models to use either multithreading and/or networking transparantly (since it should not functionally make any difference). Ergo: The developers are still making their single-thread code.
The advantage of multi core processors can be that you can lower you clockspeeds and/or memory speeds on secondary tasks. Hardly any research is done on that (I have myself but let's call that an 'academic' proof of concept).
I work at a SaaS business and I have the complete opposite experience. I have a boss/owner who is in it for the long run. I realize that if our service sucks I need to find another job.
It is more efficient to cool down 1/2 the air twice as much. Less overhead with pumps, plumbing, cooling surface, etc. The only problem, mentioned by others, you better not let the hot air escape. IANACE.
For me, creativity of the special kind, involves seeing A, B and C. Then to notice A, B and C are choices and those can be changed to see what happens.
Everybody can do ABC. Create a different word.
The fact that the login+moderation system was needed implies that early users, who might now have low uids, were abusing slashdot. I would not call the abusers smart. QED.
It is always possible your datacenter is no longer accessible (e.g. a bankrupty or legal battle over bills). A police raid is just another reason for that occurance.
I work at an online email marketing company of about 50 people.
We have weekly hotfixes for low/medium impact bugs. We can update all servers in 10 minutes for high impact bugs. We have a feature upgrade release every 6 to 9 months. We could release earlier but we don't want too many communication moments with our customers. The second reason is that we want to deliver a finished product which takes some time, documentation and marketing must be changed, etc.
We don't communicate our maintenance schedule for bugfixes. When we run an update the web browser ui is locked, afterwards a user can pick up where they left. An update is about 20 seconds and ~0% impact. In general we apply the update to a few servers earlier so we catch obvious bugs with less impact. Needless to say we make builds from a VCS and deploy automatically.
For SaaS, you want to have a solid 'operations' department which is in sync with development.
If you want to sell something you need a product and a market. The market might find a (lesser) substitute for expensive information. Regardless of the product.
I've read enough papers in my life but in general I'm just looking for 'the good idea' with reasonable argumentation. Some peer-replies are welcome have a stupidity filter. For the rest they are just long pieces of paper I have to go through.
I guess they will be replaced by blogs or Q&A-pages (like serverside/stackoverflow).
When people from a pigfarm go to the hospital they are immediately quarantined in fear of resistant bacteria. That actually triggers farmers to start lowering the dosis for their pigs...
Slashdot Mirror
I never respond to recruiters unless I find proof they actually read my resume.
Lately I have been doing the selections. Boy. I wish people would simply pass the Codility test, find the nullpointer in our test and understand sql injections. I never trust a resume again; have to verify it.
The exorbitant money will come down, in time.
...
Remember we are still in the pre-industrial era, computer wise ('everything is still manual labour'). That's why IT costs so much compared to the bare-bone costs. That's why we have QA issues.
And a cupcake if dummy mode is turned on. I heard lately that harddrives cannot stand low-frequency sound waves. He should have bought ssd's.
I've heard that they often take running servers out of racks (split the power wire, attach UPS, ... ).
You activate your hot-standby. Or you disable that part of you cluster.
Any hoster, datacenter or location can be down because of any number of reasons.
We've been doing business with Cuba too...
Who has not.
Not according to intel
There are two issues with all this multi-core speak we've been hearing:
There is hardly any code, other than a few optimized libraries, that use multi core processors. They try to make it sound unimportant but it is the largest hurdle. There is a reason people don't think of a 3930k as being 50% faster than a 3820! Other than some failed libraries like OpenMP; there are no valid programming models to use either multithreading and/or networking transparantly (since it should not functionally make any difference). Ergo: The developers are still making their single-thread code.
The advantage of multi core processors can be that you can lower you clockspeeds and/or memory speeds on secondary tasks. Hardly any research is done on that (I have myself but let's call that an 'academic' proof of concept).
Ask them how they test the application. Because you cannot change it easily if you worry about breaking stuff.
I work at a SaaS business and I have the complete opposite experience. I have a boss/owner who is in it for the long run. I realize that if our service sucks I need to find another job.
So there are still people being tortured by forcing sharepoint on them? And you have proof? It must be the Iranians and North Koreans.
My boss generally does not touch non-OSS. Only 5 mega-euro throughput though.
Cognitive dissonance reduction. Read up.
It is more efficient to cool down 1/2 the air twice as much. Less overhead with pumps, plumbing, cooling surface, etc. The only problem, mentioned by others, you better not let the hot air escape. IANACE.
For me, creativity of the special kind, involves seeing A, B and C. Then to notice A, B and C are choices and those can be changed to see what happens. Everybody can do ABC. Create a different word.
Thank god for Gaulois spaces.
The fact that the login+moderation system was needed implies that early users, who might now have low uids, were abusing slashdot. I would not call the abusers smart. QED.
Holland has fixed-price books too.
It is always possible your datacenter is no longer accessible (e.g. a bankrupty or legal battle over bills). A police raid is just another reason for that occurance.
I work at an online email marketing company of about 50 people.
We have weekly hotfixes for low/medium impact bugs. We can update all servers in 10 minutes for high impact bugs. We have a feature upgrade release every 6 to 9 months. We could release earlier but we don't want too many communication moments with our customers. The second reason is that we want to deliver a finished product which takes some time, documentation and marketing must be changed, etc.
We don't communicate our maintenance schedule for bugfixes. When we run an update the web browser ui is locked, afterwards a user can pick up where they left. An update is about 20 seconds and ~0% impact. In general we apply the update to a few servers earlier so we catch obvious bugs with less impact. Needless to say we make builds from a VCS and deploy automatically.
For SaaS, you want to have a solid 'operations' department which is in sync with development.
If you want to sell something you need a product and a market. The market might find a (lesser) substitute for expensive information. Regardless of the product.
I've read enough papers in my life but in general I'm just looking for 'the good idea' with reasonable argumentation. Some peer-replies are welcome have a stupidity filter. For the rest they are just long pieces of paper I have to go through.
I guess they will be replaced by blogs or Q&A-pages (like serverside/stackoverflow).
If the articles remain that expensive the academia end up where newspapers are now... Minimalized.
forgot to say where: Holland
When people from a pigfarm go to the hospital they are immediately quarantined in fear of resistant bacteria. That actually triggers farmers to start lowering the dosis for their pigs...
Yes I do. First, nobody reads the FS (the blogger doesn't get paid anyway). Second, one can have a valid discussion about the type of link.