delorean

delorean - Delorean lets you travel in time with Ruby by mocking Time.now

This was posted 1 day ago. It has 0 notes.
ruby on rails - Find (and kill) process locking port 3000 on Mac - Stack Overflow
This was posted 2 days ago. It has 0 notes.
MySQL Daily Automatic Backup Script

http://www.systeminplace.net/forums/index.php?topic=13.0;wap2

This was posted 2 days ago. It has 0 notes.
I wish Reddit looked like this. No ranks. No votes. No ads. No bloatware.

I wish Reddit looked like this. No ranks. No votes. No ads. No bloatware.

This was posted 3 days ago. It has 2 notes. .
Induction

Induction - A Polyglot Database Client for Mac OS X

This was posted 1 week ago. It has 0 notes.
Say Goodbye to Embarrassment

http://www.aaronsw.com/weblog/emotions

This was posted 1 week ago. It has 0 notes.

I hate TDD, but I do it anyway.

I hate TDD.

  1. TDD is slow. It takes longer time to ship features. This is obvious as you have to code for the features as well as the tests.
  2. TDD is wasted effort. During the early turbulant stage of an application development when business requirements change like a 16 year old’s hairstyle, 90% of tests you write will become useless later. They are usually not salvageable either as features change or dropped completely.
  3. TDD is full of haxx and spaghetti. I try to keep test code to look nice and maintainable. That might work well at the beginning. Sooner or later, you’ll be left with bloated ugly code. Add other collaborators in the mix, test code looks likes shitstorm. You’ll soon have 3 different sign out helper methods and 4 sign in helper methods that do the same thing and 5 different sign up helper methods with only 1 working.

I still do TDD.

  1. TDD keeps core functionalities to run. When you are about to deploy your code, at least you know that areas you tested works the way it should.
  2. TDD ensures that you haven’t broken X, Y, Z while you worked A. As your app becomes more complex with many pieces of code working together, your code changes in one area might break some other code. This happens more often as the codebase grows. TDD lessens unexpected breakage from happening from code changes.
  3. TDD is having todo list without having a todo list. And while writing a todo list, you are actually writing an automated test at the same time. It’s so much win.
This was posted 1 week ago. It has 3 notes.

Why did Panasonic discontinue Technics SL1200 mk2?

This was posted 1 week ago. It has 0 notes.
This kind of shit people try to pull off on developers amaze me.

http://programmers.stackexchange.com/questions/110487/my-customer-wants-me-to-record-a-video-of-how-i-develop-his-software-product

This was posted 2 weeks ago. It has 0 notes.

A new way to spell debugger dubbeger

This was posted 2 weeks ago. It has 0 notes.