I am a firm believer than 80% of programmers should not be programmers. Why is it so difficult? Programming is hard. It's even harder when you're stupid.
You make it sound like every development is the same. As if you are somehow handed over the spec, and just need to implement it.
I've never been handed a spec, it's always been my job to figure it out. The other part of my job is the predict what will be needed by understanding the problem domain. There's a reason I get put on all of the big projects and why people tend to come to me first before asking others. I'm also that guy who makes changes in prod because it's pretty much a requirement. I'm the only one who fixes problems in minutes instead of hours or days.
The Empire State Building was the first commercial construction project to employ the technique of fast-track construction, a commonplace approach today but very new in the early 20th Century. This technique consists of starting the construction process before the designs are fully completed in order to reduce delays and inflation costs. In this case, it was imperative to use the fast-track construction method to win the race for the tallest building. In order to make this work, the structural engineer makes a schematic design based upon the architect's sketches. The schematic design includes the materials to be used in construction (either reinforced concrete or steel), types of floors and column spacing.
About 80% of the design is known at the time they started building. The designed and built a framework upon which the remaining 20% should work just fine.
When I read about Agile from well respected people, they explicitly stated that Agile does not replace design. 80/20 rule, you need about 80% of your design ready to go before you start doing Agile. Agile will help with those remaining 20% of cases that are hard to pin down until you get more feedback. The problem is when people skip design and jump strait into dev and assume a sky scrapper can be built with no real planning.
but why is everyone so sure information cannot be "destroyed" (rendered inaccessible) in a black hole?
It was my understanding that all events need to be reversible. If information falling into a blackhole disappears or is otherwise not accessible anymore, then the act of falling into a blackhole is non-reversible. The reason everything needs to be reversible is because time is just a dimension. You can go forward or backwards, but if information is lost, then you can no longer go backwards. This has a lot of ramifications.
Budgeted military spending is a small subset of the entire military spending. If the military needs more money, they just have more printed or someone changes a number on an account.
There a/. article from the DoE that said Green energy requires a different sort of infrastructure, but it does not cost more than regular power. Adding N units of power costs about the same either way.
In the past year, someone on/. had a link to SystemD's own bug tracker where there was a bug someone submitted which was about SystemD corrupting the log during unexpected shutdowns. It wasn't just that you couldn't write to the log, but the entire log was lost. When one of the main devs closed the bug, he added a very sarcastic reason rhetorically asking the submitter how SystemD should be able to read a corrupted log and to delete the log and move on, working as intended.
All I heard was a big whoooosh, as the dev didn't seem to recognize that a volatile log is a horrible thing to have when trying to figure out what happened moments before your computer crashes. A log that can no longer be written to is one thing, but a log that self-destructs because of a race-condition is another.
It's entirely possible that this is no longer an issue for one reason or another, but the fact that one of the core Devs who is responsible for how the system as a whole works, seemed to not even recognize the seriousness of the issue, then proceeded to treat the submitter like some sort of imbecile, made me lose all confidence in their ability to write such a system. I may have caught him on a bad day, but the core dev sounded like a complete moron. He is the kind of person that if you willingly work with him, you are stupid by association.
would be easy to replicate and should be reported as a major bug
The devs don't care. These issues have been reported. Like the binary log corruption bug. After over 1 year of sitting, the bug got closed with a "working as intended" and dev border-lining lambasting the submitter. I can understand that a file can get corrupted because of faulty hardware or an FS bug, whatever. What I don't understand is how someone designs something as critical as a log to be non-atomic and easily get corrupted from an unexpected shutdown because it's designed that way.
As someone who designs systems that must be maintained, logging is vital to any amount of debugging why a system failed. SystemD fails with the most fundamental issues.
Most of the people complaining about SystemD are not complaining about how well it works most of the time, but how horrible it works when things go bad. Why did my system crash? Not sure, SystemD corrupted itself. All I hear is "It works great" or "something went wrong, can't figure it out".
The problems SystemD are trying to solve are real and FreeBSD is looking into the issue and my FreeBSD people agree with this. What the founder won't say, but other people will is that SystemD is a horrible implementation. Both Linux and WinME tried to solve the same issues, but Linux did a hella better job.
I do accept that an actual blackhole that sucks in information and doesn't let it leave probably does not exist, but the generation notation of a crazy dense object that mostly redshifts the heck out of light and can grow to be really large, does exist. When you see a 100M solar mass object orbiting a 18bil solar mass objects at 1/3rd the speed of light, but themselves emit nearly no light, most people would describe that as a "blackhole".
I could see this being useful for my desktop. I think all of my games are signed, I would need to check. But if it became common practice, this could be useful. I could create a whitelist.
Don't conflate morals and scientifically measurable results. We outlaw murder because it harms society. I'm not saying that all drugs should be outlawed, but there are situations where that may be the best option. What's good for society is not always what's good for the individual and what's good for the individual is not always good for society. There is a happy medium. In the end, society is an organism and perfectly has the right to reject your decisions. If you don't like it, you can leave, but if you want to change society, at least have science to back it up.
Caffine can give you a heart attack, but at least you can feel your heart speeding up to dangerous levels. Not so much with Adderall. Long term use of Adderall can result in permanent negative changes to the brain. These changes can build up over time and you get little warning when you should stop. The side effects of Adderall have a much increased risk. That's not including that someone who dies from a caffine overdose is cheaper to take care of than someone with mental issues from Adderall.
I was taking the smallest dose of generic Adderall, and after a few years, I suddenly got some of the side-effects. I didn't need it for everyday living, just certain classes that I found hard to concentrate in. Even then, Adderall made it worse because a simple distraction could leave me 100% focused on something non-class related. At least with my normal ADD, I could be distracted from my distraction, not so much when taking Adderall.
Adderall was horrible for my ability to problem solve. I find that strong concentration negatively affects my ability to solve unique complex problems, but it does help for simple issues that have a simple and definite answer.
ADD can be accurately diagnosed with a brain scan, but those are expensive. Most people just trust the doctor instead of forking out for an MRI. Even a normal MRI may not work, you need to do a lot of mental testing during the scan, making it more expensive than the already expensive scan.
IQ is the median of a group. Obviously they're doing inter-group IQ comparisons, not intra. An IQ of 150 in one group can be the IQ of 100 in another group.
Slashdot Mirror
I am a firm believer than 80% of programmers should not be programmers. Why is it so difficult? Programming is hard. It's even harder when you're stupid.
This is the answer to why Agile is so hard.
You make it sound like every development is the same. As if you are somehow handed over the spec, and just need to implement it.
I've never been handed a spec, it's always been my job to figure it out. The other part of my job is the predict what will be needed by understanding the problem domain. There's a reason I get put on all of the big projects and why people tend to come to me first before asking others. I'm also that guy who makes changes in prod because it's pretty much a requirement. I'm the only one who fixes problems in minutes instead of hours or days.
The Empire State Building was the first commercial construction project to employ the technique of fast-track construction, a commonplace approach today but very new in the early 20th Century. This technique consists of starting the construction process before the designs are fully completed in order to reduce delays and inflation costs. In this case, it was imperative to use the fast-track construction method to win the race for the tallest building. In order to make this work, the structural engineer makes a schematic design based upon the architect's sketches. The schematic design includes the materials to be used in construction (either reinforced concrete or steel), types of floors and column spacing.
About 80% of the design is known at the time they started building. The designed and built a framework upon which the remaining 20% should work just fine.
When I read about Agile from well respected people, they explicitly stated that Agile does not replace design. 80/20 rule, you need about 80% of your design ready to go before you start doing Agile. Agile will help with those remaining 20% of cases that are hard to pin down until you get more feedback. The problem is when people skip design and jump strait into dev and assume a sky scrapper can be built with no real planning.
but why is everyone so sure information cannot be "destroyed" (rendered inaccessible) in a black hole?
It was my understanding that all events need to be reversible. If information falling into a blackhole disappears or is otherwise not accessible anymore, then the act of falling into a blackhole is non-reversible. The reason everything needs to be reversible is because time is just a dimension. You can go forward or backwards, but if information is lost, then you can no longer go backwards. This has a lot of ramifications.
Dark energy is an observable effect.
Budgeted military spending is a small subset of the entire military spending. If the military needs more money, they just have more printed or someone changes a number on an account.
Paper work is about 50% of the entire cost of health care in the USA. Too many types of insurances and time wasted fighting them.
There a /. article from the DoE that said Green energy requires a different sort of infrastructure, but it does not cost more than regular power. Adding N units of power costs about the same either way.
In the past year, someone on /. had a link to SystemD's own bug tracker where there was a bug someone submitted which was about SystemD corrupting the log during unexpected shutdowns. It wasn't just that you couldn't write to the log, but the entire log was lost. When one of the main devs closed the bug, he added a very sarcastic reason rhetorically asking the submitter how SystemD should be able to read a corrupted log and to delete the log and move on, working as intended.
All I heard was a big whoooosh, as the dev didn't seem to recognize that a volatile log is a horrible thing to have when trying to figure out what happened moments before your computer crashes. A log that can no longer be written to is one thing, but a log that self-destructs because of a race-condition is another.
It's entirely possible that this is no longer an issue for one reason or another, but the fact that one of the core Devs who is responsible for how the system as a whole works, seemed to not even recognize the seriousness of the issue, then proceeded to treat the submitter like some sort of imbecile, made me lose all confidence in their ability to write such a system. I may have caught him on a bad day, but the core dev sounded like a complete moron. He is the kind of person that if you willingly work with him, you are stupid by association.
There is a difference in the end result, but the mindset is the same.
would be easy to replicate and should be reported as a major bug
The devs don't care. These issues have been reported. Like the binary log corruption bug. After over 1 year of sitting, the bug got closed with a "working as intended" and dev border-lining lambasting the submitter. I can understand that a file can get corrupted because of faulty hardware or an FS bug, whatever. What I don't understand is how someone designs something as critical as a log to be non-atomic and easily get corrupted from an unexpected shutdown because it's designed that way.
As someone who designs systems that must be maintained, logging is vital to any amount of debugging why a system failed. SystemD fails with the most fundamental issues.
Most of the people complaining about SystemD are not complaining about how well it works most of the time, but how horrible it works when things go bad. Why did my system crash? Not sure, SystemD corrupted itself. All I hear is "It works great" or "something went wrong, can't figure it out".
The problems SystemD are trying to solve are real and FreeBSD is looking into the issue and my FreeBSD people agree with this. What the founder won't say, but other people will is that SystemD is a horrible implementation. Both Linux and WinME tried to solve the same issues, but Linux did a hella better job.
It's not the US' fault, it's a fault in the Earth. http://en.wikipedia.org/wiki/F...
I do accept that an actual blackhole that sucks in information and doesn't let it leave probably does not exist, but the generation notation of a crazy dense object that mostly redshifts the heck out of light and can grow to be really large, does exist. When you see a 100M solar mass object orbiting a 18bil solar mass objects at 1/3rd the speed of light, but themselves emit nearly no light, most people would describe that as a "blackhole".
My Dr told me if "normal" people took Adderall, they typically felt energetic, while ADD people have a calming effect.
I could see this being useful for my desktop. I think all of my games are signed, I would need to check. But if it became common practice, this could be useful. I could create a whitelist.
Don't conflate morals and scientifically measurable results. We outlaw murder because it harms society. I'm not saying that all drugs should be outlawed, but there are situations where that may be the best option. What's good for society is not always what's good for the individual and what's good for the individual is not always good for society. There is a happy medium. In the end, society is an organism and perfectly has the right to reject your decisions. If you don't like it, you can leave, but if you want to change society, at least have science to back it up.
Caffine can give you a heart attack, but at least you can feel your heart speeding up to dangerous levels. Not so much with Adderall. Long term use of Adderall can result in permanent negative changes to the brain. These changes can build up over time and you get little warning when you should stop. The side effects of Adderall have a much increased risk. That's not including that someone who dies from a caffine overdose is cheaper to take care of than someone with mental issues from Adderall.
It's ever man's dream to have a large blood clot in their penis.
I was taking the smallest dose of generic Adderall, and after a few years, I suddenly got some of the side-effects. I didn't need it for everyday living, just certain classes that I found hard to concentrate in. Even then, Adderall made it worse because a simple distraction could leave me 100% focused on something non-class related. At least with my normal ADD, I could be distracted from my distraction, not so much when taking Adderall.
Adderall was horrible for my ability to problem solve. I find that strong concentration negatively affects my ability to solve unique complex problems, but it does help for simple issues that have a simple and definite answer.
ADD can be accurately diagnosed with a brain scan, but those are expensive. Most people just trust the doctor instead of forking out for an MRI. Even a normal MRI may not work, you need to do a lot of mental testing during the scan, making it more expensive than the already expensive scan.
IQ is the median of a group. Obviously they're doing inter-group IQ comparisons, not intra. An IQ of 150 in one group can be the IQ of 100 in another group.
Whatever their's is, your's must be lower. Obviously they were comparing our 150 to the hypothetical 100 of a more intelligent society.