[...] you're more likely to sight the yeti this way than not.
Actually you're more likely not to sight the yeti this way, because there is no yeti. At least their way the scientists can drink vodka and have a story that might get them some tail in the future (so long as they leave out the part about the yeti and focus on the snow capped mountains).
Why do people want e-voting machines? Automatic counting is quicker and less costly than paying all the ballot counters.
However, early voting is allowed like the entire month of november by mail-in, and because the job doesn't need to be done all in one day you pay less ballot counters and save money. We should do away with election day, make it election month, and get rid of these stupid electronic voting systems. Don't even need to use the postal service to have that interference, just setup some secure ballot boxes around town that the counters will collect and count daily. Hell put the counters in them, just use them armored money trucks. They already have the 24/7 satelite linked cameras in them to have remote eyes ensuring the counters aren't screwing with votes.
Capitalism is about utilizing all available avenues to come up with the most efficient means of capitalizing, unfortunately the government makes itself the most efficient "capitlizee", so we end up with patents for avoiding taxes and lobbyists making millions of dollars a year because lobbying the government gains more capital than the millions in lobbying costs for the people they lobby for.
Haha I didn't even catch this, but you're absolutely right. I too recall looking at a diagnostics table in a motherboard manual telling me what the beeps meant when I screwed something up..
Coerce, threaten with bodily harm, you know, I'm up for whatever makes him debug my code for me. The little bastard will have to work if he wants to be a part of this family!
I'm planning on teaching my kid to solder just after CPU + Heatsink installation, and before C. So somewhere around 4 years old. My kid's going to pwn me when he's 9. My own personal debugger.
Spoken like a man that has no kids.The reality is for the first 2 years unless you're lucky and has a kid that sleeps you'll be too tired and sleep deprived to do much of anything.
Actually I do have a kid who's about to turn 2, and I was lucky, he slept through the night from month 3 on.:) Moreover, I was kidding ya wank. I learned to program when I was 8 however if dos batch scripts count, and whatever language hypercard and hyperstudio ran on when I was 8 or 9, and at 11 C and spent a ton of time rooting around in makefiles thinking I was "fixing" them when really I had borked my distro and had to hack the makefiles to get the builds to work.
Children can do a hell of a lot more than we give them credit for if you just let them. Too often people are assumed to have limited abilities due to their age. As someone who has for 11 years been a professional programmer, and only just now not the youngest person in the company I work for (I think? Might be wrong), I can truly say people truly project their own limits onto those around them WAYYYY too much.
The only advantage for ARM is the lower power requirement, so if Intel can make their chips less power hungry, they can take over some of the market.
Thankyou for finally speaking the truth. I recognize that ARM is good for mobile phones because of it's cycles/watts, but either I am seriously missing something or people are nutters for not thinking that a modern chip architected to run something as bulky as windows and it's countless applications of bloat will easily smear ARMs face in the mud when it comes to performance.
The only real question now is, does intel stand a bloody chance at lowering the power cost of their architecture? If they can do it, I am on board immediately. I do realize they and AMD have both failed to show any ability to get down to the power efficiency of ARM in the past, I'm still rooting for the chip powering my HTPC to run at a power efficiency to run my phone.
I'm planning on teaching my kid to solder just after CPU + Heatsink installation, and before C. So somewhere around 4 years old. My kid's going to pwn me when he's 9. My own personal debugger.
You're right, because the $1M/year salary isn't enough to take care of the CEO when they take a risk, make a mistake, and get fired, they have to count on that measley sum to pay the bills, so they better not take risks!
Couldn't agree more, was my first too as will it be my son's. However I must say, reading through these comments and recognizing yours I can't help but wonder if our affinity for the KnR as a starter might be a symptom of something else: I am a *completely* hands on learner. I failed high school and college because of this, but succeed in my software career to great effect. I think the density and conciseness of the KnR worked so well for me possibly in relation to this fact, and not as well for many, as true hands on learners really aren't the norm.
There are two reasons the KnR is THE programming bible the way I figure it
The functionality it explains about how to instruct a computer, in a way that makes it clear what the computer is *actually* doing without going to ASM, transcends languages. In a very short read you can come away understanding: strings are actually character arrays, which are actually just bytes with a particular set of values, and you have to allocate memory for things real time and release it or else memory leaks. Find any modern day programmer who hasn't read the KnR and ask them to lay a string out in memory on a white board and they would probably stare at you blankly. I can't count the times I've heard people talking about memory leaks but not able to explain how it actually happens.
Also, it's writing is so direct and to the point, concise, a complete exercise in Strunk 'n White style writing, that makes these concepts easy for anyone. It was my first when I was 11, as will it be my son's first.
3rd, this was the best next step after the KnR when I was a teenager. Though anyone saying the KnR isn't good for a beginner is a nutjob, the strunk 'n white style writing- direct and to the point, gives a foundation for all programming in so clear and concise a manner, you'd be nuts to call it difficult.
Here here. Engineering is hard, but if you can work out the mental gymnastics required to model complex things mentally and recognize the design flaws while balancing competing interests- You will have work for life. It's true that at a certain age, the quality of the work available to you will decline, and you will probably never become mega rich short of pulling off a gates or zuckerberg. But unless you're especially needy or wasteful you will always have a solid middle class life style available to you. Smart people become Engineers for stability, and a few really smart people do it because they can't help designing complex things.
However the truth of the matter is as I prefaced this, it is hard, and school is not. Thus a degree rarely equals a competence, and as such it is my experience that these days people are great at web browsing, but somewhat short on understanding what makes a web browser.
If he wants to stay in academia, great, if he wants to get into the software industry, he better take that math VERY seriously to work in the algorithm portions of software: compression or crypto, and sometimes data mining. If his math isn't up to snuff to really wrestle with those things, it will be unlikely his software skills will be at the ready for serious industry work without more significant post-grad industry experience vs that of a CS major. Though from interviews I've done, pure CS doesn't mean you know much more than syntax these days.. but maybe that depends on the particular school you go to.
I guess one thing I would say as well is, anyone who can wrap their head around pointers and recursion and make the step past those concepts, then they are among the rare few who truly belong doing software work and should go CS all the way.
I can't use a mac to save my life, so apparently that guy can't please everyone which is the parents point
Resigned is a strong word for took his miillions in parachute and went home.
Next up: Film turns Linux into date preventer
[...] you're more likely to sight the yeti this way than not.
Actually you're more likely not to sight the yeti this way, because there is no yeti. At least their way the scientists can drink vodka and have a story that might get them some tail in the future (so long as they leave out the part about the yeti and focus on the snow capped mountains).
I call gotcha reporting!
This c# code is stupid. 3 elements of the same type would be in an array not a tuple and would then read fine
Users who are managers.
Why do people want e-voting machines? Automatic counting is quicker and less costly than paying all the ballot counters. However, early voting is allowed like the entire month of november by mail-in, and because the job doesn't need to be done all in one day you pay less ballot counters and save money. We should do away with election day, make it election month, and get rid of these stupid electronic voting systems. Don't even need to use the postal service to have that interference, just setup some secure ballot boxes around town that the counters will collect and count daily. Hell put the counters in them, just use them armored money trucks. They already have the 24/7 satelite linked cameras in them to have remote eyes ensuring the counters aren't screwing with votes.
It's police officers all the way down?
Capitalism is about utilizing all available avenues to come up with the most efficient means of capitalizing, unfortunately the government makes itself the most efficient "capitlizee", so we end up with patents for avoiding taxes and lobbyists making millions of dollars a year because lobbying the government gains more capital than the millions in lobbying costs for the people they lobby for.
What about the red earth? It's an earth too!
Haha I didn't even catch this, but you're absolutely right. I too recall looking at a diagnostics table in a motherboard manual telling me what the beeps meant when I screwed something up..
If it can play HD video (and it already can) then what else do I want performance for?
By the same logic 40 years ago people could have been told about the internet and said what do they want that for? They already had all they needed.
I am interested in your idea of a 'micro-processor', and would like to subscribe to your newsletter.
Coerce, threaten with bodily harm, you know, I'm up for whatever makes him debug my code for me. The little bastard will have to work if he wants to be a part of this family!
I'm planning on teaching my kid to solder just after CPU + Heatsink installation, and before C. So somewhere around 4 years old. My kid's going to pwn me when he's 9. My own personal debugger.
Spoken like a man that has no kids.The reality is for the first 2 years unless you're lucky and has a kid that sleeps you'll be too tired and sleep deprived to do much of anything.
Actually I do have a kid who's about to turn 2, and I was lucky, he slept through the night from month 3 on. :) Moreover, I was kidding ya wank. I learned to program when I was 8 however if dos batch scripts count, and whatever language hypercard and hyperstudio ran on when I was 8 or 9, and at 11 C and spent a ton of time rooting around in makefiles thinking I was "fixing" them when really I had borked my distro and had to hack the makefiles to get the builds to work.
Children can do a hell of a lot more than we give them credit for if you just let them. Too often people are assumed to have limited abilities due to their age. As someone who has for 11 years been a professional programmer, and only just now not the youngest person in the company I work for (I think? Might be wrong), I can truly say people truly project their own limits onto those around them WAYYYY too much.
The only advantage for ARM is the lower power requirement, so if Intel can make their chips less power hungry, they can take over some of the market.
Thankyou for finally speaking the truth. I recognize that ARM is good for mobile phones because of it's cycles/watts, but either I am seriously missing something or people are nutters for not thinking that a modern chip architected to run something as bulky as windows and it's countless applications of bloat will easily smear ARMs face in the mud when it comes to performance.
The only real question now is, does intel stand a bloody chance at lowering the power cost of their architecture? If they can do it, I am on board immediately. I do realize they and AMD have both failed to show any ability to get down to the power efficiency of ARM in the past, I'm still rooting for the chip powering my HTPC to run at a power efficiency to run my phone.
I'm planning on teaching my kid to solder just after CPU + Heatsink installation, and before C. So somewhere around 4 years old. My kid's going to pwn me when he's 9. My own personal debugger.
You're right, because the $1M/year salary isn't enough to take care of the CEO when they take a risk, make a mistake, and get fired, they have to count on that measley sum to pay the bills, so they better not take risks!
Couldn't agree more, was my first too as will it be my son's. However I must say, reading through these comments and recognizing yours I can't help but wonder if our affinity for the KnR as a starter might be a symptom of something else: I am a *completely* hands on learner. I failed high school and college because of this, but succeed in my software career to great effect. I think the density and conciseness of the KnR worked so well for me possibly in relation to this fact, and not as well for many, as true hands on learners really aren't the norm.
There are two reasons the KnR is THE programming bible the way I figure it
The functionality it explains about how to instruct a computer, in a way that makes it clear what the computer is *actually* doing without going to ASM, transcends languages. In a very short read you can come away understanding: strings are actually character arrays, which are actually just bytes with a particular set of values, and you have to allocate memory for things real time and release it or else memory leaks. Find any modern day programmer who hasn't read the KnR and ask them to lay a string out in memory on a white board and they would probably stare at you blankly. I can't count the times I've heard people talking about memory leaks but not able to explain how it actually happens.
Also, it's writing is so direct and to the point, concise, a complete exercise in Strunk 'n White style writing, that makes these concepts easy for anyone. It was my first when I was 11, as will it be my son's first.
3rd, this was the best next step after the KnR when I was a teenager. Though anyone saying the KnR isn't good for a beginner is a nutjob, the strunk 'n white style writing- direct and to the point, gives a foundation for all programming in so clear and concise a manner, you'd be nuts to call it difficult.
Who cares, so long as they can keep us alive long enough, in 80 years they'll have mastered devegetation!
Here here. Engineering is hard, but if you can work out the mental gymnastics required to model complex things mentally and recognize the design flaws while balancing competing interests- You will have work for life. It's true that at a certain age, the quality of the work available to you will decline, and you will probably never become mega rich short of pulling off a gates or zuckerberg. But unless you're especially needy or wasteful you will always have a solid middle class life style available to you. Smart people become Engineers for stability, and a few really smart people do it because they can't help designing complex things.
However the truth of the matter is as I prefaced this, it is hard, and school is not. Thus a degree rarely equals a competence, and as such it is my experience that these days people are great at web browsing, but somewhat short on understanding what makes a web browser.
If he wants to stay in academia, great, if he wants to get into the software industry, he better take that math VERY seriously to work in the algorithm portions of software: compression or crypto, and sometimes data mining. If his math isn't up to snuff to really wrestle with those things, it will be unlikely his software skills will be at the ready for serious industry work without more significant post-grad industry experience vs that of a CS major. Though from interviews I've done, pure CS doesn't mean you know much more than syntax these days.. but maybe that depends on the particular school you go to.
I guess one thing I would say as well is, anyone who can wrap their head around pointers and recursion and make the step past those concepts, then they are among the rare few who truly belong doing software work and should go CS all the way.