It all depends on experience and location. A good hardware designer with some software experience can get between UKP35 and UKP55 per hour (USD55 and USD90) in Cambridge after the agent commission. Remember to factor about 20% employment tax (employer and employee National Insurance NI) and a sliding scale going up to 40% income tax on top of the NI.
You can get more in London but the living costs can be higher.
I think the biggest recruitment site in the UK is http://www.jobserve.com/. Put in your keywords and take a look at the results. Many of them include the rate.
Don't forget the EU has restrictions on who can work so check before applying for a job.
Your posting shows why it is best to use conventional procedural programming for low level I/O and performance sensitive applications - an extremely interesting read.
In short, keep the code small, minimise calls and locate all associated parts of the code together as much as possible. It is possible for the compiler to help but when you link together lots of classes from different files (code segments) it is impossible to do it efficiently.
I spend a lot of my time writing 'Low Level' code, keeping the cache hits up and the pipeline full can make a massive difference to the program performance.
I had a similar experience earlier this year when Craphead (he posted a few times on Slashdot) died before the Linux Beer Hike. His site was eventually pulled by his ISP in Norway and I wish I had mirrored it first.
Your point about sites being pulled when the domain expires is a good one. The problem is that there is no 'standard' way of archiving them into cold storage where they can later be retrieved. At least with the older media (newspapers/mags etc) someone would usually keep a copy somwhere so it could be looked at by suceeding generations but not with a website.
This bitrot really needs addressing lest our decendants ask us what people posted and read in the exciting and dynamic days on the early Internet. Once the rm -rf has done its work nothing remains.
I am also a little saddened by this death, I never knew who was the creator of ping but use it everyday. I guess he, like Jon Postel, has left a little of himself on everyones computer and thereby improved the world a little for all those of us who are left behind.
Thats why SFF-8049 specifies an 80 conductor cable. I guess that the HF impedance is around 120 ohms. Splitting them apart is only going to result in trouble with mismatches, reflections and data corruption.
At 66MHz IDE cables are going to look like a transmission line and I assume that is why there are so many earth connections in parallel with the signal wires. If you separate them then you could end up with a mismatch, more RF interference and possibly data corruption.
If you are going to try it out then backup your data first and make sure that you have a spare cable in case you break something
The real problem is the lack of accountability with ICANN. When they were set up a board of directors was appointed who had to step down after a certain period. In an attempt to show openness they launched the At-Large campaign where web users could register and elect new directors.
So they had the election and discovered that the web users voted in the strongest critics of ICANN. Oh, dear, a problem, the ICANN board got around this by tweeking the interpretation of the rules such that the new directors would be unable to vote until after the next AGM. They also voted themselves an extension of the time in which they can stay in office. There is even talk now about reducing the number of elected officials in the future. BTW I have an enormous respect for some of the current directors so don't tar them all with the same brush.
There was a great article on Slashdot only a couple of days ago about an analysis of the domain dispute policy. This pointed out in no uncertain terms how the system favoured the complainer in that they could select the resolution body and surprise the bodies which ruled most frequently for the complainant got the most work.
I am from the UK and have concerns about an organisation which is based in the US and subject to US laws controlling such an important area of the Internet as the actions of that body will be determined by what is regarded as acceptable to the residents of North America and not myself.
With the existing.ORG,.COM and.NET (ignoring the others for the moment) domains there is little problem as there are no 'rules' about what someone can do with them after registration. With the new ones which are coming out things will be different. Consider museum, who decides what is permitted to be registered ? ICANN along with MDMA. There ***will*** be disagreements as to what contitutes a museum particually when different languages and national laws are involved. Can you see North Korea happily accepting the decision made by ICANN in regard to an application. Anyway who gives them the right to do this? - themselves.
If you are working on a new project use XML Schema rather than DTDs. DTDs are a hangover from the days of SGML and do not allow you much control on the content of your documents.
If you use XML Schema then you can specify exactly the format and content of your fields and validate the document much more precisely than just PCDATA / CDATA permits.
Go and have a look at the W3C site before you commit yourself, it is an easy change at the start of a project but will be much harder later.
Its all very well having TLDs for sex etc. The problem is defining what goes in each and trying to enforce it.
The problem is that the Internet is world wide and the different countries each have their own standards for what is acceptable. If ICANN or a registry try to apply a given standard for decency they would (rightly) be accused of trying to force the rest of the world into their standards of ethics, morals and decency. And in the case of ICANN charges of American Imperialism would me made. Imagine trying to come up with a definition of pornography which would be acceptable to Iran, China, France and the US.
There would also be cases where a commercial organisation would wish to have a TLD which others would think inappropriate. Who defines what it right?
It could be a GOOD THING if the US tried to shutdown the Internet as it would encourage the rest of the world to reduce the dependance on the US. The non-US backbone providers would quickly update their routing tables and IANA would be forced to allow more root servers to be established in Europe etc.
It would hurt in the short term but we would end up with a more resilient and secure Internet.
Slashdot Mirror
It all depends on experience and location. A good hardware designer with some software experience can get between UKP35 and UKP55 per hour (USD55 and USD90) in Cambridge after the agent commission. Remember to factor about 20% employment tax (employer and employee National Insurance NI) and a sliding scale going up to 40% income tax on top of the NI.
You can get more in London but the living costs can be higher.
I think the biggest recruitment site in the UK is http://www.jobserve.com/. Put in your keywords and take a look at the results. Many of them include the rate.
Don't forget the EU has restrictions on who can work so check before applying for a job.
Andy
Your posting shows why it is best to use conventional procedural programming for low level I/O and performance sensitive applications - an extremely interesting read.
In short, keep the code small, minimise calls and locate all associated parts of the code together as much as possible. It is possible for the compiler to help but when you link together lots of classes from different files (code segments) it is impossible to do it efficiently.
I spend a lot of my time writing 'Low Level' code, keeping the cache hits up and the pipeline full can make a massive difference to the program performance.
I had a similar experience earlier this year when Craphead (he posted a few times on Slashdot) died before the Linux Beer Hike. His site was eventually pulled by his ISP in Norway and I wish I had mirrored it first.
Your point about sites being pulled when the domain expires is a good one. The problem is that there is no 'standard' way of archiving them into cold storage where they can later be retrieved. At least with the older media (newspapers/mags etc) someone would usually keep a copy somwhere so it could be looked at by suceeding generations but not with a website.
This bitrot really needs addressing lest our decendants ask us what people posted and read in the exciting and dynamic days on the early Internet. Once the rm -rf has done its work nothing remains.
I am also a little saddened by this death, I never knew who was the creator of ping but use it everyday. I guess he, like Jon Postel, has left a little of himself on everyones computer and thereby improved the world a little for all those of us who are left behind.
Mike Muuss, thank you.
Thats why SFF-8049 specifies an 80 conductor cable. I guess that the HF impedance is around 120 ohms. Splitting them apart is only going to result in trouble with mismatches, reflections and data corruption.
At 66MHz IDE cables are going to look like a transmission line and I assume that is why there are so many earth connections in parallel with the signal wires. If you separate them then you could end up with a mismatch, more RF interference and possibly data corruption.
If you are going to try it out then backup your data first and make sure that you have a spare cable in case you break something
The real problem is the lack of accountability with ICANN. When they were set up a board of directors was appointed who had to step down after a certain period. In an attempt to show openness they launched the At-Large campaign where web users could register and elect new directors.
So they had the election and discovered that the web users voted in the strongest critics of ICANN. Oh, dear, a problem, the ICANN board got around this by tweeking the interpretation of the rules such that the new directors would be unable to vote until after the next AGM. They also voted themselves an extension of the time in which they can stay in office. There is even talk now about reducing the number of elected officials in the future. BTW I have an enormous respect for some of the current directors so don't tar them all with the same brush.
There was a great article on Slashdot only a couple of days ago about an analysis of the domain dispute policy. This pointed out in no uncertain terms how the system favoured the complainer in that they could select the resolution body and surprise the bodies which ruled most frequently for the complainant got the most work.
I am from the UK and have concerns about an organisation which is based in the US and subject to US laws controlling such an important area of the Internet as the actions of that body will be determined by what is regarded as acceptable to the residents of North America and not myself. With the existing .ORG, .COM and .NET (ignoring the others for the moment) domains there is little problem as there are no 'rules' about what someone can do with them after registration. With the new ones which are coming out things will be different. Consider museum, who decides what is permitted to be registered ? ICANN along with MDMA. There ***will*** be disagreements as to what contitutes a museum particually when different languages and national laws are involved. Can you see North Korea happily accepting the decision made by ICANN in regard to an application. Anyway who gives them the right to do this? - themselves.
If you are working on a new project use XML Schema rather than DTDs. DTDs are a hangover from the days of SGML and do not allow you much control on the content of your documents.
If you use XML Schema then you can specify exactly the format and content of your fields and validate the document much more precisely than just PCDATA / CDATA permits.
Go and have a look at the W3C site before you commit yourself, it is an easy change at the start of a project but will be much harder later.
Description of XML schema can be found at http://www.w3.org/XML/Schema .
Its all very well having TLDs for sex etc. The problem is defining what goes in each and trying to enforce it.
The problem is that the Internet is world wide and the different countries each have their own standards for what is acceptable. If ICANN or a registry try to apply a given standard for decency they would (rightly) be accused of trying to force the rest of the world into their standards of ethics, morals and decency. And in the case of ICANN charges of American Imperialism would me made. Imagine trying to come up with a definition of pornography which would be acceptable to Iran, China, France and the US.
There would also be cases where a commercial organisation would wish to have a TLD which others would think inappropriate. Who defines what it right?
I forsee lots of trouble ahead ...
It could be a GOOD THING if the US tried to shutdown the Internet as it would encourage the rest of the world to reduce the dependance on the US. The non-US backbone providers would quickly update their routing tables and IANA would be forced to allow more root servers to be established in Europe etc.
It would hurt in the short term but we would end up with a more resilient and secure Internet.