1) Write a small program to start understanding the syntax. Use code you find on the web for reference.
2) Become familiar with the following projects, and understand how they are implemented:
a) mbUnit, a fantastic example of modern, idiomatic c# design.
b) DynamicProxy, which pushes (abuses?) the CLR's reflection APIs past what you might think they are capable of.
3) Get a copy of.NET reflector, which you'll need to overcome the lack of documentation for key useful pieces of the framework. This thing is magical.
Process Explorer, Filemon, Autoruns. Some other windows debugging tools too, since I do development on that platform. But those three are generally useful.
It seems to me that the entire point of the wiki is to do away controlled vocabularies. http://shirky.com/writings/ontology_overrated.html is a good read about these kind of things - he doesn't talk about wikis in particular, but the same things apply.
Come now, beaverton isn't that bad. Parts of it are pretty uppity, but it's mostly just your average 'burb. Don't know about hillsboro, but you're spot on about lake oswego.
UML is a language, not so different from C or Java. It's good at representing some things, like structure relationships and certian kinds of high-level sequencing. It's not so good at others, like complicated data stuctures or calculations. It would be silly to write a memory manager in UML.
I use a bastardized form of UML on the whiteboard when I need it. It's not in any way official, just enough to get the point across. I occasionally will put that on the computer using visio, but again without much regard for form. I'm not one to think in UML itself, so all of the modeling tools that are designed around it tend to slow me down more than anything.
I'm perfectly happy with my way of doing it, but maybe I just haven't seen the light. Could be that a few weeks of Rational "training" would reverese my opinions entirely.;-)
This is perhaps a tangential answer, but I do much better by going through the code with a debugger and watching things happen. Especially with some of the more compilacated OO stuff, and when the comments are unhelpful or wrong, it can be much more useful than reading the code.
app load times in kde has historically been a big problem. It's due to the way the library loader works with c++ apps. The current solution is "kdeinit", which is kind of a hack, but the right way to do it is to have improved control over what exactly is exported from a library, which gcc 3.4 gives.
It doesn't have to be so hard... I had a thinkpad where you could remove the hard drive be removing just one screw, one that could be turned with a quarter actually. And my current compaq has a reasonable way to access the drive too, iirc.
How'd you work the BS->couple years->MS sequence? I've considered doing the same thing, but I'm worried that I'm too far gone from undergrad and won't be able to get the requisite academic reference letters. (that and I was rather quiet at the time)
Slashdot Mirror
I'm assuming you're doing this on windows.
.NET reflector, which you'll need to overcome the lack of documentation for key useful pieces of the framework. This thing is magical.
1) Write a small program to start understanding the syntax. Use code you find on the web for reference.
2) Become familiar with the following projects, and understand how they are implemented:
a) mbUnit, a fantastic example of modern, idiomatic c# design.
b) DynamicProxy, which pushes (abuses?) the CLR's reflection APIs past what you might think they are capable of.
3) Get a copy of
4) Write something larger.
Anyone who's used perforce will understand. I read this and it made me very, very jealous.
Process Explorer, Filemon, Autoruns. Some other windows debugging tools too, since I do development on that platform. But those three are generally useful.
You know, that's what I thought at first, until I googled it and learned it was a bass boost. Now I don't know what to think...
Loudness is a slight bass boost so things'll sound better at low volumes.
It seems to me that the entire point of the wiki is to do away controlled vocabularies. http://shirky.com/writings/ontology_overrated.html is a good read about these kind of things - he doesn't talk about wikis in particular, but the same things apply.
Gravity is a harsh mistress.
I prefer Rotini, lots of recursive functions...
But then how would you get out a bomb?
Come now, beaverton isn't that bad. Parts of it are pretty uppity, but it's mostly just your average 'burb. Don't know about hillsboro, but you're spot on about lake oswego.
UML is a language, not so different from C or Java. It's good at representing some things, like structure relationships and certian kinds of high-level sequencing. It's not so good at others, like complicated data stuctures or calculations. It would be silly to write a memory manager in UML.
;-)
I use a bastardized form of UML on the whiteboard when I need it. It's not in any way official, just enough to get the point across. I occasionally will put that on the computer using visio, but again without much regard for form. I'm not one to think in UML itself, so all of the modeling tools that are designed around it tend to slow me down more than anything.
I'm perfectly happy with my way of doing it, but maybe I just haven't seen the light. Could be that a few weeks of Rational "training" would reverese my opinions entirely.
This is perhaps a tangential answer, but I do much better by going through the code with a debugger and watching things happen. Especially with some of the more compilacated OO stuff, and when the comments are unhelpful or wrong, it can be much more useful than reading the code.
University, huh?
actually...
app load times in kde has historically been a big problem. It's due to the way the library loader works with c++ apps. The current solution is "kdeinit", which is kind of a hack, but the right way to do it is to have improved control over what exactly is exported from a library, which gcc 3.4 gives.
Play on KGS. It's way better than yahoo software wise, and the people are friendlier typically.
Why, exactly, should I take the word of a guy who works for Rational? The people who want to SELL me the tools to do these things?
Newer TVs will have HDMI inputs, which AFAIK is essentially DVI-D + some PCM stream. (S/PIDIF?) No conversion should be necessary.
Things have gotten somewhat better now that they've trained the chimpanzee that writes their filter drivers. Somewhat.
Now I will cry.
*sob*
Does an obscure interface as a copy-protection mecahnism? Because I'd say it was just circumvented.
Liberate America!
Cowa-fucking-bunga, dude! ;-)
"Come see the bias inherent in the system!"
*ahem*
It doesn't have to be so hard... I had a thinkpad where you could remove the hard drive be removing just one screw, one that could be turned with a quarter actually. And my current compaq has a reasonable way to access the drive too, iirc.
How'd you work the BS->couple years->MS sequence? I've considered doing the same thing, but I'm worried that I'm too far gone from undergrad and won't be able to get the requisite academic reference letters. (that and I was rather quiet at the time)