I used a lot of visualized search engine technologies being pitched by different research groups or startups in my last job. They were all pretty (well, okay, they were 50 footers) but they all had the same problem: horribly inefficient as search engines. Which is, you know, what they were supposed to be.
Maybe we should take the "states as laboratories for democracy" concept to an extreme. Designate some state--I offer you my home state of West Virginia--and isolate it from the current system. Then try the craziest stuff we can think of and see what works. People are pretty risk-averse when it comes to things this big, so if we lower the ante (WV is pretty low, love it though I do) maybe the other 49 states will agree to go along ;-)
One idea I heard on C-SPAN this morning was to chop them up and take the bailout money to instead build something like 12 hardcore engineering outfits to build cars of the future, then get startup people to pitch for an opportunity to run those outfits and/or commercialize them down the road.
I don't have any capacity for analyzing the pros and cons to this, but the idea of focusing on starting from innovation rather than trying to steer a big, unwieldy ship towards innovation sounds attractive.
Your summary didn't match with what I read in the NYTimes article. The point seemed to be that people have advantages in certain endeavors that are not attributable to their skill or talent. Bill Gates is a offered as a case of someone who had the advantage of privileged access to and time on computing systems (which is not a knock on his genius). Another case cited has to do with age cutoffs for Canadian youth hockey leagues. Basically, anyone born right before the cutoff tends to be the older, bigger, stronger kid in that bracket and this advantage increases over time. They practice, yes, but they also have a significant advantage stemming from a factor totally outside of their influence. The other point being that you can analyze these factors and reduce that influence, supposing you wanted to do that.
I think your assessment of what the book offers is actually more of an assessment of what Giles zeroed in on. I'm not defending the book--I have no interested since the concept can be summed up in a twitter post--but thought I'd point out that I think there's a different thesis at work.
When I started getting in to coding and started focusing on refactoring, it amused me how close that was to the process of writing poetry (at least the way I was taught). Write it all out. Then cut some, add less, cut some more, move some things around.
I just had a funny daydream of me installing the Vista upgrade on to an XP laptop, getting it all set up and finally to the desktop, then panicking and hitting Ctrl+Z frantically and repeatedly.
I do as well on my Vista work laptop. I sometimes have to do IE or FF specific things, and I use FF at home on Ubuntu, but for Windows I just use Chrome. I don't need a lot of plugins at work, the omni-tab page substitutes well for bookmarks and the browser is way faster, which is important since Vista is so chipper.
I didn't think it was FUD, but the article did confuse me so maybe it was just poorly written (or I suck). Here's what I read:
Title: Warming of blackouts if wind, sun added to grid [note: I think this was supposed to be "warning"]
Opener: Adding electricity from the wind and the sun could increase the frequency of blackouts and reduce the reliability of the nation's electrical grid, an industry report says.
Body: The North American Electric Reliability Corp. says in a report scheduled for release today that unless appropriate measures are taken to improve transmission of electricity, rules reducing carbon dioxide emissions by utilities could impair the reliability of the power grid.
They went from warning about alternatives to discussing issues with emission reduction rules. Those two weren't connected in the article, so maybe I'm just not up on SF legislation. Am I to understand that the emission reduction rules mandate the use of some solar and wind and that the result of that could impair reliability because of the swings you mentioned (not mentioned in the article)? Help :-)
Every generation thinks the next generation is lazy, shiftless, immoral and will destroy the world. It's been happening for a while. The worrying, not the destroying.
Yeah, I sort of feel like this is safest at a relatively simple scale where the efficiency gains also stand to be the smallest. Although I heart Ruby, personally, I'd be more interested to see someone nail the deep javascript stack with quality. Something like Rhino on Rails on the server, javascript/AJAX client/server, CouchDB w/ javascript views for the DB and AIR for javascript/AJAX desktop apps and widgets. Seems like with JSON around, that could be elegant and efficient at larger scales, rather than generating code from one language to another for some pieces.
Considering that both candidates were on twitter and both made updates, but Obama just made way more, do you think that was entirely a function of money?
I don't know anyone who thought they were getting actual candidate tweets, but people buy extended warranties too. Especially after they get a crayola oblongata.
I remember my wife describing the morning of the 4th when she brought up Facebook and her feed was this giant mass of get-out-the-vote status updates from people who donated their status to Obama. I also remember getting far more tweets from Obama than McCain, and the follower counts were very lopsided. Clearly, the campaigns had different approaches in the wired and I think it at least helped enthusiasm amongst my generation.
I have worked on a Ruby MUD. I think this is probably a good suggestion, along with bk's suggestion to get the hang of balancing and populating a game first. Thanks.
My wife's a portable furnace and I'm cold-blooded. Incidentally, she also grabs the comforter at night, hooks it under her torso and rolls up in a burrito. I have purchased a second comforter.
Amen on #2. Since brevity isn't just aesthetics, this has always been a problem for me. The last thing I built in C# was the last thing I built in C# because it became hard/annoying to maintain and debug, even with VS.
Anyone have similar advice for an ultra-nerd like me who has always wanted to make RPGs and only RPGs (the games, not the weapon)? I have always assumed the skill set would be a little different.
My first thought is that encouraging people to make their own highly inexpensive plastic objects and to spread the ability to their neighbors could lead to a significant increase in disposable plastic usage. In general, plastic doesn't really go away. Anyone know if the plastic used here is recyclable, biodegradable or otherwise mitigates the long term (granted, I mean, really long term) concern of flooding landfills?
I appear to be on the list of people for whom the upgrade will remove 3d acceleration. I'm going to have to wait. Does anyone know if this is purely an issue with kernel and drivers that should get resolved soon or if this is a strategic change in supporting the vendor drivers (Nvidia in my case)?
I have a lifetime bid for a fraternity (I didn't join, probably won't) as a result of a legitimate receptionist test. I was hanging out waiting for a friend and some senior member started cursing at his laptop. He had apparently lost an essay and I was able to rescue the contents, safely transfer it to disk, help him back it up just in case and give him advice on avoiding the problem in the future. Won me some points.
The author is suggesting that some getters and setters--particularly the ones that introduce a public method to replace a property against a private variable without introducing any actual value-added logic or protection--are counter-productive.
I've been pondering the following things recently in relation to the glue code in Java issue:
1) IDEs often require Beans be created, which require getters and setters. So, if you have to use IDEs, you are pushed towards getters and setters in many cases to create Bean-compatible classes.
2) Rather than stuffing all this in the code and creating explicit glue, would it be possible to implement an interface which adds getters and setters for Bean compatibility at runtime if explicit ones have not been created (ostensibly because there is no value to add in the method body that provides additional logic or security)?
I need to get back in to this and see if its possible or even makes sense. I've been out of Java since 2000.
I've always thought that ASP.NET was an attempt to get MFC programmers building web applications while avoiding re-training them on how to build web applications.
I just sent a mail to Tumblr support yesterday asking if there was a way to do this without having to export all my Blogger content and write a custom loader script against the API. Of course, they said they don't have such a tool.
The professor might also be an overbearing tool bag or the class might not be particularly worth the effort (I've had a few of these). Anecdotal evidence like this is junk.
My dad showed me his report card from Kindergarten once. He barely passed because "Eddie has trouble whistling and skipping in a straight line." When he got in to Dylan, it was all over for his potential as a productive and intelligent human.
Of course, he's a published author and editor of poetry, novels and non-fiction, humor columnist, wilderness advocate, sometimes environmental lobbyist, motivational speaker and researcher/writer/editor for the beautifully designed black-bordered brochures you get at our national parks.
And still loves Dylan (Bob and Thomas). And he's my hero. And he figured out how to whistle and skip in line somewhere along the way.
Agreed. Some people just aren't as effective at abstract symbol manipulation. I've found that people who can pick up programming languages can pick up other human languages and vice versa.
This doesn't mean that they can't learn programming. It means that they would be much better off focusing on their strengths instead. There's a difference between "can't do it" and "fails course" as you rightly suggest.
This was how most of my professors taught debugging, actually. Print statements. Reading the code is great but after a while it really does become hard to see where things go awry--especially in your own code. I think teaching students the basic concepts of debugging, break points, stepping, etc. will 1) clearly illustrate how bad print statement approaches are and 2) become annoying enough that it will make them better planners and code readers.