My Life

Development strategy for google-app-engine

2010-02-27T19:36:00.000-08:00

In developing my site for the cloud I found it a bit of a challenge. There is very little documentation in terms of infrastructure strategy and a lot of sites assume you have a clear methodology. I always strive for a clean infrastructure — having developed code for the quite awhile I have come to know that if you have a solid scalable strategy up front it makes things just work easier later on. That is why I was really turned onto google-app-engine. It gives you a clear way of building and testing your code and then pushing it to the web. It is a great place to start but it isn’t the “everything” I’m looking for.
Because some of the limitations/restrictions with using google-app-engine (GAE) you need to understand that if you want to use it (i.e. python package) you need to include it in your application. That is where the benefits of a virtualenv come into play. virtualenv (when combined with pip) let you know exactly what packages you have because throughout the application development process if you need it you ‘pip-it’. Then pip gives you a clean manifest on what you have so you always know. But.. (you knew this was coming) GAE doesn’t like a virtual env. In fact if you try it you almost surely run into problems. For me it was a error along this line...


ImportError: No module named unittest

So what can I do? For me the reasons to use a virtualenv/pip combination is too compelling to simply not use it. I really like knowing what packages I willbe deploying up to the cloud and since I need to package them with my application why not? Furthermore if you are used to running in a virtualenv/pip environment or you have a somewhat stock python environment this is just a good way to keep things straight. Understanding the obvious limitation that you can’t run in a virtualenv we are going to take advantage of everything else this environment has to offer.

General Development Strategy

Use Django. While I understand that GAE now support 1.1 I want that control left to me.
Keep the development tree streamlined for the entire site. Guido recommends (as I understand him in this video ~11:45) to use a single app-engine application per independent application. This doesn’t make much sense to me as the ability to share information between different models is really extending the multi-dimensionality of the site. So my preference is to keep it all under one hood.
Use revision control (for me it’s perforce - I don’t have anything against the others (hg/git/svn) it’s just what I like)
Use eclipse/pydev as my development environment

General Directory Structure

I am developing for $SITE ( i.e export SITE=“foobar.com”)

/dev
        /<$SITE>
                /bin
                /lib
                /include
                /src
                        /django
                /www
                        app.yaml
                        /appengine_django
                        manage.py
                        main.py
                        /apps
                                /app_1
                                /app_2
                                /app_3
                                /app_n
                        /settings
                                __init__.py
                        urls.py
                        django symlink to ../src/django/django

Getting started

Setup your virtualenv


 cd dev

Build up a baseline virtualenv


 virtualenv --python=python2.5 --no-site-packages ${SITE}

Install some needed apps.. (make sure you are in your dev directory..)


# pip install -E ${SITE} -e svn+http://code.djangoproject.com/svn/django/trunk#egg=Django
# pip install -E ${SITE} -e svn+http://code.djangoproject.com/svn/django/tags/releases/1.1.1/#egg=Django
 pip install -E ${SITE} -e svn+http://code.djangoproject.com/svn/django/tags/releases/1.1/#egg=Django
 pip install -E ${SITE} yolk

*Notes: 1.1.1 failed 2 tests and trunk failed more.. 1.1 passes all tests

Activate your virtualenv


 source ${SITE}/bin/activate

Create your www tree (this is where we house our app). Use the google-app-engine-django helper stuff. It’s well worth it!!


 cd ${SITE}
 svn export http://google-app-engine-django.googlecode.com/svn/trunk/ www

Link in your django tree


 cd www
 ln -s ../src/django/django

At this point you should be able to deactivate yourself and simply verify everything works.


 deactivate
 python2.5 manage.py test
  #Ran 61 tests in 8.058s
 python2.5 manage.py runserver

Now open up a web browser to http://127.0.0.1:8000/ and you should get the famous “It works!!”. At this point you should also configure the Google App Engine Launcher to point to your site directory and “www” will be your application.

Build up a quick index and push it to the web.

This is not for the faint. I am going to quickly build up a basic django index page. I want to show it works and we con complete the process.

Shuffle around my tree (personal preference)

Like I indicated above I like to have my apps all under a single apps tree (keep it clean). I also like to put settings.py under a settings tree - this allows me to mess with the __init__.py

So with that hang on..


 cd ${SITE}/www
 mkdir settings
 mv settings.py settings/__init__.py
 rm settings.pyc

 mkdir apps
 python2.5 manage.py startapp core
 mv core apps/

Build your simple app

Edit your ${SITE}/www/urls.py


 urlpatterns = patterns('',
      url(r'^', include('apps.core.urls')), 
 )

Add in your app to the ${SITE}/settings/__init__.py


 INSTALLED_APPS = (
       'appengine_django',
       'apps.core',
 )

Create your apps/core/views.py


 from django.http import HttpResponse 
 def index(request):
    return HttpResponse('Hello World -- Django rocks!!')

Get your apps/core/urls.py ready to accept the index view


 from django.conf.urls.defaults import *
 import views
 urlpatterns = patterns('',
    url(r'^$', views.index),
 )

Verify it works.. Voila - pretty simple eh??

Next up publish it..

References:

Guido's screencast - it was awesome..
Rapid Development with Python, Django, and Google App Engine (2008 Google I/O Session Videos and Slides)

Building Python on 2.6.4 Snow Leopard

2010-01-04T11:05:00.000-08:00

Goal:
        •        Fully functioning Python with MySQL, Ldap, P4Python, installed
        •        Use pip

Limitations:
        •        None so far — P4Python was not x86_64/i386 compatible but that now is fixed..

Notes:
        •        Stock python on Snow Leopard ships as a 32-bit only application (file /System/Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5)

Building readline-6.0

Normally you won’t have to set these variables up but since we want a 32 bit with a 64 bit readline we need to ensure these are set up..


         export MACOSX_DEPLOYMENT_TARGET=10.6
         export CFLAGS=“-arch i386 -arch x86_64”
         export LDFLAGS=“-Wall -arch i386 -arch x86_64”
         ./configure
         make
         sudo make install

Building Python 2.6.4

If you use a custom ~/.pydistuti“s move it out of the way! This will build an intel only version of Python.


         ./configure --enable-framework MACOSX_DEPLOYMENT_TARGET=10.6 --with-universal-archs=intel --enable-universalsdk=/
         make
         sudo make install

After the make you should see errors like this..


        Failed to find the necessary bits to build these modules:
        _bsddb             dl                 gdbm            
        imageop            linuxaudiodev      ossaudiodev     
        spwd               sunaudiodev                        
        To find the necessary bits, look in setup.py in detect_modules() for the module’s name.

MySQL (Not Python)

Get the latest MySQL 64-bit (of course). Pull the file from MySQL.com
Get the Snow Leopard Preference Panel for 64-bit from here

Getting rolling with pip.

If y’u use a custom ~/.pydistutils put it back..

Get setuptools (0.6c11) from pypi.


        python2.6 setup.py build
        python2.6 setup.py test
        python2.6 setup.py install

Get pip from pypi


        python2.6 setup.py build
        python2.6 setup.py install

Start getting your apps..


        pip install --install-option=“--prefix=/Users/sklass/perforce/dev/tools/python/Mac”  nose

Now build up MySQLdb


        python2.6 setup.py build
        python2.6 setup.py test
        python2.6 setup.py install

Setting up MacJournal for Code Blocks

2010-01-02T05:07:00.000-08:00

So I wanted to get some good syntax highlighting..

        1.        Install SyntaxHighlighter on Blog
        2.        Configure SyntaxHighlighter in MacJournal Blog by turning off Escape < and &gt under the edit server list!
        3.        Create a http://www.smileonmymac.com/TextExpander/ snippet (pyp) to wrap plain text in <pre class=“brush: python” >)
        4.        Test it out

This is a basic python code block


        urldata = urllib.urlopen(settings.PEOPLE_NOTES_BASE_URL).read()
        nsoup = BeautifulSoup(urldata)
        total = 0
        links = nsoup.fetch(‘a’, {‘href’:re.compile(‘\/hr\/.*OpenDocument’)})
        for element in links:
            if maxNum and total >= maxNum: break
            queue.put({u”name”: u”%s” % element.find(text = True),
                       u’url’: “https://intranet.mycompany.com%s” % element[‘href’]})
            total += 1

        for index in range(50):
            if maxNum and index >= maxNum: break
            thrd = self.ParseUserPage(out_queue, final)
            thrd.setDaemon(True)
            thrd.start()
        #wait on the queue until everything has been processed
        queue.join()
        out_queue.join()

And the important thing is grace..

Continuing this should be fine..

Saturday, January 02, 2010 6:13 AM

Thoughts on pip - whats the big deal?

2010-01-01T04:47:00.000-08:00

I have been a python user since python 2.0. Since then I’ve stayed fairly current with the python and the newer methodologies (currently running 2.6.4). I am always striving to make myself a more proficient developer seeking out more efficient ways of doing things and not afraid to give them a try.
I currently am responsible for a cross platform python environment for our engineering teams (>150 ppl) which has spanned various unix’s, macs and the occasional windows machine. I’ve been doing this for the past several years and have managed python transitions from 2.2 - 2.6 with relative ease.
The methodology we employ to maintain this has been around since I started using python and I would expect will remain so in the future. We extend the default python path using a pth file methodology. The pth file is coupled to an environment variable which gives developers the ability to shift an environment variable and quickly be testing their code in their respective sandbox. This coupled with Perforce gives us a nice branched virtualenv without using virtualenv. We use this methodology for both external modules ( django/beautifulSoup/paramiko etc) and internally developed modules. Currently our single pth file looks like this.

import os, site; tech = os.environ.get("TECHROOT", "/"); tech = tech if os.path.isdir(os.path.join(tech, "tools/python/Mac/lib/python2.6/site-packages")) else "/"; site.addsitedir(os.path.join(tech, "tools/python/Mac/lib/python2.6/site-packages"))
import os, site; tech = os.environ.get("TECHROOT", ""); tech = tech if os.path.isdir(os.path.join(tech, "tools/python/modules")) else "/";site.addsitedir(os.path.join(tech, "tools/python/modules"))

Admittedly this may be a bit overkill. However limitations on pth files (paths must be on a single line) force the need. FWIW all this file does is get the environment variable TECHROOT if defined or establish a default path. The first line is used for external modules and the second line is for internally developed modules. Module installation is a then breeze when using a ~/.pydistutils.cfg file which looks like this.

[install]
install_lib = $TECHROOT/tools/python/Mac/lib/python$py_version_short/site-packages
install_scripts = $TECHROOT/tools/python/Mac/bin

Again this is all tied to our revision control system (perforce) which allows any developer to easily add external modules or build modules for other to use. By shifting around the environment variable we can thoroughly test our code prior to release. Simple enough.

Over the past couple years I have really come to enjoy easy_install. It certainly worked for everything I needed. It has some limitations which I didn’t like but for the most part it worked. Some of the notable limitations I usually do are as follows.

Dependency Tracking must be thought out and tested ahead of time.
easy_install should be named easy_install<ver> (easy_install2.6)
Any bin files should have its header nailed down (/usr/bin/env python2.6) or be named file<ver> (django-admin2.5.py)
Un-Installing is a manual process - but simple cause it’s a single file and tweak of on file.

Barring the above limitations, I like easy_install. I like the packaging of egg archives; it’s a simple 1 file. True this forced me to be very conscience of the platforms and make sure that everyone was on the same page with respect to upgrades but that’s simple planning. Not every package builds with easy_install but then again neither does pip.

So I decided that I would use my shift to Snow Leopard and 2.6.4 as the basepoint for using pip. After reading comments like this I figured surely I must be missing something. After playing with pip now for a week I can honestly say - Nope I don’t think so.

To be fair pip is still at release 0.61. It appears pip is really geared towards those which use a virtualenv environment. As detailed above we don’t need virtualenv we effectively have an automated one with perforce, and an environment variable. That being said I found several things I didn’t like with pip and other things which are broken altogether.

Dependency Tracking still must be thought out and tested ahead of time.
Un-Installing packages doesn’t always work
Pip Doesn’t understand the test constructs if provided.
Pip Doesn’t always respect ~/pydistutils.cfg install_scripts directive. Most of the time I just needed to pip install --install-option="--prefix=$TECHROOT/tools/python/Mac”

So what’s the big deal? Is it me or am I missing something larger. I thought pip would track dependancies allowing you to have say two versions of a module installed simultaneously. But no. It’s a nice and clean installer (I’ll give you that). The freeze is pretty slick if you are distributing your own system without a real SCM system in place. Overall I’m not overly impressed and I feel pip is overrated or easy_install misleadingly accused. Maybe it’s me?

Eclipse

2009-12-13T19:29:00.000-08:00

So I am playing with pydev and so far I think it’s pretty cool. Here is a sample with a picture..

This is the second post. So far it’s pretty amazing. I love the new stuff in 1.5!!

And then I edited it some more.. Pictures..

2009-12-13T19:17:00.000-08:00

This is just a sample test from MacJournal.

I was sitting here wondering what to do then I thought “Hey why not code”

OK here goes

from Tkinter import *

root = Tk()
w = Label(root, text="Hello, world!")
w.pack()
root.mainloop()

So what about daily templates..

Surpise! Nortel files for bankruptcy

2009-01-14T07:08:00.001-08:00

Coming from the not-so-surpised category.. I don't care for companies that use proprietary systems witch antiquated methodologies. Unfortunately at both my current and my former company we use(d) Nortel hardware. It doesn't play well with everything - and frankly sucks. Am I sad this one's going south - NOPE!

Nortel to file for bankruptcy protection — Facing $107-million interest on debts, former telecom giant will likely be broken up and sold to foreign rivals — Former technology titan Nortel Networks Corp. is expected to file for bankruptcy protection as early as today, sources say …
[From Nortel to file for bankruptcy protection (Globe and Mail)]

Aperture Workflow for Scanned Pics

2008-12-30T11:05:00.001-08:00

This will go over my workflow for Scanned Images.

This is my aperture workflow for scanned pics.

First things first - we need to get the images scanned in. Fortunately the folks over at Scancafe.com figured this out pretty easily. I simply packaged up my photos and negatives and shipped them off. Now a couple words of wisdom on this - as I have several thousand that I have now started working through. First - Organization is the key. Using baggies bag and tag the relevant “projects” - Make sure you Identify both the negatives and the pics. In general negatives definitely come out better. I opted for both - often times the negatives come out better but sometimes the pic is all you have. Once I have them in digital form then I do the following:

1.) Get the negatives and pictures back in sync. This is a huge time consuming process but pays off because then the timeline can be preserved. I named the pic xyz_.jpg and the negative xyz_s.jpg. The tool a A Better Finder Rename comes in real handy here.

2.) Figure out when / where the pic was taken. This is another very time consuming piece.

3.) Using A Better Finder Attributes - “Change the date the original photo was taken” to the correct date.

4.) Import into Aperture into a new project.

5.) If you are bringing both the negatives and the photos in use stacks to stack them. Bring the negative to the first one in line..

6.) Grade them. I use this as my reference thanks Mark Jaquith

-1 Unusable
★ Keep
★★ Show
★★★ Share
★★★★ Boast
★★★★★ Flaunt

7.) Keyword them. Make sure you identify the scans (35mm/35mm negative)

8.) Geotag them using mapture .

9.) Push them to picassa using Aperture to Picassa plugin.

10.) Push them to smugmug for archiving using ApertureToSmugMug.

That's it!! Simple eh...

Python 2.6 final released

2008-10-02T07:33:00.000-07:00

Whoot!

Python 2.6 final is now available.

12 Unit Testing Tips for Software Engineers

2008-08-15T16:10:00.001-07:00

Unit Testing is one of the pillars of Agile Software Development. First introduced by Kent Beck, unit testing has found its way into the hearts and systems of many organizations. Unit tests help engineers reduce the number of bugs, hours spent on debugging, and contribute to healthier, more stable software.

In this post we look at a dozen unit testing tips that software engineers can apply, regardless of their programming language or environment.

1. Unit Test to Manage Your Risk

A newbie might ask Why should I write tests? Indeed, aren't tests boring stuff that software engineers want to outsource to those QA guys? That's a mentality that no longer has a place in modern software engineering. The goal of software teams is to produce software of the highest quality. Consumers and business users were rightly intolerant of buggy software of the 80s and 90s. But with the abundance of libraries, web services and integrated development environments that support refactoring and unit testing, there's now no excuse for software with bugs.

The idea behind unit testing is to create a set of tests for each software component. Unit tests facilitate continuous software testing; unlike manual tests, it's cheap to perform them repeatedly.

As your system expands, so does the body of unit tests. Each test is an insurance that the system works. Having a bug in the code means carrying a risk. Utilising a set of unit tests, engineers can dramatically reduce number of bugs and the risk with untested code.

2. Write a Test Case Per Major Component

When you start unit testing, always ask What Tests Should I Write?

The initial impulse is to write a bunch of functional tests; i.e., tests that probe different functions of the system. This is not correct. The right thing is to create a test case (a set of tests) for each major component.

The focus of the test is one component at a time. Within each component, look for an interface - a set of publicly exposed behaviour that component offers. You then should write at least one test per public method.

3. Create Abstract Test Case and Test Utilities

As with any code, there will be common things all your tests need to do. Start with finding a unit testing for your language. For example, in Java, engineers use JUnit - a simple yet powerful framework for writing tests in Java. The framework comes with TestCase class, the base class for all tests. Add convenient methods and utilities applicable to your environment. This way, all your tests cases can share this common infrastructure.

4. Write Smart Tests

Testing is time-consuming, so ensure your tests are effective. Good tests probe the core behaviour of each component, but do it with the least code possible. For example, there is very little reason in writing tests for Java Bean setter and getter methods, for these will be tested anyway.

Instead, write a test that focuses on the behaviour of the system. You don't need to be comprehensive; create the tests that come to mind now, then be ready to come back to add more.

5. Set up Clean Environment for Each Test

Software engineers are always concerned with efficiency, so when they hear that each test needs to be set up separately they worry about performance. Yet setting up each test correctly and from scratch is important. The last thing you want is for the test to fail because it used some old piece of data from another test. Ensure each test is set up properly and don't worry about efficiency.

In cases when you have a common environment for all tests - which doesn't change as tests run - you can add a static set up block to your base test class.

6. Use Mock Objects To Test Effectively

Setting up tests is not that simple; and at first glance sometimes seems impossible. For example, if using Amazon Web Services in your code, how can you simulate it in the test without impacting the real system?

There are a couple of ways. You can create fake data and use that in tests. In the system that has users, a special set of accounts can be utilised exclusively for testing.

Running tests against a production system is risky: what if something goes wrong and you delete actual user data? An alternative is fake data, called stubs or mock objects.

A mock object implements a particular interface, but returns predetermined results. For example, you can create a mock object for Amazon S3 which always reads files from your local disk. Mock objects are helpful when testing complex systems with lots of components. In Java, several frameworks help create mock objects, most notably JMock.

7. Refactor Tests When You Refactor the Code

Testing only pays if you really invest in it. Not only do you need to write tests, you also need to ensure they're up to date. When adding a new method to a component, you need to add one or more corresponding tests. Just like you should clean out unused code, also remove tests that are no longer applicable.

Unit tests are particularly helpful when doing large refactorings. Refactoring focuses on continuous sculpting of the code to help it stay correct. After you move code around and fix the tests, rerunning all the related tests ensures you didn't break anything while changing the system.

8. Write Tests Before Fixing a Bug

Unit tests are effective weapons in the fight against bugs. When you uncover a problem in your code, write a test that exposes this problem before fixing the code. This way, if the problem reappears, it will be caught with the test.

It is important to do this since you can't always write comprehensive tests right away. When you add a test for a bug, you're filling in the gap in your original tests in a disciplined way.

9. Use Unit Tests to Ensure Performance

In addition to guarding correctness of the code, unit tests can help ensure the performance of your code doesn't degrade over time. In many systems slowness creeps in as the system grows.

To write performance tests, you need to implement start and stop functions in your base test class. When appropriate you can use a time-particular method or code and assert that the elapsed time is within the limits of the desired performance.

10. Create Tests for Concurrent Code

Concurrent code is notoriously tricky and typically a source of many bugs. This is why it's important to unit test concurrent code. The way to do this is by using a system of sleeps and locks. You can write in sleep calls in your tests if you need to wait for a particular system state. While this is not a 100% correct solution, in many cases it's sufficient. To simulate concurrency in a more sophisticated scenario, you need to pass locks around to the objects you're testing. In doing so, you will be able to simulate concurrent system, but sequentially.

11. Run Tests Continuously

The whole point of tests is to run them a lot. Particularly in larger teams where dozens of developers are working on a common code base, continuous unit testing is important. You can set up tests to run every few hours or you can run them on each check-in of the code or just once a day (typically overnight). Decide which method is the most appropriate for your project and make the tests run automatically and continuously.

12. Have Fun Testing!

Probably the most important tip is to have fun. When I first encountered unit testing, I was sceptical and thought it was just extra work. But I gave it a chance, because smart people who I trusted told me that it's very useful.

Unit testing puts your brain into a state which is very different from coding state. It is challenging to think about what is a simple and correct set of tests for this given component.

Once you start writing tests, you'd wonder how you ever got by without them. To make tests even more fun, you can incorporate pair programming. Whether you get together with fellow engineers to write tests or write tests for each other's code, fun is guaranteed. At the end of the day, you will be comfortable knowing your system really works because your tests pass.

And now please join the conversation! Share unit testing lessons from your projects with all of us.

[From 12 Unit Testing Tips for Software Engineers]

Analog Rails - Thoughts from a Cad Manager

2008-07-21T08:03:00.001-07:00

Last week myself and a senior member of my staff were invited to a hands-on look of Analog Rails. Analog Rails is company whose focus is to "create the best analog and RF environment for the IC circuit designer". The system is built upon Open Access and gives an analog design engineer the complete ability to do both schematic capture, simulation and layout. It nicely automates the more tedious aspects of analog layout while giving the design engineer the complete flexibilty. For example the process of both matching (common-centroid anyone) and wire-widening (based on via size) is done in very automated push button method.

In the last several months Analog Rails have really stepped up the development by starting to integrate with outside tools. For example they now integrated in Veritools into the design framework. This is a big step because it implies that they designed a flexible subsystem which is critical - there is no single solution in IC Design. I would like to see spectre ( -turbo of course ) and calibre integrated but it's not there yet.

Throughout the discussion / demo I began to understand the impact of this. Of course it's built on OA and will nicely integrate with Cadence and many many others, but something more interesting is afoot. This tool represents a clear methodology shift.. ..The demise of the block level analog layout engineer. Why? First as I said earlier, the layout automation piece is very intuitive and friendly. Plus the smaller technology geometries that analog design is pushing into (<90nm) is forcing simulation earlier (using Cadence) to account for device parasitics (LOD). So the analog engineer is already doing a fair amount of the placement and letting the layout guy clean up the work. But this tool is correct by construction and so the layout is clean from the get-go. So involving a layout person to "clean it up" isn't necessary. There will still need to be layout for macro / chip level integration but block level layout could (will) be going the way of hand-LVS.

There are areas which need to be better defined. From a cad managers perspective - I look at flexibility and integration. The flexibility to align the tool to corporate goals and strategy, and the hooks necessary to integrate it into my existing flow, and (perhaps) migration to this tool.

The flexibility of the tool is fundamentally there but needs better definition. For example: If the company has it's own fab, and the strategy is to use its own fab, how will this tool which claims to not need a PDK get the design constraints from my foundry into their system? The converse is also true - I am a fabless company with a strategy to tape-out to the lowest cost foundry - how do I ensure that the constraints from Dongbu will work with my design. The point is while Analog Rails clearly has the framework so support this, they need to have a clear methodology for how to implement design constraints which the customer may use or opt to use the defaults from Analog Rails.

[UPDATE]: I did receive a bunch of documentation on the methodology for creating these techfiles. It is pretty straight forward and not as difficult as I had imagined.

From the integration side it was better defined but still lacks the clarity for migration. Because the tool can work on OA it should "just work". But how does this system work when an existing layout done in Virtuoso or Laker which doesn't or isn't correct by construction adapt itself? We spoke of the "dummy mode" but I think a bit more clarity on this would be helpful. I not sure this is show stopper - because it would depend on the use model. If you define your flow/methodology such that this is the sole block level tool for a project it could work. If you want to do a mix - well that would have to be tested.

Overall I was very impressed. The tool has certainly matured over the last year. It's flexible sub-system and the ability to tie into other tools gives me reason to want to look further at the tool. It will be a real test to see this tool integrate with the work horses of the IC Design tools, and how easy it is to define a methodology around the tool. Again this tool has some really cool technology under the hood and should make for a fun evaluation. My concern (as any cad manager has) is that our designers are going to eat this up and really want it. That's a good problem to have.

iPhone Platform: What We Can Learn From Tap Tap Revenge

2008-07-19T05:43:00.001-07:00

In reading this - it makes you consider what happens when having a marketing group becomes less important.... Get your fanatical customers to market your product for you and reward them by giving it to them for free.

...

But I think there is something even more important to notice about Tap Tap's success. When Seth Godin released his first marketing book, Permission Marketing, he gave away the first four chapters for free via pdf to over 150,000 people. It generated a lot of buzz about the book and was a big factor in the book's success when it eventually became available in hardback. So when he followed up with Unleashing The Ideavirus, he went one step further. He gave away the entire book for free in pdf (it still is available free). Seth says that over 2mm copies were given away. And yet when the book was published in hardback it went to #5 on Amazon. It was a demonstration of the very tactics Seth was evangelizing in the Ideavirus book. Seth asserted that by giving away your product early to your greatest fans who will do more work and put up with a less than optimal experience, you prime the pump for the mass market. That's because your early fans will spread the ideavirus and market the book for you.

Tapulous did the same thing with Tap Tap Revenge. The game was first made available for the iPhone at the start of this year. But the only people who could play it were people with phones that were jailbroken. So it's audience was small, but fanatical. These were the early iPhone app adopters, the ones who would work harder and put up with a less than optimal experience. But now that everyone can play Tap Tap, the early adopters are telling everyone else how great it is.

[From iPhone Platform: What We Can Learn From Tap Tap Revenge]

Verizon CEO grasping at straws .. we will not become just a network pipe!

2008-07-01T07:21:00.001-07:00

Apparently Ivan Seidenberg just doesn't get it. My suggestion: Focus on one thing and do it really well. Apple develops very end-point good hardware/software. Verizon (and all mobile operators) should focus on a stable "all access" network. Having a company which primary focus ought to be "connectivity - anywhere, anytime" (Hey I like that..) focus part on their attention on the actual end-point device is silly.

What's even more bothersome is the comments he makes regarding Steve Jobs.

As handsets become banking tools and games controllers, he argues, mobile operators can up-end other companies' business models. "It's very cool. And Steve Jobs eventually will get old . . . I like our chances."

Yeah good luck with that..

Read the original article here

Progressive MyRate drive-monitoring device goes national - Confession

2008-06-30T07:48:00.001-07:00

Confession.

I speed.

There I've said it. I don't know why I speed, I understand the illogic of speeding in that I'm not saving much time. I understand the consequences of speeding that being tickets and potential road rage from someone who doesn't share my view. Further I get I'm wasting gas. I understand all of that. But I still speed. I can't help it - it's wired into me. But if I'm now going to be monitored... Um no thanks.

All I can say is - Here's $10 for the guy that cracks this.. Good luck and godSPEED ;)

Progressive insurance has been testing out the MyRate driving monitoring system for a few years now (it used to be called TripSense), but it's finally taking the system national, bringing pay-as-you-drive insurance into the mainstream. The little blue box plugs into your car's ODB II diagnostic port (all cars made after 1996 have one), and studiously records your driving habits, wirelessly sending the data back to Progressive HQ (it's not clear exactly how). Every six months, Progressive will crunch the numbers and issue a new rate for you based on how you drive -- savings of up to 40 percent are possible. That's pretty tempting, depending on your current rates and driving habits, but we're not so sure we're willing to share that much data for an unspecified discount -- especially since we're confident the MyRate box will get cracked almost immediately.

Read - MyRate press release

Read - MyRate video

Read - How MyRate works

Thinking Like a Cocoa Programmer

2008-06-30T07:32:00.001-07:00

Reading this should be the mantra of ANY software engineer.

Theocacao: “First and most importantly, the Cocoa programmer’s focus is always the end result for the user, not the academic sophistication of the code.”
[From Thinking Like a Cocoa Programmer]

If you can't beat em - join em!! Dell wants to be like Apple

2008-06-27T06:32:00.001-07:00

You just can't make this stuff up.
Dell is launching a new mid-range line of portable computers called Studio Laptops with a Mac-like “Dock” designed to give Vista users an illusion of the OS X experience.
Studio Laptops’ desktop GUI takes Windows’ traditional application icon layout and organizes it into a “Dock” similar to the one familiar to Mac users, though questions remain as to whether users will be able to customize the Dock layout and place it on either side or at the bottom of the desktop.
In an additional concession to the proposition that Apple may be winning the OS war, Dell will offer cases in seven colors, a significant change to the company’s predominantly industrial look.
[From Dell Brings Dock, Color to New Laptops]

Man's Wii Fit experiment comes to an end, 15 pounds shed

2008-06-24T09:01:00.001-07:00

Go Wii!!

As you may recall, Mickey DeLorenzo rose to some degree of internet stardom a little over a year ago by dropping a whopping nine pounds using Wii Sports as his sole exercise routine and, after packing on a few pounds, he decided to give it another go using Nintendo's latest weight-shedding wonder: Wii Fit. Unlike a certain other would-be success story, DeLorenzo actually managed to complete his experiment, and the results are fairly impressive. After 45 days, he managed to shed a full 15 pounds, or about 2.56 pounds a week, and he dropped his body fat % from 20.8% to 18.4%. Of course, DeLorenzo admits that doing anything involving movment an extra 60 minutes a day will result in some weight loss, but he seems pretty sold on the benefits of Wii Fit, saying that it made it "especially easy" to work the training into his daily life. [From Man's Wii Fit experiment comes to an end, 15 pounds shed]

Making AppleCare Worthwhile: MacBook Pro Battery Replacement

2008-06-24T08:58:00.001-07:00

This is a really interesting article on battery replacement..

Every time I buy a new Mac laptop, I question whether I should purchase AppleCare to extend the warranty from one year to three years. My MacBook Pro cost $2,800 (with tax and shipping) in November 2006, so laying out another $300 for AppleCare - well, frankly, it hurt. (For more on the purchase, and how it stacked up to previous PowerBooks I've owned, see "More Bang, Less Bucks for my MacBook Pro" 2006-11-20.) However, I've found that almost every laptop I've owned has needed some sort of after-warranty work done, so I've ordered AppleCare for every one. [From Making AppleCare Worthwhile: MacBook Pro Battery Replacement]

Semi IP market grew 8% in 2007

2008-06-23T08:45:00.001-07:00

Not exactly a stellar year..

The growth of the worldwide market for semiconductor intellectual property slipped back to a single-digit percentage in 2007, reflecting signs of maturity, less organic growth and more growth by acquisition, according to market research company Gartner.

[From Semi IP market grew 8% in 2007]

Dell pushes back desktop XP cutoff date to June 26

2008-06-22T07:24:00.001-07:00

First glancing at the below story I laughed. I went to post this but that's when the real shocker hit me... Windows XP was released in 2001 - Almost 7 years ago.. That turns the story from not funny but to sad (it's close to pathetic).

Sure, you'll be able to pay out the nose for a Vista machine with a XP Professional "downgrade" soon enough, but Dell just pushed back its cutoff for straight-up XP machines. They'll be selling select Inspiron and XPS desktop with whatever flavor of XP you choose up until June 26th, at precisely 6:59AM EST. Naturally after June 26 you'll be able to buy a Vista Biz or Ultimate machine and downgrade to XP Pro, but we'll hope it doesn't have to come to that. We heard that one guy even got a printer to work with Vista. Things are looking up, folks!

[From Dell pushes back desktop XP cutoff date to June 26]

Cadence bids to buy Mentor Graphics

2008-06-17T07:59:00.001-07:00

Now this is news!! I can't believe it - poor wally!

Cadence Design Systems, Inc. announced it has submitted a proposal to the board of directors of Mentor Graphics Corp. to acquire Mentor Graphics for $16.00 per share in cash. The transaction is valued at $1.6 billion.

[From Cadence bids to buy Mentor Graphics]

Firefox 3 download day - how are you getting involved?

2008-06-17T07:50:00.000-07:00

In case you have been completely under a rock today is the official Firefox 3 release day. The folks over at Mozilla are trying to break a world record for the most number of downloads in a day.

So happy downloading! Of course you can follow this on twitter!

Sign of the Times - Segway Glides as Gasoline Jumps

2008-06-16T08:12:00.001-07:00

This falls under the obvious - but apparently the micro-car business is not the only ones making money in these $4.20/gal times.

Say hello to Segway. Once a techie toy - now seems to have sales jumping 50% this year. And it's no longer simply being used by universities and public offices - small business are also jumping into the mix..

Firefox 3 Launch Tomorrow!

2008-06-16T07:55:00.001-07:00

Firefox 3 Launch Tomorrow (and Party):

"I suspect everybody knows by now that tomorrow is the official launch of Firefox 3.

A couple things to note about tomorrow. Firefox is trying to break a record for the most downloads in a 24 hour period. So if you plan to download FF3, you might as well do it tomorrow and contribute to a record being set."

(Via A VC.)

TomTom for iPhone lives; Jobs' true health; green iPhone 3G?

2008-06-14T07:52:00.001-07:00

TomTom for iPhone lives; Jobs' true health; green iPhone 3G?: "Despite reports to the contrary, TomTom is still working on a GPS app for the iPhone. Meanwhile, Steve Jobs' thin look may be permanent evidence of his cancer cure, Greenpeace is concerned about a toxic iPhone 3G. and a growing number of would-be iP...

(Via AppleInsider.)