It is more efficient to run all turbines at a set performance. Therefore the electricity companies try and flatten out demand so it is constant across 24 hours. They do this by letting you heat your water in off-peak tanks that are timed to when demand is lowest.
The thing is in Australia some bright spark figured this out and we now pump water uphill overnight, buying the electricity cheap then let the water run downhill into a hydro-electric during the day and sell power back to them when the price is highest. Surely the same applies here, create the electricity and then store it somehow, pump water uphill, use batteries or store it in flywheels. Whatever works and is cheapest. At the very least if the windfarms are generating power then those coal fired powerstations would scale back production.
He is not saying that you must take a popular position just that you must take a position. I am also curious whether you read it to the end. The essay was interesting and meandering and all in all not directly pointed.
It is strange I went through Australian School and I was taught exactly as he described.
a) Take a position and argue it. This was what I was taught in Modern History for the HSC (11th & 12th year).
b) State the objective and restate the argument at the end.
These simple rules were given to me by my English teacher in year 7. Probably because I am a programmer type and want something to follow or else I am lost. If you were a natural then you did not 'need' rules to write an essay.
Depends upon your video card. If you have asked for help in such a vague way then I am sure you got less response than I am giving you. What video card, what driver are you using, etc.
Second, often features that are present in new software makes the application smarter and leaner so while nothing happens directly to the driver itself the applications using the X interface become leaner and meaner and therefore faster.
When you know where to put the printf I agree. I don't disagree with what you are saying however it is not the 'whole truth'. There is no golden bullet.
In any office suite there are thousands of inputs and thousands of outputs, work out the combinations to test this. No-one proves anything but the most trivial code or if they have I bet it was an academic not someone that works at coding for a living.
Now if you talk about test suites wrapped around the individual functions to exercise things then yes there are instances of this but this is not classic 'proving' but testing.
The latest versions have a LOT of changes to make the software more robust. It really is worth revisiting. If it crashes please let us know, we are interested in eliminating problems like this.
The software is not perfect but we are working on it:-)
Did you describe the problem and solution to them.
Seriously this really is the problem now. I had a problem with IE not loading a webpage, it locked up totally. I had 5 attempts to get Microsoft to acknowledge that I did not have a problem (I changed my page to not lockup once I figured it out) and accept that it was a bug that they could escalate to the developers.
I have no idea whether the problem ever left the call centre. The ability to describe problems and solutions directly to the developers is a bonus for Open Source.
Where do you put the printf if you have no idea where the problem is?
Duck over to OpenOffice.org and throw a few printf's to fix some of the bugs in the code. I use this technique at work where I work on program line counts in thousands of lines. First you have to find the point to put the code, in millions of lines you cannot do this with a look at the code.
What they say is a valid approach to software development. Developers cannot always totally correct the problems. Similar but more damning:
"In order to understand this, we have to understand a basic principle of fixes. You make the simplest code change required to fix the problem."
This again is a valid approach however it also encourages entrophy. You have to make occasional agressive changes to the code and stop patching it up. It is equivalent to painting a house for the 50 years, you eventually have to remove almost all the paint and start again. Where in the manual do they discuss this.
When someone does something stupid you blow your horn. When enough people have blown their horn at a driver they learn how to drive better.
How is silence better? The chaos of stupid people not 'knowing the rules' and driving on the wrong side of the road because no-one cares to tell them different.
The system is not perfect, however we have to attempt to make the web a better place for all.
I have found the way out of unpaid PC support. I have not run windows for 2 years, sorry I cannot help you.
The issue with this is that no attempt has been made to let the other party know that they are at risk. It is highly likely that it is a computer that has been comprimised itself.
Let the other party know via an email, at least an attempt to the ISP in question. It may not come to anything but at least you have communicated and potentially corrected another internet loophole.
The women I have worked with were not good coders however they are excellent at the business analysis side of things. Both opinions may reflect this.
There are also huge boys clubs and girls clubs in the tech industry. I worked in a company where you had to have a skirt to be promoted, and now in a company that is the reverse. There are a lot of women in the industry however they tend to be centralised in specific companies or industries. Perceptions will vary dramatically as a result.
TCP/IP was originally designed and built in a University environment to loose specifications given by the Military. All TCP/IP derives from BSD Unix which is Open Source. Most (if not all) implementations are based upon the BSD code.
Yes TCP/IP is everything to do with Open Source and by the way Open Standards.
First computer Z80 64k $5,000 (second hand) Second computer IBM AT $5,000 (second hand) Third computer 386/25 $5,000 (new) Fourth computer Pentium $4,000 Fifth computer Pentium $3,000 Current computer $1,500
As a programmer I no longer need to be on the bleeding edge just to do my work. A cheap computer is sufficiently fast. My requirements of a computer have gone down in essence.
There was actually a nobel proze given out for irrational economics. It outlines that people are not willing to follow obvious rational paths taking a hit now against later.
for example. I bought a car. A total dud and dead loss, should have sold it after a few months and lost 3,000 from 8,000 on it. I held on because I felt I could not 'loose' the 3,000 dollars. I ended up loosing a lot more than that, rational did not come into it. I knew what was right but emotionally I could not justify it the same way.
I agree that it is restrictive. It is your freedom to use it or not. It is your freedom to buy something else to use in your product.
You could use something which is LGPL where the "library" portion must be disclosed but the rest of your application may be closed.
It is the choice of person that wrote the software how they want to use it. This is their freedom when they work on something, as they could have easily made you pay for it. They in return would like you to develop open software for the masses, your choice to have freedom to distribute or to make money off the back of others without payment.
If the license is no good for your product then it does not matter who developed it you must pass it by and find another. This may be proprietary or open source.
Will NOT generate a warning under gcc 3.3 (-Wall with optimisation). This will:
int i; if( a )
i = 0; else if( b )
i = 1;
Compilers can be smarter and help us poor mortals along. There is code that will give warnings that are not strictly correct (other logic ensure that the unitialised variable is never referenced like a boolean guard value) but it is simple enough to code in a reasonable default in case some idiot does a poor change later on.
Ignoring the warning on the other hand will lead to program crashes in obscure ways. It works on Solaris and Windows but not on Linux. I am currently working through OpenOffice.org removing unitialised variables, costs a little effort and potentially a good pay back on my time in program stability. It may not correct all the bugs but it should make the problems repeatable because it starts from a known value.
I was at a conference this week and the comment was made that the students do not understand that the "degree/cert" is the key to the interview, their real knowledge got them the job. Do not forget that Open Source is a certification, how many commits have been accepted from you.
My Mum also told me that as a secretary she would filter the resumes her manager based on rules. Uni degree or 5 years of experience. The manager did not see your resume if you did not fit a 'tick list'. So have the appropriate experience or qualifications to get to the top of the resume pile or you will not get an interview.
Any qualifications will get you to the interview what you do once there opens the door. This was pretty much my story, I had a High Distinction in a single computing subject and no other qualification. I play with computers during high school, this was before the IBM PC was released. It took me about 8 years to get an 'official' programming job. I was configuring reports, doing operations management, loading tapes for a long time before my break came. So if you are at the beginning take the loan get the certifications. If you are not willing to bet on yourself why would anyone else do it.
I read up on the juniors that are "sure" their ability is worth a shot. They are "smarter" that a qualified person. To be sure there is the expectional case that this is true. Most homebrew people cannot cope outside reinstalling a simple computer. Depth on one type if computer does not equal breadth. Certification forces you to learn some of this breadth and opens eyes as to how much there is to actually learn. A failure breeds some humility.
I also read with joy the "qualified" person saying they would not trust an unqualified hack. I lack ANY formal qualifications. I do not have CCNA, I just taught it for a while. I am not a qualified programmer but I just finished a semester teaching 120 students. I really do believe that I am better qualified than most "papered" people out there. If you really want to excel at computer you must be willing to read and learn. You must be willing to struggle through some awful textbooks at times (I read a windows programming manual, took me 6 months! Bad was not an understatement). You must invest your personal time to learn, write Open Source software like OpenOffice.org (plug!)
So what does make the difference. Interview well, actually like the person you are talking too. If you think they are high paying idiots it is likely you will not perform and then you will loose the job. Like the job first and let the money come to you. It is a formula that has worked for me.
What has happened is that we have in part had a major release for BETA tsting that a lot of people have started using (Alpha test was 2.5) so there is a shakeout of problems. The same occurs in Windows with early release users raising bugs tht are fixed in the final release, if and only if they are major enough. Linux is a bit more open to repairing bugs faster so there is a cycle of fast updates. As noted elsewhere it will slow down a lot shortly. Then a new alpha branch (2.7) will be openned and a lot of work will go on there. Alpha branches (2.7) are where angles fear to tread.
Reason 2: Linux kernel = low level stuff + drivers.
Windows has the drivers externalised a fair amount so that the vendor can replace the driver without specific change to Windows. (This is good). Linux does more with imbedding drivers for performance (This is good too for different reasons). Updates to drivers therefore cause more releases (perceived as bad, but not really)
Apparently mice work in the USB port but not in the PS/2 port. This was discussed on the sydney LUG recently. I can definitely say it works in the USB port.
The comments made about Redhat can be applied to many company supported projects. Now that is scary. It takes a lot more time to be "trusted" by a company than Open Source projects not run by companies. Funny, sad and scary.
We chase away enthusiastic supporters that can really help by not having a process which they can follow to get real access to these systems and make a difference.
Slashdot Mirror
It is more efficient to run all turbines at a set performance. Therefore the electricity companies try and flatten out demand so it is constant across 24 hours. They do this by letting you heat your water in off-peak tanks that are timed to when demand is lowest.
The thing is in Australia some bright spark figured this out and we now pump water uphill overnight, buying the electricity cheap then let the water run downhill into a hydro-electric during the day and sell power back to them when the price is highest. Surely the same applies here, create the electricity and then store it somehow, pump water uphill, use batteries or store it in flywheels. Whatever works and is cheapest. At the very least if the windfarms are generating power then those coal fired powerstations would scale back production.
He is not saying that you must take a popular position just that you must take a position. I am also curious whether you read it to the end. The essay was interesting and meandering and all in all not directly pointed.
It is strange I went through Australian School and I was taught exactly as he described.
a) Take a position and argue it. This was what I was taught in Modern History for the HSC (11th & 12th year).
b) State the objective and restate the argument at the end.
These simple rules were given to me by my English teacher in year 7. Probably because I am a programmer type and want something to follow or else I am lost. If you were a natural then you did not 'need' rules to write an essay.
Depends upon your video card. If you have asked for help in such a vague way then I am sure you got less response than I am giving you. What video card, what driver are you using, etc.
Second, often features that are present in new software makes the application smarter and leaner so while nothing happens directly to the driver itself the applications using the X interface become leaner and meaner and therefore faster.
When you know where to put the printf I agree. I don't disagree with what you are saying however it is not the 'whole truth'. There is no golden bullet.
The whole statement is total crap.
In any office suite there are thousands of inputs and thousands of outputs, work out the combinations to test this. No-one proves anything but the most trivial code or if they have I bet it was an academic not someone that works at coding for a living.
Now if you talk about test suites wrapped around the individual functions to exercise things then yes there are instances of this but this is not classic 'proving' but testing.
Load times are a real focus of attention by a lot of developers. You can expect improvements on this in the next major release.
The latest versions have a LOT of changes to make the software more robust. It really is worth revisiting. If it crashes please let us know, we are interested in eliminating problems like this.
:-)
The software is not perfect but we are working on it
Did you describe the problem and solution to them.
Seriously this really is the problem now. I had a problem with IE not loading a webpage, it locked up totally. I had 5 attempts to get Microsoft to acknowledge that I did not have a problem (I changed my page to not lockup once I figured it out) and accept that it was a bug that they could escalate to the developers.
I have no idea whether the problem ever left the call centre. The ability to describe problems and solutions directly to the developers is a bonus for Open Source.
Where do you put the printf if you have no idea where the problem is?
Duck over to OpenOffice.org and throw a few printf's to fix some of the bugs in the code. I use this technique at work where I work on program line counts in thousands of lines. First you have to find the point to put the code, in millions of lines you cannot do this with a look at the code.
What they say is a valid approach to software development. Developers cannot always totally correct the problems. Similar but more damning:
"In order to understand this, we have to understand a basic principle of fixes. You make the simplest code change required to fix the problem."
This again is a valid approach however it also encourages entrophy. You have to make occasional agressive changes to the code and stop patching it up. It is equivalent to painting a house for the 50 years, you eventually have to remove almost all the paint and start again. Where in the manual do they discuss this.
When someone does something stupid you blow your horn. When enough people have blown their horn at a driver they learn how to drive better.
How is silence better? The chaos of stupid people not 'knowing the rules' and driving on the wrong side of the road because no-one cares to tell them different.
The system is not perfect, however we have to attempt to make the web a better place for all.
I have found the way out of unpaid PC support. I have not run windows for 2 years, sorry I cannot help you.
Implying that all geeks are ugly?
There are ugly and good looking geeks. Talk about a heap of gross generalisations on this topic.
The issue with this is that no attempt has been made to let the other party know that they are at risk. It is highly likely that it is a computer that has been comprimised itself.
Let the other party know via an email, at least an attempt to the ISP in question. It may not come to anything but at least you have communicated and potentially corrected another internet loophole.
The women I have worked with were not good coders however they are excellent at the business analysis side of things. Both opinions may reflect this.
There are also huge boys clubs and girls clubs in the tech industry. I worked in a company where you had to have a skirt to be promoted, and now in a company that is the reverse. There are a lot of women in the industry however they tend to be centralised in specific companies or industries. Perceptions will vary dramatically as a result.
TCP/IP was originally designed and built in a University environment to loose specifications given by the Military. All TCP/IP derives from BSD Unix which is Open Source. Most (if not all) implementations are based upon the BSD code.
Yes TCP/IP is everything to do with Open Source and by the way Open Standards.
First computer Z80 64k $5,000 (second hand)
Second computer IBM AT $5,000 (second hand)
Third computer 386/25 $5,000 (new)
Fourth computer Pentium $4,000
Fifth computer Pentium $3,000
Current computer $1,500
As a programmer I no longer need to be on the bleeding edge just to do my work. A cheap computer is sufficiently fast. My requirements of a computer have gone down in essence.
There was actually a nobel proze given out for irrational economics. It outlines that people are not willing to follow obvious rational paths taking a hit now against later.
for example. I bought a car. A total dud and dead loss, should have sold it after a few months and lost 3,000 from 8,000 on it. I held on because I felt I could not 'loose' the 3,000 dollars. I ended up loosing a lot more than that, rational did not come into it. I knew what was right but emotionally I could not justify it the same way.
I agree that it is restrictive. It is your freedom to use it or not. It is your freedom to buy something else to use in your product.
You could use something which is LGPL where the "library" portion must be disclosed but the rest of your application may be closed.
It is the choice of person that wrote the software how they want to use it. This is their freedom when they work on something, as they could have easily made you pay for it. They in return would like you to develop open software for the masses, your choice to have freedom to distribute or to make money off the back of others without payment.
If the license is no good for your product then it does not matter who developed it you must pass it by and find another. This may be proprietary or open source.
For the record
int i;
if( a )
i = 0;
else
i = 1;
Will NOT generate a warning under gcc 3.3 (-Wall with optimisation). This will:
int i;
if( a )
i = 0;
else if( b )
i = 1;
Compilers can be smarter and help us poor mortals along. There is code that will give warnings that are not strictly correct (other logic ensure that the unitialised variable is never referenced like a boolean guard value) but it is simple enough to code in a reasonable default in case some idiot does a poor change later on.
Ignoring the warning on the other hand will lead to program crashes in obscure ways. It works on Solaris and Windows but not on Linux. I am currently working through OpenOffice.org removing unitialised variables, costs a little effort and potentially a good pay back on my time in program stability. It may not correct all the bugs but it should make the problems repeatable because it starts from a known value.
I was at a conference this week and the comment was made that the students do not understand that the "degree/cert" is the key to the interview, their real knowledge got them the job. Do not forget that Open Source is a certification, how many commits have been accepted from you.
My Mum also told me that as a secretary she would filter the resumes her manager based on rules. Uni degree or 5 years of experience. The manager did not see your resume if you did not fit a 'tick list'. So have the appropriate experience or qualifications to get to the top of the resume pile or you will not get an interview.
Any qualifications will get you to the interview what you do once there opens the door. This was pretty much my story, I had a High Distinction in a single computing subject and no other qualification. I play with computers during high school, this was before the IBM PC was released. It took me about 8 years to get an 'official' programming job. I was configuring reports, doing operations management, loading tapes for a long time before my break came. So if you are at the beginning take the loan get the certifications. If you are not willing to bet on yourself why would anyone else do it.
I read up on the juniors that are "sure" their ability is worth a shot. They are "smarter" that a qualified person. To be sure there is the expectional case that this is true. Most homebrew people cannot cope outside reinstalling a simple computer. Depth on one type if computer does not equal breadth. Certification forces you to learn some of this breadth and opens eyes as to how much there is to actually learn. A failure breeds some humility.
I also read with joy the "qualified" person saying they would not trust an unqualified hack. I lack ANY formal qualifications. I do not have CCNA, I just taught it for a while. I am not a qualified programmer but I just finished a semester teaching 120 students. I really do believe that I am better qualified than most "papered" people out there. If you really want to excel at computer you must be willing to read and learn. You must be willing to struggle through some awful textbooks at times (I read a windows programming manual, took me 6 months! Bad was not an understatement). You must invest your personal time to learn, write Open Source software like OpenOffice.org (plug!)
So what does make the difference. Interview well, actually like the person you are talking too. If you think they are high paying idiots it is likely you will not perform and then you will loose the job. Like the job first and let the money come to you. It is a formula that has worked for me.
Experience is the best certification.
Sending credit card information in an email is less than optimal from a security perspective. I am confused why you would even consider doing this.
Reason 1: K 2.6 is really a beta test Windows:
What has happened is that we have in part had a major release for BETA tsting that a lot of people have started using (Alpha test was 2.5) so there is a shakeout of problems. The same occurs in Windows with early release users raising bugs tht are fixed in the final release, if and only if they are major enough. Linux is a bit more open to repairing bugs faster so there is a cycle of fast updates. As noted elsewhere it will slow down a lot shortly. Then a new alpha branch (2.7) will be openned and a lot of work will go on there. Alpha branches (2.7) are where angles fear to tread.
Reason 2: Linux kernel = low level stuff + drivers.
Windows has the drivers externalised a fair amount so that the vendor can replace the driver without specific change to Windows. (This is good). Linux does more with imbedding drivers for performance (This is good too for different reasons). Updates to drivers therefore cause more releases (perceived as bad, but not really)
Hope this helps...
Apparently mice work in the USB port but not in the PS/2 port. This was discussed on the sydney LUG recently. I can definitely say it works in the USB port.
It is interesting to see RedHat argue for the same Stability that Debian has had forever. RHEL has a 2 year release cycle and so does Debian stable.
I notice that there is no comment to the middle ground, testing is a good one to go with and has (sometimes) faster updates to security fixes.
Stable is really meant to be stable, it should work predictably first, reliably second.
The comments made about Redhat can be applied to many company supported projects. Now that is scary. It takes a lot more time to be "trusted" by a company than Open Source projects not run by companies. Funny, sad and scary.
We chase away enthusiastic supporters that can really help by not having a process which they can follow to get real access to these systems and make a difference.