Slashdot stories can be listened to in audio form via an RSS feed, as read by our own robotic overlord.


Forgot your password?

Comment: I don't know what I don't know. (Score 1) 396

by Dragnl0rd (#31201812) Attached to: What Knowledge Gaps Do Self-Taught Programmers Generally Have?
Being self taught, one of the major revelations I had was that the more I tried to teach myself, the more I realized I knew just a FRACTION of what it took to become a good developer. In the beginning when I thought I understood what i was doing, writing oop programs, when in fact I was writing procedural code with objects scattered around it. Regular Expressions were (to me) among the arcane arts known by masters, engines were something to be licensed from those same masters, and I didn't even hear the words "design pattern" until I'd been trying to work professionally for over a year. Many of the things I know today, I wouldn't have even known to ask/research/learn about back then, because I couldn't conceive of its existence. Heck, I'll probably be saying that forever! To quote a friend of mine: "I cannot grasp the depth of my own ignorance." However, while doing the 'self taught' thing, I have seen other threads like this recommending the staple books like the Petzold book for windows programming, the O'Reilly series, the Stroustrup book for C++, and the "Head First Design Patterns" book. However since i still have google up when doing the vast majority of my coding, I've actually found that more and more I've been bookmarking blogs by developers more experienced and skilled than myself. Moreso than most books, the blogs I keep bookmarked tend to have prefaces at the beginning of each article explaining exactly what programming obstacle the blogger had encountered, thus providing a concrete application for the code to follow in that article.

Astronomers Discover 33 Pairs of Waltzing Black Holes 101

Posted by ScuttleMonkey
from the teach-them-to-foxtrot dept.
Astronomers from UC Berkeley have identified 33 pairs of waltzing black holes, closing the gap somewhat between the observed population of super-massive black hole pairs and what had been predicted by theory. "Astronomical observations have shown that 1) nearly every galaxy has a central super-massive black hole (with a mass of a million to a billion times the mass of the Sun), and 2) galaxies commonly collide and merge to form new, more massive galaxies. As a consequence of these two observations, a merger between two galaxies should bring two super-massive black holes to the new, more massive galaxy formed from the merger. The two black holes gradually in-spiral toward the center of this galaxy, engaging in a gravitational tug-of-war with the surrounding stars. The result is a black hole dance, choreographed by Newton himself. Such a dance is expected to occur in our own Milky Way Galaxy in about 3 billion years, when it collides with the Andromeda Galaxy."

Comment: Put the kill burden on developers? (Score 1) 374

by Dragnl0rd (#29043903) Attached to: MS — Dropping IE6 Support "Not an Option"
Lately I've been toying with the theory that IE6 is still alive because of circular logic. Specifically, that MS doesn't want to try and kill IE6 because people keep using it, and people keep using it because it hasn't been killed yet (and are too lazy/computer illiterate to switch to IE7, IE8, Firefox, Opera, Chrome, Konqueror, etc etc etc). Under that theory, the burden of killing that damned browser then falls to developers (such as the people behind to say 'No more IE6, we're tired of having to code IE6 compatibility hacks in.' If enough developers took that particular leap, then the userbase's adoption of better (or at least more recently developed) browsers would be accellerated to the point where Microsoft could look at the market's usage statistics and finally say 'okay, we're letting IE6 die.'

C for yourself.