In financial terms, if you have pricing power, you can do what you want. If you don't, it's called deflation and you do what the customer wants or you go out of business. As an employee, you are in a business relationship with your employer. Which of you can go down the block for a substitute? This is why you can walk out and get a cheap burger from half a dozen chains. But if you want a hand-built guitar from the Fender Custom Shop, you pay their price.
When you want to legalize vigilante justice, you better make sure you can outgun everyone. When it comes to the Internet, RIAA hasn't got a chance. Of course, this is why they went whining to Washington in the first place.
I'd love it if several of the RIAA people went to prison for live for hacking. Two wrongs make a righteous fantasy!
On my Linux box, I am using NetSaint to monitor the temperature. I have added scripts to kill SETI@Home and Folding@Home when the temperature gets to the warning levels (45C Mobo, 50C CPU) and start an orderly shutdown when the temperature gets to the critical levels (50C Mobo, 55C CPU). Killing the NULL tasks drops the temperature 5 degrees Celsius.
I expect a fair number of professors are close to my age (51). When I started, terminals were either unavailable, or too expensive for classwork. I wrote code, on paper, and then went and keyed it on punched cards. Then you turned it in and received the card deck and a listing back in: a few hours, a day, or even a week. A misplaced semi-colon cost you one turn around cycle. You had better be able to proof your work before the compiler gets your program or you will not get your work done in time.
There are still people who think this is the only proper way to program (see Cleanroom process).
What the original poster is telling me is that he is brittle, he can only code when Ares is rising, his favorite MP3 is playing, the sun isn't too bright, etc.
Now preferred conditions are fine, but "I can't code on paper". Fragile, brittle. I like white boards for design, paper for writing, terminals for editting, etc. I've designed on terminals, paper, backs of envelopes, cocktail napkins, etc. I've coded at the key punch, terminal, Starbucks, etc. I've debugged on cards w/ a listing, memory dumps, front panels, hex debbuggers, symbolic debuggers, IDEs, etc. That's what being a professional means. Otherwise you are a recreational coder.
"The only tool a programmer needs is a pencil with a five pound eraser." - circa mid 70's
Most people learn concrete first, then they can move to abstract. Without some programming language(s) to think in or weigh alternatives in, it gets difficult to consider abstract notions.
It sounds like you are trying to do what I tried, teaching black belt lessons to white belts. This does not work, even if the black belt lessons are on topics the white belts already have covered.
Not under this bill. It is not digital. And it predates the bill. However, you may find that nothing will come out on VHS tape. I think you can cough up the money to play a protected program once and record it in analog. However, the usual fair use, etc. rules apply.
That said, if this passes in anything like its current form, there will be even more restrictive legislation.
I just read the definition of an "interactive digital device" in the SSSCA draft. The little keyless access goody to unlock my car qualifies. It transmits, receives, and stores information in digital form. And this requires a copy protection device to protect Disney et al's intellectual property? You gotta be kidding!
Maybe the analysis didn't get it right. I've seen one connect attempt to port 80 since meltdown and there wasn't anything running on port 80 at that IP address, so it was probably wasn't Code Red, just a dork with a script.
People skills! Programmers can hide in their
caves and snarl when thrown their ration of caffeine and carbohydrates. Sysadmins gotta be able to smile while being asked: 1) to do the impossible, 2) Yet Another FAQ, 3) add another user, 4) restore from backup, 5) say no to some bigwig who wants the security policy violated for his/her personal whim, *) you get the idea.
Be good to your sysadmin, even if it isn't his/her day.
As easy to use as the ical program (I liked Todo lists, graphical setting of appointments and warnings). Ability to send e-mail warnings to my cellphone so I don't have to carry it and a PDA w/ appointments. Way to extend repeat options (every 8th day, the two Thursdays before 2nd Sunday, are ones I need). Share calendars like Outlook Express. Reliability, unlike Outlook Express.
I have been in this business for 25 years. Being a task lead is the price I pay to get to do the high level design. I am an excellent programmer and a competent task lead and intend to stay that way. I would rather be doing what I am good at, but who doesn't.
Advice? Compliment good work. If you can't find any good work by someone, look harder, find them some place to succeed, or get rid of them. What out for heroes and saviors. They may be cranking out incomplete code to look good, that others will find or trip on the bugs and look bad. Anyone who is working 60+ hours/week isn't doing their job in the planning department. Remember you are dealing with people, they have lives, wives, kids, significant others, bad days, and deaths in the family. Learn something about the Meyers-Briggs Type Inventory. Extraverts annoy/terrify introverts by thinking out load. Sensation types annoy Intuitives by demanding facts, data, etc. Good intuitives annoy sensation types by being right without having facts, data to back it up. Process types are great in emergencies where the pre-made plans don't apply. Judgement types are great with setting schedules and planning (and reducing the number of emergencies). Try to understand peoples strengths and weaknesses. Let them flex their strengths and get them help with weak areas that are needed for their job. This is especially true for yourself. Read the magazines that slant towards technical management (e.g. Software Development).
Finally, ask your self if you really want to be a manager. My father and I both tried it and decided no, knowing it meant that our "juniors" would be making more money and have more authority.
Books: "Getting to Yes", "Getting Past No", "Getting Together", and all the rest by the Harvard Negotiation project. IIRC, the authors of the first are Ury and Fisher.
Testing is done for two reasons: to find bugs so they can be fixed and to demonstrate how good the product is. E.g., the FDA requires formal QA to do the latter. Users, coders, and testers are all equally adept at the former. Any large company has some body tasked with determining the quality (and suitability) of potential products and services that will be used company wide. They don't delegate or trust someone else to do that. This is in addition to any testing the original team did.
If there is a make check target, I feel a little better about the quality. They did some testing, they automated it so it probably get done with every release and most builds, etc. I know that some attention has been paid to testing. For example, the GNOME XML library has dozens of tests and takes about as long to run the tests as build the library. I has some assurance that there is some concern for quality.
Excuse the cynicism. My experience with QA people has not been good. There may be even fewer really good QA people than programmers. I have encountered a number of great programmers in 25 years in this business. I have met one great QA person (thanks Roger Mason wherever you are). The rest reinforced the notion that those that can do, those can't test (and criticise).
I read a tech report sometime in 1997 or before that described an integer DCT with just shifts and simple constants (e.g., X * 5 == X + X 2). Maybe this is it, maybe it was prior art. I don't remember who wrote it or what organization it was. HTH
Break out the disinformation, pollute the DB
on
Profiling A Nation
·
· Score: 1
title says it all. Any database is subject to the second law of thermodynamics (in a closed system, entropy increases). Give them a little help.
PC 99 means you have to buy all new cards, HW, printers, etc. Mac did it all right. Yeah, they sure did. My mother's Mac just died. To get an iMac she will have to replace the working printer or pay 80-100 bucks for a USB to serial adapter. I couldn't believe they didn't include a serial port.
Slashdot Mirror
In financial terms, if you have pricing power, you can do what you want. If you don't, it's called deflation and you do what the customer wants or you go out of business. As an employee, you are in a business relationship with your employer. Which of you can go down the block for a substitute? This is why you can walk out and get a cheap burger from half a dozen chains. But if you want a hand-built guitar from the Fender Custom Shop, you pay their price.
When you want to legalize vigilante justice, you better make sure you can outgun everyone. When it comes to the Internet, RIAA hasn't got a chance. Of course, this is why they went whining to Washington in the first place.
I'd love it if several of the RIAA people went to prison for live for hacking. Two wrongs make a righteous fantasy!
On my Linux box, I am using NetSaint to monitor the temperature. I have added scripts to kill SETI@Home and Folding@Home when the temperature gets to the warning levels (45C Mobo, 50C CPU) and start an orderly shutdown when the temperature gets to the critical levels (50C Mobo, 55C CPU). Killing the NULL tasks drops the temperature 5 degrees Celsius.
I expect a fair number of professors are close to my age (51). When I started, terminals were either unavailable, or too expensive for classwork. I wrote code, on paper, and then went and keyed it on punched cards. Then you turned it in and received the card deck and a listing back in: a few hours, a day, or even a week. A misplaced semi-colon cost you one turn around cycle. You had better be able to proof your work before the compiler gets your program or you will not get your work done in time.
There are still people who think this is the only proper way to program (see Cleanroom process).
What the original poster is telling me is that he is brittle, he can only code when Ares is rising, his favorite MP3 is playing, the sun isn't too bright, etc.
Now preferred conditions are fine, but "I can't code on paper". Fragile, brittle. I like white boards for design, paper for writing, terminals for editting, etc. I've designed on terminals, paper, backs of envelopes, cocktail napkins, etc. I've coded at the key punch, terminal, Starbucks, etc. I've debugged on cards w/ a listing, memory dumps, front panels, hex debbuggers, symbolic debuggers, IDEs, etc. That's what being a professional means. Otherwise you are a recreational coder.
"The only tool a programmer needs is a pencil with a five pound eraser." - circa mid 70's
Most people learn concrete first, then they can move to abstract. Without some programming language(s) to think in or weigh alternatives in, it gets difficult to consider abstract notions.
It sounds like you are trying to do what I tried, teaching black belt lessons to white belts. This does not work, even if the black belt lessons are on topics the white belts already have covered.
Not under this bill. It is not digital. And it predates the bill. However, you may find that nothing will come out on VHS tape. I think you can cough up the money to play a protected program once and record it in analog. However, the usual fair use, etc. rules apply.
That said, if this passes in anything like its current form, there will be even more restrictive legislation.
I just read the definition of an "interactive digital device" in the SSSCA draft. The little keyless access goody to unlock my car qualifies. It transmits, receives, and stores information in digital form. And this requires a copy protection device to protect Disney et al's intellectual property? You gotta be kidding!
Maybe the analysis didn't get it right. I've seen one connect attempt to port 80 since meltdown and there wasn't anything running on port 80 at that IP address, so it was probably wasn't Code Red, just a dork with a script.
People skills! Programmers can hide in their
caves and snarl when thrown their ration of caffeine and carbohydrates. Sysadmins gotta be able to smile while being asked: 1) to do the impossible, 2) Yet Another FAQ, 3) add another user, 4) restore from backup, 5) say no to some bigwig who wants the security policy violated for his/her personal whim, *) you get the idea.
Be good to your sysadmin, even if it isn't his/her day.
Mutt supports Maildir, MH, MMDF, and mbox formats out of the box. Works fine, been using it for several years.
As easy to use as the ical program (I liked Todo lists, graphical setting of appointments and warnings). Ability to send e-mail warnings to my cellphone so I don't have to carry it and a PDA w/ appointments. Way to extend repeat options (every 8th day, the two Thursdays before 2nd Sunday, are ones I need). Share calendars like Outlook Express. Reliability, unlike Outlook Express.
I have been in this business for 25 years. Being a task lead is the price I pay to get to do the high level design. I am an excellent programmer and a competent task lead and intend to stay that way. I would rather be doing what I am good at, but who doesn't.
Advice? Compliment good work. If you can't find any good work by someone, look harder, find them some place to succeed, or get rid of them. What out for heroes and saviors. They may be cranking out incomplete code to look good, that others will find or trip on the bugs and look bad. Anyone who is working 60+ hours/week isn't doing their job in the planning department. Remember you are dealing with people, they have lives, wives, kids, significant others, bad days, and deaths in the family. Learn something about the Meyers-Briggs Type Inventory. Extraverts annoy/terrify introverts by thinking out load. Sensation types annoy Intuitives by demanding facts, data, etc. Good intuitives annoy sensation types by being right without having facts, data to back it up. Process types are great in emergencies where the pre-made plans don't apply. Judgement types are great with setting schedules and planning (and reducing the number of emergencies). Try to understand peoples strengths and weaknesses. Let them flex their strengths and get them help with weak areas that are needed for their job. This is especially true for yourself. Read the magazines that slant towards technical management (e.g. Software Development).
Finally, ask your self if you really want to be a manager. My father and I both tried it and decided no, knowing it meant that our "juniors" would be making more money and have more authority.
Books: "Getting to Yes", "Getting Past No", "Getting Together", and all the rest by the Harvard Negotiation project. IIRC, the authors of the first are Ury and Fisher.
Testing is done for two reasons: to find bugs so they can be fixed and to demonstrate how good the product is. E.g., the FDA requires formal QA to do the latter. Users, coders, and testers are all equally adept at the former. Any large company has some body tasked with determining the quality (and suitability) of potential products and services that will be used company wide. They don't delegate or trust someone else to do that. This is in addition to any testing the original team did.
If there is a make check target, I feel a little better about the quality. They did some testing, they automated it so it probably get done with every release and most builds, etc. I know that some attention has been paid to testing. For example, the GNOME XML library has dozens of tests and takes about as long to run the tests as build the library. I has some assurance that there is some concern for quality.
Excuse the cynicism. My experience with QA people has not been good. There may be even fewer really good QA people than programmers. I have encountered a number of great programmers in 25 years in this business. I have met one great QA person (thanks Roger Mason wherever you are). The rest reinforced the notion that those that can do, those can't test (and criticise).
Oops, this should have been plain old text (POT?). 5 * X == X + (X left shifted 2)
I read a tech report sometime in 1997 or before that described an integer DCT with just shifts and simple constants (e.g., X * 5 == X + X 2). Maybe this is it, maybe it was prior art. I don't remember who wrote it or what organization it was. HTH
title says it all. Any database is subject to the second law of thermodynamics (in a closed system, entropy increases). Give them a little help.
Nerds are Boomers. Geeks are Gen X. I read User Friendly. However, most of the rest of the site is beyond me, different generation.
PC 99 means you have to buy all new cards, HW, printers, etc. Mac did it all right. Yeah, they sure did. My mother's Mac just died. To get an iMac she will have to replace the working printer or pay 80-100 bucks for a USB to serial adapter. I couldn't believe they didn't include a serial port.
GPG does not appear to have the wipe option of PGP, or rather, it doesn't complain and doesn't wipe the plaintext.