Lazycoder

22Aug/102

Twitter Updates for 2010-08-22

Powered by Twitter Tools

Filed under: General 2 Comments
21Aug/101

Twitter Updates for 2010-08-21

Powered by Twitter Tools

Filed under: General 1 Comment
20Aug/100

Twitter Updates for 2010-08-20

  • Microsoft to Co-Chair New W3C Web Performance Working Group http://bit.ly/dgOfXX #
  • Seriously, do people actually conduct financial transactions on E*Trade? The website sucks and doesn't work 1/2 the time. #
  • In unrelated news, I hate everything. #
  • .@SaraJChipps JavaScript – The Good Parts by Douglas Crockford #BasicsTrumpsFrameworks #
  • .@bmsullivan Right, but if you don't understand scope and events you might wright your handlers incorrectly and cause more problems. #
  • #herdingCode Herding Code 91: Listener-Powered Lightning Round: This week on Herding Code, K Scott, Jon, Kevin, an… http://bit.ly/bU1jd7 #
  • http://bit.ly/bU1jd7 where we finally tackle the burning question "Cake or pie?" #
  • Did I just see a JavaFX article on DrDobbs? Seriously? Is JavaFX still around? Has anything other than examples been written using it? #
  • For those wondering, yes Dr Dobbs is still around. At least online. http://bit.ly/9MH0Nf #
  • I'm not registering for PDC10, but I will register for PDC10 afterparties. ;) #
  • “@dorianmuthig: Lala :) ” got me on my knees #
  • Cool, husband of one of my HS classmates is the President of SendThisFile.com http://j.mp/dxPYDH #fb #
  • .@robconery Not so fast Conery! You don't speak for me! in reply to robconery #
  • [posted] Twitter Updates for 2010-08-19 http://bit.ly/dbUgku #
  • 5 assumptions MongoDB makes that users often miss. http://j.mp/9gGqBG #
  • I have 4687 fake followers. Wait, that can't be right. #

Powered by Twitter Tools

Filed under: General No Comments
19Aug/100

Twitter Updates for 2010-08-19

  • Ruby 1.9.2 is released http://bit.ly/aLHlEW #
  • Free F# stand alone IDE (VS Shell) http://bit.ly/9zPBp5 #
  • Interesting, If you install enough extensions in Chrome, you lose the default menus? Can't get to the "home" menu anymore. #
  • .@jongalloway @OdeToCode he also loads jQuery twice for some reason. (fo' reals) #
  • I am the terror that flaps in the night. I am the 8 am conference call that starts late… #fb #
  • One thing I'd like is to be able to hook my iPhone up to a monitor for gaming/movies and use the iPhone as the controller. #
  • That might require a beefier chip though and drain the battery faster. #
  • I've noticed that multiple monitors aren't necessary if I can use Expose on osx or with the taskbar peaks in windows7 #
  • /s/peaks/peeks sheesh #
  • I don't get it? Why roll out a @lightswitch beta to MSDN subscribers? They aren't the target audience. #

Powered by Twitter Tools

Filed under: General No Comments
30Jun/1012

The hardest part of software development has nothing to do with code

People who complain about how much “more” code they have to write in an MVC project versus a Webforms project, or really any project, prove to me that they have absolutely no idea where the REAL work is in ANY development project.

The main work in any software development project is FIGURING OUT WHAT TO BUILD. How you build it is trivial compared to the amount of time and effort you SHOULD put into discovering the users needs and working with them to solve their problems and make their life better.

Remember, that’s the number one purpose for any piece of computer hardware or software. This cannot be stressed and repeated enough.

COMPUTERS SHOULD MAKE OUR LIVES BETTER!

How do we write programs that make lives better? By writing programs that fulfill their needs and ease the pain of their work. We still aren’t at a point where we have a common, easy to understand vocabulary when it comes to build software. We often get it wrong the first, second, and third times. That’s where the discipline and engineering comes into play.

18Mar/1016

Getting started with node.js on Windows

The title is somewhat misleading. As of right now, node.js doesn’t run on Windows. You have to run it on some kind of *nix/BSD based system. But there is a somewhat low footprint way to run it and play around with it on your Windows box.

 

Step 1 – Download and install VirtualBox orVMWare Player. I chose VirtualBox. It’s free, and supports 64-bit guests.

Step 2 – Download The Turnkey Linux core appliance and unzip it somewhere. This handy little virtual machine is based on Ubuntu and give you a basic command line environment with networking.

Step 3 – Import the Turnkey core appliance into VirtualBox.

turnkey_step_1

turnkey_step_2

Choose the .ovf file in the Turnkey directory you unzipped earlier.

turnkey_step_4

Click next and review the settings, making any changes as you see fit. The defaults should work fine. Then click import.

turnkey_step_3

Once Virtualbox finishes importing the virtual machine, you can start it up.

Assuming your network is configured correctly, the virtual machine will grab an IP from your DHCP server and be ready to go.

turnkey_startup

Step 4 – At this point you can either SSH into the virtual machine or you can connect using the web shell at the address indicated in the startup screen. Initially you can connect using as the root account with no password. You are almost ready to start installing node.js. First type “apt-get update” at the command line to make sure you have all the latest package information.

Step 5 – Install the developer tools you need to get and build node.js. Node.js isn’t packaged as a binary, you have to build it from source. Luckily it includes it’s dependencies and is pretty easy to build. But first we need to get a compiler. Type “apt-get install build-essential” and hit return. A lot of text will fly past, if it asks you if you want to go ahead press “y”.

Step 6 – Install Git. Now you’ve got a compiler installed, we have to install git so we can fetch node.js from the repository. At the command prompt type “apt-get install git”. Once that is complete, type “apt-get install git-core”.

Step 7 – Clone the node.js Git repository. If you want to put node.js is a specific directory, go ahead and make it then “cd” into the new directory. At the command prompt, type “git clone git://github.com/ry/node.git“.

Step 8 – configure the source for building. type “cd node” and change into the node directory that Git created. Type “./configure”. You may see a few “fail” messages. Don’t worry about them.

Step 9 – Build node.js. Type" “make” at the command prompt. Get a sandwich or a nice cool drink. It doesn’t take very long, but it’s not very exciting unless the Matrix screensaver is your favorite screen saver.

Step 10 – Install node.js and start build applications. Type “make install” once the build is complete. Once that is complete,you can type “node” at the command prompt and you should see the standard help information fly by.

 

Building a node module or application is beyond the scope of this short tutorial. I suggest reading up at the Node.js site.