I will be sueing all of mankind for emitting dangerous electromagnetic radiation from their heads! Only those with flatline electroencephalograms will escape my litigious wrath!
For stuff of currency (news, specific tech info, mail lists) then it's the web. But for in-depth coverage that requires thought (such as foreign policy analysis, political analysis, layman's overview of current scientific thinking in various subjects, technical subjects on languages, tools, and architectures), it's going to be periodicals or books.
In other words, if requires heavy thought I want it printed. That may reflect that I need to reread and ponder weightier stuff, and that it's harder for a guy over 40 to stare at text on a monitor for lengthy periods of time. It's also harder to bring a monitor into the toilet with you.
My life expectency now is about 80 years, which means I have about 35 to go. But in 2038, medical advances may allow me to live another 20 years past that date. When 2058 rolls around, I may get another 20 year advance, and so on.
So I might make it to 2100. My children should, easily.
Moe says: "If you have 10 brilliant people leading 100 average people... fire the 100 and support the 10 to do the delivery effectively. Make sure they follow a process, and make sure that the requirements are defined and change as little as possible. Make sure designs are verified, make sure code is reviewed."
From my memory, Brooks says poo-poo to this mode of thinking. The fact is that there are NOT enough brilliant people available in market to make this work for everybody.
And from my experience, you're going to have a shot at success with a mix of good/mediocre people who can communicate and function as a team, rather than with a few brilliant prima donna's who can't stand to talk to each other.
Code completion/syntax checking has probably saved me countless compile/debug cycles.
I think the only way to become a better programmer is to suffer through a product's first few life cycles: concept->analysis->design->implementation->mainten ance 1->reengineering->maintanence 2.
After the second maintenance cycle you're just milking the cow, so move on to another start-up project and apply your new-found experience elsewhere.
The point is, until you have to maintain and rewrite you're own mistakes, you don't learn much of anything.
Up until the recent past, unfortunately, a lot of startups have been bottom-heavy with young, inexperienced developers who are willing to put in the long hours necessary to brute-force their mistakes through by whatever bandaids and chewing gum it takes. That's a hit-or-miss proposition.
Alas, it's very hard to get a doomed project cancelled or realigned due to political inertia. When it becomes obvious that management is living in Cloud Cuckooland, it's time for you to pick up sticks and move on.
Slashdot Mirror
All female carp caught in Australia have suddenly developed an unusual countenance that closely resembles a smile of extreme satisfaction.
will be the day they pull the power cable from my hot frying dead hands.
... is the theoretical limit for modem technology.
... it's probably made up of quirks instead of quarks.
and I'm not just talking content here! Screams for a web designer.
Arf! Arf!
I will be sueing all of mankind for emitting dangerous electromagnetic radiation from their heads! Only those with flatline electroencephalograms will escape my litigious wrath!
For stuff of currency (news, specific tech info, mail lists) then it's the web. But for in-depth coverage that requires thought (such as foreign policy analysis, political analysis, layman's overview of current scientific thinking in various subjects, technical subjects on languages, tools, and architectures), it's going to be periodicals or books.
In other words, if requires heavy thought I want it printed. That may reflect that I need to reread and ponder weightier stuff, and that it's harder for a guy over 40 to stare at text on a monitor for lengthy periods of time. It's also harder to bring a monitor into the toilet with you.
A neutron star is a ball of neutrons. A large pile of neutrons may be harder to produce, since the material is so dense it would tend to collapse.
My life expectency now is about 80 years, which means I have about 35 to go. But in 2038, medical advances may allow me to live another 20 years past that date. When 2058 rolls around, I may get another 20 year advance, and so on.
So I might make it to 2100. My children should, easily.
eom
Passing through like the stake in a vampire's heart.
Heck, even Zenith got into the act!
Hell, Philco was making mirror TVs in 1939! Take a gander.
It's a gas laser. Gas is hypersonically ejected out of a chamber, and during expansion the photons are released.
It's the ejection of the gas into the expansion chamber that causes the kick.
Yeah, I guess you're right. Evidently Toland had a shitload of light lying around.
Nope, wasn't small aperature. Both foreground and background were in focus.
Take a look at shots from "The Best Years of Our Lives" (1946)
BTW, Toland died in 1948, so I should have said movies of the 40's, not 50's.
Does anybody remember the deep focus cinematography of Gregg Toland? How were those shots done?
Hey, where did Jon Katz go?
1. Make the ISP responsible.
2. You wouldn't. The ISP would have to.
3. Add token-response protocols to email messages.
Tax foreign e-mail "imports". Those that don't pay, don't get to import.
It doesn't have to be much, just 1/8 cent per email or so. That's all it would take.
Since when was Sputnik a commercial communications satellite?
and another one that's doing poorly.
I know! I'll bind them together at the hip like siamese twins! That will make them both look and function so much better! Ya, that's the ticket!
Stupid marketing dweebs.
Moe says:
"If you have 10 brilliant people leading 100 average people... fire the 100 and support the 10 to do the delivery effectively. Make sure they follow a process, and make sure that the requirements are defined and change as little as possible. Make sure designs are verified, make sure code is reviewed."
From my memory, Brooks says poo-poo to this mode of thinking. The fact is that there are NOT enough brilliant people available in market to make this work for everybody.
And from my experience, you're going to have a shot at success with a mix of good/mediocre people who can communicate and function as a team, rather than with a few brilliant prima donna's who can't stand to talk to each other.
Code completion/syntax checking has probably saved me countless compile/debug cycles.
n ance 1->reengineering->maintanence 2.
I think the only way to become a better programmer is to suffer through a product's first few life cycles: concept->analysis->design->implementation->mainte
After the second maintenance cycle you're just milking the cow, so move on to another start-up project and apply your new-found experience elsewhere.
The point is, until you have to maintain and rewrite you're own mistakes, you don't learn much of anything.
Up until the recent past, unfortunately, a lot of startups have been bottom-heavy with young, inexperienced developers who are willing to put in the long hours necessary to brute-force their mistakes through by whatever bandaids and chewing gum it takes. That's a hit-or-miss proposition.
Alas, it's very hard to get a doomed project cancelled or realigned due to political inertia. When it becomes obvious that management is living in Cloud Cuckooland, it's time for you to pick up sticks and move on.