Start-Up Weekend App


I am a big fan on start-up business and start-up weekend really offers a platform for like-minded people to get together and build a company.

But, start-up weekend event is only hosted every now and then. Why don’t create the app where we can interact with everybody on daily, continuous basis?


  • Real-time, continuous.
  • User profile provide detail information of their area of expertise.
  • Built-in project management tools.
  • Scheduling assistance, for meeting, etc.


It’s basically match-maker for venture capitalists, developers / designers, sales reps and project managers. Every users can create their own project of their idea. Then, developers / designers can pick a project they want to participate based on their area of expertise. Based on the team needs, the project may include additional project mangers, business analyst or marketers. Venture capitalist will then come in and see project details including all its members profiles and decide on what project to throw money into.

Will it work?

As, Is Operators and Explicit Conversion, What’s the Difference?

is operator is used to check / verify if an object is compatible with a given type.

int a = 0;
if (a is string) {} // result is false

as operator is used to perform certain types of conversion between compatible, or nullable, types.

as operator will return null type whenever it encounters exception during conversion. as operator will not throw the exception.

int a = 0;
var b = a as string // b is null

Explicit conversion, on the other hand, will throw exception when it encounters one.

int x = 10;
var y = (byte) x; // valid operation

CSS Language: SASS vs {LESS} vs xCSS


My take is {LESS}. That’s the short answer.

Kind of longer (and boring) answer:

There is only slight difference between the two. The biggest challenge is syntax learning curve, everything else (IDE plugins, features, requirements, etc) is much or less the same.

One consideration is how heavy will we (or the consultants) use the framework? When used heavily, syntax and language can be complicated and hairy, hard to understand. New comers will have significant learning curve. However, either way with SASS or LESS, we will have the learning curve.

I want to say we should go with framework that we most comfortable to develop with. At the end of the day, we use this framework to deliver product, so the more we comfortable with the framework, the more we can beautify the site and deliver product. This also true for consultants we hire to do the UX piece. But, consultants leave us with their code which bring us to maintainability subject. And the question for that is: which one we are more comfortable to maintain?

But what makes me really pick LESS is not because I am more comfortable with them. Instead, it’s more because of the community support (and usage for that matter) for this particular framework. SASS used to have more active development but lately LESS has taken the spot despite being newer that SASS. Community’s acceptance and implementation of LESS is also increasing rapidly as shown in’s tags counts and BuiltWith usage statistic. Not only this means LESS is gaining momentum, but also support level that we can expect outside of official documentation.






Age Oldest (v 3.2.5 as of this writing) Newer (v 1.3.3 as of this writing) Newest (v 1.0.1 as of this writing)
Active Development Open Issue 5/16/12: 84

Open Issue 1/12/13: 83

Pending pull request 5/16/12: 3

Pending pull request 1/12/13: 7

Commits count 5/16/12: 35

Commits count 1/12/13: 14

Open Issue 5/16/12: 392

Open Issue 1/12/13: 112

Pending pull request 5/16/12: 86

Pending pull request 1/12/13: 10

Commits count 5/16/12: 11

Commits count 1/12/13: 84

Requirements Ruby

Each rule in one line (SASS syntax)

Proper indentation (SASS syntax)


Compiler PHP-enabled server
Documentation Online – Excellent

SO: 1431 tags

Online – Good

SO: 1260 tags

Online – Good

SO: 0 tag

Key Features Inheritance

Nested rules


Mixins (set of styles in a variable)

Function and operation

File ‘includes’


Nested selectors



Math operations

File ‘includes’


Interpolation (string & selector)



Nested selectors


Math operations

File ‘includes’

Language Type Compile Compile

Run-time compile (with JavaScript)

Run-time compile
Pro Support 2 syntax (SCSS – CSS-like syntax and SASS – Ruby-powered) Syntax matches CSS convention

Usage is common

Cons SASS syntax is learning curve (contrast to CSS convention)   Tedious and quirky setup

Variables definitions decrease readability


Some sources and links

Comprehensive comparison:
BuiltWith {less} Counts:
BuiltWith {less} Trends:

Mind Achievement

What the mind of man can conceive and believe, it can achieve.

– Napoleon Hill

Not The Same

The significant problems we have cannot be solved at the same level of thinking with which we created them

– Albert Einstein

Stylesheet Limits in Internet Explorer?

This is something I am not aware of, not even thought it makes any sense. Internet Explorer, version 6 to 9, does have some limitation to include CSS files. It only allows as much as 31 files to be included in a page.

Eric Law went to explain why this is the case. The limitation has to do with IE using 32bit integer to identify these stylesheets rules.

However, this is not an issue in IE 10.

Digital Invoices and Receipts


I am sure this is out there somewhere, either in form of idea or actually application.

The idea is simple, an application that will manage digital invoices and receipts. Obviously, to be 100% paperless, it requires cooperation and integration with a lot parties such as retail stores, restaurants, vendors, service providers and basically all the places where we normally get our invoices / receipts. However, this ideas deals with management of the digital documents as well as helping digitalized existing one in any way possible. This will encourage all parties to start sending their invoices / receipts digitally.


  • Paperless, earth friendly, green living.
  • Security, no misplace of documents.
  • Ease of management.
  • Fasten document submission / processing (reimbursement, tax filing, etc).
  • No loss of documents.


Build an application that allows users to manage their digital documents. The system can upload, organize, and store all user documents. From this portal, user can also print or email out specific document.

Some of the ways we can digitalized existing documents are by scanner device and mobile app to take photo of the documents. After these documents are digitalized, the device will automatically upload them to user’s account in our application.

The application provides email inbox where users can send in the invoices / receipts as attachment. The system will then parse the attachment and turn in to digital documents. The email inbox is user-specific and can also be used for any stores to send digital document to the user. Eventually, the documents will be available when user logs in to the application.

All documents uploaded to the system will be OCR-ed. This way, users can categorized their documents based on vendor names, recipient names, prices, etc.


Will it work?