Compartilhar via


I'm out of ideas

Well in case you haven't noticed, I've run out of ideas for thigns to write about.  This is you're queue to send me questions or suggestions.

My best guess as to why I've run out of ideas is because of my recent change in jobs.  I am no longer dealing with C# day in and day out (where I am at least minorly an expert), and I'm now living and breathing code-generation for AMD64.  I get to deal with things like GC holes where the JIT isn't properly emitting GC information so the runtime can't properly do a GC.  Needless to say, I am not and expert at this yet, and so nothing to write about.

My old PocketPC recently died (the screen's digitizer went out).  Yes I could probably $100-$200 to have it fixed, but it's an old Casio E-200 still running 2002, and so I'm using this as an excuse get something new.  Accordinng to Dell's order tracking page, my new X30 is in transit to the UPS guy!

Maybe when I get that, I'll find more time to work on PocketPC stuff.  Thanks to the OpenNETCF.org I actually feel like programming on my PocketPC with C# is viable!  Of course in case you're wierd enough to actually want to write code on your PocketPC, there are a hndful of tools out there.  Most notably, Vitaly Pronkinhas already ported the DotGNU C# compiler and GCC to the PocketPC!  Vitaly is either really smart or has a lot more free time than me.

--Grant

Comments

  • Anonymous
    June 10, 2004
    It's hard to talk about the features you're new to. I noticed that when I moved from debugger to C# IDE -- I suddenly had nothing to say to customers.

    You could talk about each discovery you make as you learn.
  • Anonymous
    June 10, 2004
    Instead of writing "you're queue" you should write "your cue". It's disheartening to see that Microsoft can't hire more literate people. You should read more books dude. Sheesh.
  • Anonymous
    June 10, 2004
    Although I toook techinical writing in college, I don't claim to have remembered any of it. Like most skills, if not excercised, they wither and die. Such has become of my English.
  • Anonymous
    June 10, 2004
    There's nothing wrong with writing about things you're not an expert in. In fact, it could lead to an even more valuable information exchange. Maybe someone out here would be able to answer some of your questions? If not, I still think it would be valuable to get your input on the technology throughout your learning process.

    I mean, Microsoft people have to learn, too, right? :)
  • Anonymous
    June 10, 2004
    Write what you're learning. Share the excitement (and frustrations) of your discoveries. You can have a conversation (which is what a blog is, really) with people who know more about the subject than yourself, or people who are on the path of knowledge with you.
  • Anonymous
    June 11, 2004
    Has the GC changed much for VS 2005/.NET 2.0? A lot seem to have been written about all the new framework classes in .NET 2.0, generics etc, but not a lot has been said about the GC, performance improvements etc.
  • Anonymous
    June 13, 2004
    You can write about GC (a lot), pinning sounds pretty good. Write barriers also good.