Which is why you need the _employer's_ permission, and not just the network manager's. It doesn't belong to the network manager, so he can't give it away. Getting management to bless such a thing is different (and appropriate).
"In any large software system, the truly unique code probably accounts for about 1% of the source."
In a novel, there are often less than 1% truly unique words in the composition. It is the combination of those words together, in major section and its entirety, that makes a novel "novel".
"All commercial software should include a copy of its full source..."
I suggest that you reconsider your use of the word "should". Instead, consider the marketplace in terms of delivering value. The act of marketing something is a complex activity which involves the exchange of value between parties. What value is in it for the buyer? How many consumers are how likely to spend how much on software that is delivered with source? How many consumers will see it as a purchasing discriminator? What is in it for the seller? What would motivate a seller to do this?
Lastly, I humbly suggest that you haven't had your fingers in anything other than the most exceptional of open source efforts. I have seen plenty of open source, and it is as bad and worse as the worst closed source software that I've had the misfortune of seeing. Open source is no cure for software quality; software quality happens when people care about it, open source or no.
Jedi: "This is not the magic wand that you are looking for."
You: "This is not the magic wand that I am looking for."
While I'm sure you intended to be funny, showing a customer bad code is a bad idea. It risks making them wonder how reliable and safe your code is, for one thing. This will make them consider someone else.
While I agree with your assessment that XML is really just a bad s-expression, xml does offer one thing that sexp doesn't: forced agreement between the begin and end tags. Of course this can be implemented in sexp, too (tag value value tag). The benefits are the same either way: the parser can recover from malformed pairs much more sensibly than it can from unbalanced parens.
Actually, this was quite an interesting chart. Seeing that Ultra-320 is twice PCI, I wonder if A) anyone makes Ultra-320 for PCI, and B) anyone is stupid enough to buy it?
It's not preposterous if he legitimately believes that Intel's throwing good money after bad. For example if one holds the belief that the Itanium won't recoup its investment cost, cancelling it now's a good idea, no matter how much money has been spent.
This isn't really correct. AMD is targeting the entire x86 industry with Hammer, and intends to retire Athlon as a line within a fairly short time frame after Hammer comes out.
This chunking is described in great detail in the original POWER4 public design documents. It's referred to in passing as a redeeming feature, borrowed from VLIW concepts. The suggestion is that its a part of traditional VLIW that could be leveraged into a non-VLIW design.
EULA's no longer require testing in court like they once did. DMCA gives them legal weight. Unless you believe that DMCA provisions can be ruled unconstitutional by appelate courts, we're stuck until the law is changed.
...and the average American requires over 45,000 pounds of newly-mined minerals every year.
Wuut? Cleter. I think I'm gonna try out that new fangled calcumalator I bawwt last year. Lemme se. foooorty-fiyve thousand, wheh! that's a biggun, hit that there divide key, how many days in a year, Cleter? 365? Is dat right. Alright. Where wuz I. Right. That divide button. And three-hunndrid-sixty-fiyve! Holly, hell, Cleter! The avrage 'merican eats 128 pounds a food a day. I'll be. I ate that much, I wouldn't be crappin' for a week, now would I?
Why is no one going after him under SLPP provisions? In California, at least, a company can get in big trouble by attempting to use the courts to squelch free speech.
This wasn't meant as a literal template. It was meant as an example. Something appropriately sincere will substitute fine, such "as I have an avid ongoing interest in public key infrastructure, which is one of your areas of work." The purpose here is to demonstrate a commonality and alignment of some kind. Use your imagination, just remember that it has to be very brief in a cover letter.
C//
Never underestimate a good cover letter
on
Resume Tips For Jobs
·
· Score: 3, Informative
I've reviewed a lot of resumes. A lot. One piece of advice; write a cover letter, very brief (a paragraph!) that is costomized _specifically_ for where you are applying. Furthermore, I suggest that you touch up your resume for every job.
The point of the cover letter: to get the interviewer to read the resume, and to positively bias them towards what they read there.
The point of the resume: to get the interviewer to want to interview you.
Don't oversell any one point. It's a waste of energy. The point of your resume is not to get the interviewer to want to hire you. The point of your resume is to get the interviewer to want to interview you.
For tech jobs, make sure you have a "buzzword" section. Little to no prose is acceptible in this section. We interviewers have short attention spans. It's common for us to use a yellow hiliter and simply hilite your technical skills. It's quite possible that we can make the decision to interview you on your cover letter alone. To wit:
" Dear Sir or Madam,
I noticed that XYZ widget company is looking for a skilled senior XXX engineer. I've long had an interest in your company, and I'm enthused with the work that you've done, particularly in the area of ZZZ research. I have up-to-date skills in XXX-A, XXX-B, and XXX-C. Let's schedule an interview to see how it would be possible for me to contribute to your team.
--[Signed, hotshot]"
Anyway, hope this helps.
C//
Re:Migration path, opteron, and stuff...
on
Itanium Problems
·
· Score: 2
In the same way, most applications aren't even aware of 64 bits. For the lazy man's migration path of using the same apps on a 64 bit system, there will be no advantage whatsoever of using a 64 bit system.
This isn't quite correct, because, at a minimum, the operating system can arrange each 32 bit application _at _least_ be given its _OWN_ 32 bit address space (using a sort of virtual segmenting) for 4 gig of addressable memory per application.
Meanwhile, the main advantage isn't that any one older programs can or can't get memory, but rather that they all continue to work, and the few you need to upgrade to 64 bit addressing can be done incrementally. This saves you quite a lot of $$$ on software budgets.
One of our founding curmudgeons once opined that since all government was obviously evil, the less of it the better, except whatever minimum level of evil was actually necessary. Good point, though. This rule appears to not be adhered to at the level of group decision.
The problem is, they made a mistake about who they were stealing FROM. They are stealing from the affiliates, this is outright fraud, and the shrink wrapped agreement is hardly relevant. Two parties cannot agree to relinquish the rights of a third party!!!
Why do they believe that the user's agreement makes this legal? An agreement between two parties cannot, as a general rule, relinquish the rights of a third party. This is almost certainly felony fraud, earning the players 5-10 in the clink. I hope the players have good attorneys. As soon as the victims (hint: not the user) hear about this and file a complaint, charges will be filed. They're not going to be civil charges, and it's not going to be judge Judy.
Some people are really stupid about the internet! "Oh, this is the internet, therefore if I do something unethical, they must not have passed a law against that yet." Not so. God. DUMB!!!!!
Yes, I know you are right. Amongst other things, I won't be stuck with 64K per thread stack in Linux, and as you say, I could use 64 bit alpha linux. I'm looking forward to Hammer, actually.
The end result is, even if Windows does try to create 64k worth of memory segment space for a process, unless it is actually reading or writing to a byte in each 4k chunk, its internal VM will not allocate physical memory for the whole 64k.
Yes. Quite true. I hade a problem a while back on Windows which took me a bit of reading through the documentation (and verifying with some low level sys calls) to determine that what was happening is that I was running out of "reserve memory". Which is to say that, while I had plenty of physical memory left, all the address space had been used up. You can do this very easily by creating thousands of threads on your computer. To get a large number of these threads, you'll have to push the default stack size to its minimum, 64K. I was a bit disatisfied with this minimum, but I suppose I'll live with it now (or port to linux) if I have to, or upgrade to a 64 bit os if it becomes a practical limit in the future.
The 64K page size is Windows' page size. I can only assume that the poster stating that the intel hardware page size is 4K. I would suppose this means that a Window's (2K,NT) page of 64K is assembled from 16 hardware pages, then. The Windows' page size of 64K is in their documentation. I never paused to think about how this interfaces with hardware pages...
Slashdot Mirror
not all employers are sour pusses, you know
Which is why you need the _employer's_ permission, and not just the network manager's. It doesn't belong to the network manager, so he can't give it away. Getting management to bless such a thing is different (and appropriate).
C//
You've just advised people to engage in a behavior which can justify their termination. Did you know that?
Just curious.
C//
"In any large software system, the truly unique code probably accounts for about 1% of the source."
In a novel, there are often less than 1% truly unique words in the composition. It is the combination of those words together, in major section and its entirety, that makes a novel "novel".
"All commercial software should include a copy of its full source..."
I suggest that you reconsider your use of the word "should". Instead, consider the marketplace in terms of delivering value. The act of marketing something is a complex activity which involves the exchange of value between parties. What value is in it for the buyer? How many consumers are how likely to spend how much on software that is delivered with source? How many consumers will see it as a purchasing discriminator? What is in it for the seller? What would motivate a seller to do this?
Lastly, I humbly suggest that you haven't had your fingers in anything other than the most exceptional of open source efforts. I have seen plenty of open source, and it is as bad and worse as the worst closed source software that I've had the misfortune of seeing. Open source is no cure for software quality; software quality happens when people care about it, open source or no.
Jedi: "This is not the magic wand that you are looking for."
You: "This is not the magic wand that I am looking for."
C//
While I'm sure you intended to be funny, showing a customer bad code is a bad idea. It risks making them wonder how reliable and safe your code is, for one thing. This will make them consider someone else.
C//
While I agree with your assessment that XML is really just a bad s-expression, xml does offer one thing that sexp doesn't: forced agreement between the begin and end tags. Of course this can be implemented in sexp, too (tag value value tag). The benefits are the same either way: the parser can recover from malformed pairs much more sensibly than it can from unbalanced parens.
C//
Actually, this was quite an interesting chart. Seeing that Ultra-320 is twice PCI, I wonder if A) anyone makes Ultra-320 for PCI, and B) anyone is stupid enough to buy it?
C//
It's not preposterous if he legitimately believes that Intel's throwing good money after bad. For example if one holds the belief that the Itanium won't recoup its investment cost, cancelling it now's a good idea, no matter how much money has been spent.
C//
This isn't really correct. AMD is targeting the entire x86 industry with Hammer, and intends to retire Athlon as a line within a fairly short time frame after Hammer comes out.
C//
computing in chunks... sounds a lot like a Cray
This chunking is described in great detail in the original POWER4 public design documents. It's referred to in passing as a redeeming feature, borrowed from VLIW concepts. The suggestion is that its a part of traditional VLIW that could be leveraged into a non-VLIW design.
C//
It's insignificant as a work, so of course there is no copyright, you yahoo.
C//
EULA's no longer require testing in court like they once did. DMCA gives them legal weight. Unless you believe that DMCA provisions can be ruled unconstitutional by appelate courts, we're stuck until the law is changed.
C//
Modding your X-box can't be illegal because you own it.
You are arguing about what _ought_ to be, not what is. If it's illegal, it's illegal. The DMCS stinks, but facts are facts.
C//
...and the average American requires over 45,000 pounds of newly-mined minerals every year.
Wuut? Cleter. I think I'm gonna try out that new fangled calcumalator I bawwt last year. Lemme se. foooorty-fiyve thousand, wheh! that's a biggun, hit that there divide key, how many days in a year, Cleter? 365? Is dat right. Alright. Where wuz I. Right. That divide button. And three-hunndrid-sixty-fiyve! Holly, hell, Cleter! The avrage 'merican eats 128 pounds a food a day. I'll be. I ate that much, I wouldn't be crappin' for a week, now would I?
Yeee haww.
C//
Why is no one going after him under SLPP provisions? In California, at least, a company can get in big trouble by attempting to use the courts to squelch free speech.
C//
This wasn't meant as a literal template. It was meant as an example. Something appropriately sincere will substitute fine, such "as I have an avid ongoing interest in public key infrastructure, which is one of your areas of work." The purpose here is to demonstrate a commonality and alignment of some kind. Use your imagination, just remember that it has to be very brief in a cover letter.
C//
I've reviewed a lot of resumes. A lot. One piece of advice; write a cover letter, very brief (a paragraph!) that is costomized _specifically_ for where you are applying. Furthermore, I suggest that you touch up your resume for every job.
The point of the cover letter: to get the interviewer to read the resume, and to positively bias them towards what they read there.
The point of the resume: to get the interviewer to want to interview you.
Don't oversell any one point. It's a waste of energy. The point of your resume is not to get the interviewer to want to hire you. The point of your resume is to get the interviewer to want to interview you.
For tech jobs, make sure you have a "buzzword" section. Little to no prose is acceptible in this section. We interviewers have short attention spans. It's common for us to use a yellow hiliter and simply hilite your technical skills. It's quite possible that we can make the decision to interview you on your cover letter alone. To wit:
"
Dear Sir or Madam,
I noticed that XYZ widget company is looking for a skilled senior XXX engineer. I've long had an interest in your company, and I'm enthused with the work that you've done, particularly in the area of ZZZ research. I have up-to-date skills in XXX-A, XXX-B, and XXX-C. Let's schedule an interview to see how it would be possible for me to contribute to your team.
--[Signed, hotshot]"
Anyway, hope this helps.
C//
In the same way, most applications aren't even aware of 64 bits. For the lazy man's migration path of using the same apps on a 64 bit system, there will be no advantage whatsoever of using a 64 bit system.
This isn't quite correct, because, at a minimum, the operating system can arrange each 32 bit application _at _least_ be given its _OWN_ 32 bit address space (using a sort of virtual segmenting) for 4 gig of addressable memory per application.
Meanwhile, the main advantage isn't that any one older programs can or can't get memory, but rather that they all continue to work, and the few you need to upgrade to 64 bit addressing can be done incrementally. This saves you quite a lot of $$$ on software budgets.
C//
...and because of its monstruosities (8 registers ? stack-based FP ?) it has become a major hurdle in staying on Moore's curve...
Could have fooled me. It seems like just yesterday that MIPS said they would change the world. Not buying it, this time around.
C//
One of our founding curmudgeons once opined that since all government was obviously evil, the less of it the better, except whatever minimum level of evil was actually necessary. Good point, though. This rule appears to not be adhered to at the level of group decision.
C//
The problem is, they made a mistake about who they were stealing FROM. They are stealing from the affiliates, this is outright fraud, and the shrink wrapped agreement is hardly relevant. Two parties cannot agree to relinquish the rights of a third party!!!
C//
Why do they believe that the user's agreement makes this legal? An agreement between two parties cannot, as a general rule, relinquish the rights of a third party. This is almost certainly felony fraud, earning the players 5-10 in the clink. I hope the players have good attorneys. As soon as the victims (hint: not the user) hear about this and file a complaint, charges will be filed. They're not going to be civil charges, and it's not going to be judge Judy.
Some people are really stupid about the internet! "Oh, this is the internet, therefore if I do something unethical, they must not have passed a law against that yet." Not so. God. DUMB!!!!!
C//
Yes, I know you are right. Amongst other things, I won't be stuck with 64K per thread stack in Linux, and as you say, I could use 64 bit alpha linux. I'm looking forward to Hammer, actually.
C//
The end result is, even if Windows does try to create 64k worth of memory segment space for a process, unless it is actually reading or writing to a byte in each 4k chunk, its internal VM will not allocate physical memory for the whole 64k.
Yes. Quite true. I hade a problem a while back on Windows which took me a bit of reading through the documentation (and verifying with some low level sys calls) to determine that what was happening is that I was running out of "reserve memory". Which is to say that, while I had plenty of physical memory left, all the address space had been used up. You can do this very easily by creating thousands of threads on your computer. To get a large number of these threads, you'll have to push the default stack size to its minimum, 64K. I was a bit disatisfied with this minimum, but I suppose I'll live with it now (or port to linux) if I have to, or upgrade to a 64 bit os if it becomes a practical limit in the future.
C//
The 64K page size is Windows' page size. I can only assume that the poster stating that the intel hardware page size is 4K. I would suppose this means that a Window's (2K,NT) page of 64K is assembled from 16 hardware pages, then. The Windows' page size of 64K is in their documentation. I never paused to think about how this interfaces with hardware pages...
C//
Well, that may be the case. I was making more of a reference to the reserve memory lower limit on a thread's stack size.
C//