Search This Blog

Sunday, November 13, 2011

Crosspile Week 1

I have been researching tools to convert C# into javascript for awhile. I just think it would make work more fun if I could use the refactoring tools built into Visual Studio to clean up my javascript code. I also like the idea of getting compiler errors for simple typos.

So I decided to spend some of my spare time creating a tool that will allow me to do this. This is what I got done in Week 1
  1. Sent email to my boss and got approval to do this. 
  2. Bought a new macbook since mine was super old.
  3. Setup my laptop to run MonoDevelop.
  4. Created test project googleReaderShares2Blogger to see if I want to use MonoDevelop or Visual Studio
  5. Created Git repository and uploaded my test project code.
  6. Used Boot Camp to setup Windows 7 on my mac and installed Visual Studio
  7. Downloaded sharpkit and started a test project to see if I can use this tool.
  8. Came up with the snazzy name Crosspile for my project.
  9. Cleaned up blog a little.
  10. Read through Git tutorial.
I plan to update this blog every week with my progress.  If I get any questions, I will add more detail about what I am doing.

Monday, October 31, 2011

Nikhil Kothari's Weblog : Getting Started with Script#

link -> Nikhil Kothari's Weblog : Getting Started with Script#
Hello World with Script# - a 101-style walkthrough on authoring and deploying scripts compiled from c#, while using the HTML DOM APIs, XMLHttpRequest, and jQuery.
I downloaded and watched the Mix11 presentation. He showed launching tests server side that ran in the browser. That was pretty cool.

Tuesday, October 25, 2011

I Broke Your Code, And It's Your Fault

link -> I Broke Your Code, And It's Your Fault
Early in my career, I was afraid of making changes that could affect unexpected aspects of the system. My first job out of college, whenever I made changes, I'd read lots of code and was extra careful. Of course, nobody can ever be careful enough with this methodology, so I'd wind up breaking things. I'd feel awful for this, completely embarrassed. I'd panic and try to fix the code as quickly as possible, assuming my co-workers thought I was an idiot.
Today, I take the exact opposite approach: fearless refactoring. I refactor code without even the slightest bit of concern about the ramifications. If I break something, a test will let me know. If no test lets me know when I broke something, I don't feel embarrassed. I feel like someone else should be embarrassed.
Scary idea but maybe it makes sense

Wednesday, October 19, 2011

How To Produce Bug-Free Software

link -> How To Produce Bug-Free Software

Many are resigned to the fact that all software is destined to contain some “bugs”, but did you know it’s possible (and arguably pretty easy) to always produce “bug-free” software?

I think this was a long way of saying you need to write tests

Friday, September 30, 2011

Friday, September 16, 2011

ExtJS code in CSharp

link -> ExtJS code in CSharp
Wouldn't it be cool to program in this instead of javascript. Think of the intellisense and compile time support. Might be faster to convert to 4.0 if we converted all our code to C# first.