Oh bullshit. Governments are made of people. All governments act according to a moral code. The best governments act according to a code dictated by the citizens. Bad governments operate on a code dictated by very few powerful people or in the worst cases one person.
Was there any usability testing with developers performed as part of the design process? If so, how did the testing guide development of the specification?
One of the complaints often heard from both critics and fans is that CSS is very difficult to learn and read. In particular the complex rules governing the Cascade are often a source of problems for even experienced developers. Another instance is the often extreme difficulty and skill required to achieve layouts that were easy and common in pre-CSS days.
Then let's a call a spade a spade here. This was a cheap childish PR stunt because previous half-assed attempts failed. It takes a damn long time to get access to the head of an State. You start with lower level representatives and civil servants. You don't try to cut to the front of the line for anything other than some ink and glossy photos.
Fast forward a couple of years. He is still collecting LTD. During a meeting discussing staffing for the dev on a new chip, the VP asked "What about xxx? Can't he do the Unix and SCO drivers?". "But he is in the insane asylum!". "That's ok, we can give him a computer, can't we? He is still on the payroll".
Hu Jintao is the president of one of the most repressive and least humane governments on the planet. There is NOTHING about this man worthy of admiration.
1. Utah is pretty much the MLM capital of the world. This is because the state is littered with big extended families.
2. Working for or doing business with an MLM is no big deal in Utah. As a programmer I get approached to work for or with MLM's on an almost weekly basis. Since I'm not a native I know better than to ever allow one of these black marks ever appear on my resume
3. I was a local developer get-together not too long ago where there were a couple of developers who worked for SCO. They both said they were working on "wireless messaging". Now I know.
The key is the developer has to be around when the people he or she must interact with are around. The developer's hours don't have to match exactly but there has to be sufficient overlap to facilitate good in-person communication. If the developer isn't around when everyone else is then people will question the need to have such a role on-site.
The webmaster example is a good one. Webmasters often have to work or get called in a weird hours. Especially if they are the only person qualified to update the site(s) they control. The mananger has to recognize that and provide sufficient compensation in time, money, and other perks. There may be no way to avoid the occasional Sunday night press release posting but there had better be accomodation made for it. In situations like this I've done things like put the person on a modified schedule that allowed for regular time off on weekly or bi-weekly basis. I've also made the effort to ensure the someone else is cross-trained in at least the simpler tasks so the developer/webmaster doesn't feel chained to their desk.
Part of my role as manager is to provide enough structure to ensure the developers have the freedom to get their work done and feel satisfied. There are many ways to organize a team or manage an individual but it all comes down to a set of agreements. One of the agreements that I won't budge on is a normal work schedule. To date I haven't had any problem hiring or retaining people because of this.
I spend a minimum of 50% of my week programming and I haven't worn a suit since prep school. The people who work for me have a great deal of freedom. That freedom is secured by a very well defined yet minimal set of agreements. Everyone inside and outside my group understands the agreements and recognizes the importance of maintaining them. A regular reasonable work schedule is just one agreement.
I haven't had any problems filling my open slots and I haven't lost or fired anyone in over two years. There are plenty of developers who welcome such structure. For those who don't there are plenty of other places to work.
Not if they work for me. Sorry but I and most of the company work roughly from 8:30 to 5:30 and I expect my developers to roughly conform to that schedule. An hour or so on either side is no big deal but showing up at 12:00 or a different time every day is great way to get fired. I expect developers to maintain a regular schedule with decent hours for the following reasons:
Reliability is key. If you can't maintain a regular schedule then everyone will question your suitability for the job even if your work is stellar
The best communication is in-person. I'm a retail manager - I get the best information through short in-person meetings with my staff. I also expect my staff to directly engage me or other developers if there is a problem. If a developer is not around when I and the rest of the developers are then the project suffers because communication is restricted.
Developers are one part of an integrated team. Sometimes every member of the team has to be present to accomplish a task. I will not allow a developer to force other people to stay late or come in early just to conform to their schedule. Nor will I accept other people doing this to one of my developers
In return for this I make the commitment that developers in my team will not average more than 45 hours per week in a three-month period. If the average is higher or if we anticipate developer's time will spike I bring in a contractor or a new hire.
I know a lot of people may consider this harsh. Too bad. Maybe I've missed hiring the one star developer that will save the company but I seriously doubt it. My experience is that there are plenty of developers on the market for me to choose from. I pick the good reliable team-oriented communicator every time. Rockstar cave dwellers can find some place else to work.
It is however quite true that MS Office has much better support for the visually impared than Open Office. Several years ago Microsoft made a major push to ensure nearly every application they built had some Accessibility support.
We wrote some simple hook scripts for SubVersion that automatically deploys changes to a test instance for syntax checking and then to all our regular servers. We actually to this for all our Linux configuration files. It's a hell of a lot better than.bak the crap.
Yes of course! Just exactly how does one put an entire corporation in jail? Does every shareholder have to serve a period of time in porportion to their percentage of ownership?
Limited Liability (LL) is for the protection of INDIVIDUALS not the corporation. Without LL each and every owner/shareholder could have their personal assets taken as part of a lawsuit. Just exactly how just would it be if your house was taken because you owned one share of a corporation?
So a mother should be required to carry an unwanted pregnancy to term because the child has a detectable abnormality? Then what? She's required to spend her whole life caring for the child? That's some amazingly crazy logic you have there.
I could have ended in abortion as well. I probably would have if my mother wasn't in rural Wyoming at the time. I'm very glad that I'm alive and my mother gave me up for adoption. But I'll never be thankful my mother never had a choice.
Your friend must work in a very tiny insulated box. These systems are so insanely complex it requires input from multiple sources. No one person could design everything.
Also, there is absolutely zero evidence to substantiate you or your friend's claim that the O2 generator failure is due to poor design.
The "Rapid" part of RapidSVN is nowhere to be found. Nearly every operation that hits the server is insanely slow. I've tried it several times over the last year and pitched it within minutes every time. The web-based interfaces are faster and easier to use. Unless the repository is on your workstation avoid RapidSVN.
The Subversion plugin for Eclipse is a reasonable alternative. Development seems to lag behind Subversion by quite a bit though. It can sometimes take weeks for EclipseSVN to implement new commands.
I'd really like to know where you work so I can make sure your employer get's their ass sued off for exposing people's private information. If you and your employer are such ignorant cheapskates that your would RMA a drive with people's personal information then neither of you should be roaming free.
The roads will stay plenty clear as long as we all agree not to tell New Jersey. Those guys can't pump their own gas. Do we *really* want them hanging around after a Tsunami?
Slashdot Mirror
Oh bullshit. Governments are made of people. All governments act according to a moral code. The best governments act according to a code dictated by the citizens. Bad governments operate on a code dictated by very few powerful people or in the worst cases one person.
Was there any usability testing with developers performed as part of the design process? If so, how did the testing guide development of the specification? One of the complaints often heard from both critics and fans is that CSS is very difficult to learn and read. In particular the complex rules governing the Cascade are often a source of problems for even experienced developers. Another instance is the often extreme difficulty and skill required to achieve layouts that were easy and common in pre-CSS days.
I sure do get tired of saying this.... http://slashdot.org/comments.pl?sid=144332&cid=120 98999
Then let's a call a spade a spade here. This was a cheap childish PR stunt because previous half-assed attempts failed. It takes a damn long time to get access to the head of an State. You start with lower level representatives and civil servants. You don't try to cut to the front of the line for anything other than some ink and glossy photos.
Let's just say you're crackers.
Things is - if there is such a thing as "Free Energy" then it can be scientifically proven. I don't have to "Believe it." YOU have to prove it.
Hu Jintao is the president of one of the most repressive and least humane governments on the planet. There is NOTHING about this man worthy of admiration.
1. Utah is pretty much the MLM capital of the world. This is because the state is littered with big extended families.
2. Working for or doing business with an MLM is no big deal in Utah. As a programmer I get approached to work for or with MLM's on an almost weekly basis. Since I'm not a native I know better than to ever allow one of these black marks ever appear on my resume
3. I was a local developer get-together not too long ago where there were a couple of developers who worked for SCO. They both said they were working on "wireless messaging". Now I know.
The key is the developer has to be around when the people he or she must interact with are around. The developer's hours don't have to match exactly but there has to be sufficient overlap to facilitate good in-person communication. If the developer isn't around when everyone else is then people will question the need to have such a role on-site.
The webmaster example is a good one. Webmasters often have to work or get called in a weird hours. Especially if they are the only person qualified to update the site(s) they control. The mananger has to recognize that and provide sufficient compensation in time, money, and other perks. There may be no way to avoid the occasional Sunday night press release posting but there had better be accomodation made for it. In situations like this I've done things like put the person on a modified schedule that allowed for regular time off on weekly or bi-weekly basis. I've also made the effort to ensure the someone else is cross-trained in at least the simpler tasks so the developer/webmaster doesn't feel chained to their desk.
Part of my role as manager is to provide enough structure to ensure the developers have the freedom to get their work done and feel satisfied. There are many ways to organize a team or manage an individual but it all comes down to a set of agreements. One of the agreements that I won't budge on is a normal work schedule. To date I haven't had any problem hiring or retaining people because of this.
I spend a minimum of 50% of my week programming and I haven't worn a suit since prep school. The people who work for me have a great deal of freedom. That freedom is secured by a very well defined yet minimal set of agreements. Everyone inside and outside my group understands the agreements and recognizes the importance of maintaining them. A regular reasonable work schedule is just one agreement.
I haven't had any problems filling my open slots and I haven't lost or fired anyone in over two years. There are plenty of developers who welcome such structure. For those who don't there are plenty of other places to work.
Not if they work for me. Sorry but I and most of the company work roughly from 8:30 to 5:30 and I expect my developers to roughly conform to that schedule. An hour or so on either side is no big deal but showing up at 12:00 or a different time every day is great way to get fired. I expect developers to maintain a regular schedule with decent hours for the following reasons:
In return for this I make the commitment that developers in my team will not average more than 45 hours per week in a three-month period. If the average is higher or if we anticipate developer's time will spike I bring in a contractor or a new hire.
I know a lot of people may consider this harsh. Too bad. Maybe I've missed hiring the one star developer that will save the company but I seriously doubt it. My experience is that there are plenty of developers on the market for me to choose from. I pick the good reliable team-oriented communicator every time. Rockstar cave dwellers can find some place else to work.
It is however quite true that MS Office has much better support for the visually impared than Open Office. Several years ago Microsoft made a major push to ensure nearly every application they built had some Accessibility support.
We wrote some simple hook scripts for SubVersion that automatically deploys changes to a test instance for syntax checking and then to all our regular servers. We actually to this for all our Linux configuration files. It's a hell of a lot better than .bak the crap.
Yes of course! Just exactly how does one put an entire corporation in jail? Does every shareholder have to serve a period of time in porportion to their percentage of ownership?
Limited Liability (LL) is for the protection of INDIVIDUALS not the corporation. Without LL each and every owner/shareholder could have their personal assets taken as part of a lawsuit. Just exactly how just would it be if your house was taken because you owned one share of a corporation?
If you think the Palestinian Authority is a Democracy then you need to go back to school. The PA is a tribal oligarchy.
So a mother should be required to carry an unwanted pregnancy to term because the child has a detectable abnormality? Then what? She's required to spend her whole life caring for the child? That's some amazingly crazy logic you have there. I could have ended in abortion as well. I probably would have if my mother wasn't in rural Wyoming at the time. I'm very glad that I'm alive and my mother gave me up for adoption. But I'll never be thankful my mother never had a choice.
Your friend must work in a very tiny insulated box. These systems are so insanely complex it requires input from multiple sources. No one person could design everything.
Also, there is absolutely zero evidence to substantiate you or your friend's claim that the O2 generator failure is due to poor design.
The "Rapid" part of RapidSVN is nowhere to be found. Nearly every operation that hits the server is insanely slow. I've tried it several times over the last year and pitched it within minutes every time. The web-based interfaces are faster and easier to use. Unless the repository is on your workstation avoid RapidSVN.
The Subversion plugin for Eclipse is a reasonable alternative. Development seems to lag behind Subversion by quite a bit though. It can sometimes take weeks for EclipseSVN to implement new commands.
I'd really like to know where you work so I can make sure your employer get's their ass sued off for exposing people's private information. If you and your employer are such ignorant cheapskates that your would RMA a drive with people's personal information then neither of you should be roaming free.
You sir, are an idiot. Plenty of data recovery companies are able to put the shattered bits back together.
THE ONLY WAY to ensure the HD is completely unrecoverable is to melt it down. Completely melt it down. Get it?
Melt
it
down
Have you got a microwave? Google for instructions on turning it into a kiln and use that.
Case Western is private. I should know, I'm still paying them.
The roads will stay plenty clear as long as we all agree not to tell New Jersey. Those guys can't pump their own gas. Do we *really* want them hanging around after a Tsunami?