But, I think it’s a bit more than that. Happiness is also about making sure your surroundings are happy. Sure, you can isolate yourself from all that mess, but sooner or later you will see that there’s only so far you can run before the reality of living in a social, well-connected, interdependent world bites you. But, I digress. So, then what is happiness? Is it dependent on others appearing happy? Is it just wealth? Is it just success? Being content?

I don’t know. But, that admitted, I can now say that there is one underlying factor I see in all people who are happy – they live, and I mean really live life without regrets. It’s really not easier said than done. We make mistakes all the time, but only the weak let themselves fall behind and repent all their life instead of picking up and making sure the mistake(s) of their life work for them in the long term. So that’s it – live life like you have no regrets and everything that makes you happy will casually follow.

Here’s how I keep myself happy, and everyone knows I am always cheerful and optimistic -

1. Be dreamy; imagine the good that has yet to come in your life.

2. Stop worrying and just do it. If something worries me a lot, be it whether injustice towards me or someone else, I try my best to take action at the right time.

3. Never say no to yourself.

4. Do unto others the way you would have them do to you. This is not just a biblical verse. It’s one of the first step towards being human. Is your selfish behavior making life worse for someone else? You will never be happy because guilt is subliminal and goes with you.

5. Keep yourself enlightened; Never stop learning. I could learn something new everyday and still know only so much about this wonderful world.

6. Don’t let negative energies or thoughts build up. This one is really hard to adhere to, and I fail often. Maybe that’s why it’s so hard to be 100% happy! And no, this doesn’t fully conflict with being optimistic. You could be largely optimistic and still have negative ideas about something in your life.

7. Don’t let others rule over your life. The only person in control of your life should be you and a very very small group of really close family members. Everyone else doesn’t matter.

8. Be loyal to people you care about.

9. Don’t lie. This is easier done than said, actually.

10. Do whatever it takes to keep the important people in your life happy. If they’re unhappy, you’ll never be happy.

11. Money is immaterial. It’s all about your mind. If you are smart, money will come, if not now, then very soon.

12. Always always think about changing the world for the better with your actions. Everyone is capable of doing so. Just smiling at that person in the train could make their day better and lead them to do something nice for someone else.

13. Be largely immune to selfish thoughts. Avoid jealousy. If you’re happy you’d be more worried about making sure that other jealous people don’t infect you with negative vibes.

14. Travel whenever you get the chance. Embrace change in surroundings.

I think this is it. This is how I stay happy and continue loving my life.

You can, too!

PS: Plato was a genius. If you’re really interested in understanding humans around you on a more philosophical level, you owe it to yourself to read the Republic. I will do so soon, too.

People are being violated in public by these employees, threatened, humiliated, etc. etc. On last count, the TSA was successful in apprehending some drug abusers. But, that’s besides the point of this article.

Every country needs safeguards to make sure that air safety is not compromised by rogue elements. The easiest way to implement them is at the physical level right at the port of entry/departure. This is what the TSA seems to be doing. The reason this is inefficient is that in this day and age, there are more reasons to rely on intelligence and psychological analysis than the brute force method of X-Raying individuals or frisking them at the airports.

The problem isn’t just this frisking. When you take into account that pre-boarding security is often complemented by post-arrival immigration checks, the process is visitor unfriendly at best.

Why cannot intelligence be combined at all levels to make the process seamless? Surely, any country that would bar an individual from entry at the immigration post would like to do the same at the point where the individual tries to even get into a flight into the country. This is what is lacking in the current security regime in the US. It is like different organizations are running their own respective shows.

Compare this to traveling within European countries. There is freedom of movement and hence a lot of intelligence is (presumably) utilized to make the process hassle free for genuine travelers while at the same time keeping checks on shady individuals. When you travel from one country to another, you’re often not even forced to get into an immigration line, because there is no immigration! You just show your travel documentation briefly to the airline representative manning the gate at board time. This is convenience, and this truly signals ‘Welcome to our country’.

We’re developing an iOS application, and of course, the user would have to input some personal information before he/she can start using the application. What kind of validations should be implement on the device? Which ones on the server?

Most people, especially when starting out on a new project, consider input validation to be a fairly trivial problem statement with fixed states. But, as the application matures, they fairly quickly realize that every input has its own set of error and valid states. The validation problem grows exponentially with the number of user inputs on the device, as every combination needs its own validation, more or less.

I firmly believe that validation should never be done on the client, unless that’s the only place you need to do it. If there’s even a single server side validation component in the project, the team is better off delegating it entirely to the servers. This makes life much more easier for the front end developers and also makes testing easier. If your application depends on a web service (as most iOS apps do), chances are that the web service would in the near future completely rewrite its required inputs specs and then you will find yourself in a situation where instead of adding new features to your iOS app, you are spending valuable time in trying to get all the client side validations in place. This, until the next time this repeats itself.

That said, there is also a need to think about whether that input is really required. Let’s not forget that iOS devices are mostly mobile gadgets where the users are generally in a hurry to complete a particular task. Even if it’s their first time using the application, forcing them to input personal data which is only partially required is detrimental to the entire user experience. It adds unnecessary validation.

Conversely, if you have an input component in your app, then you necessarily HAVE to validate it. If you’re not validating it, it’s not important, and hence, must be disposed off.

Lessons: Abide by the Apple Human Interface Guidelines, always. Don’t force your users to input more information than is logically necessary for the application to do its job. If you have to perform input validations, do them all at one place, and that place is the server where you have the necessary processing cycles.

It sounds really simple in intention, except that it really isn’t. The bill’s sponsor, Senator Charles Schumer (Democrat NY) states that it is beneficial to the country because it ‘Would Hike Fees On Personnel Companies That Exploit U.S. Visa Laws’. Wait, what?

Before I state my reasons for supporting this bill, I would like the discuss the exploitation Schumer talks about. The H1-B/L1 visa categories are particularly controversial, in part because they are both what are known as ‘dual intent’ visas. This means that any H1-B/L1 visa holder is allowed under US immigration law to seek a path towards permanent residency in the country. Why this complicates the entire debate – they are both mandated to ‘temporarily employ foreign workers’ in specialty occupations. According to Schumer, ‘It will also avoid adding to the deficit by raising fees on a handful of foreign corporations that abuse U.S. visa programs to import workers from India.’ So, it is clear – the bill’s primary target is Indian IT companies, namely Infosys, Wipro, TCS, and Mahindra Satyam. All these companies are also responsible for the majority of American offshored work as well. So, where is the exploitation? It is clear that the companies bring foreign workers to the US temporarily for a specific work project and for a specific client. Of course, owing to the aforementioned dual intent provision, these temporary workers are free to obtain permanent residency in the US, too, but few do. I bet this mostly due to the contractual nature of such an engagement.

The exploitation Schumer refers to could be the fact that these Indian companies are what are called ‘H1-B dependent’ companies. Simply stated, these are companies with 15% or more employees on an H1-B. These companies pay extra for this ‘privilege’ come time to apply for an H1-B. They also have to provide an attestation that they made ‘good faith’ efforts to hire Americans and that no American jobs would be lost as a result. But wait, there’s a rider. If the company hires workers with a master’s degree or pays them above a threshold salary, they aren’t required to attest anything, not that it’s genuinely easy to find qualified software engineers in the US.

So, please don’t give these companies a bad name. They are not exploiting any visa laws. At best, they are exploiting America’s global push for open markets at open labor rates.

Now, onto why I support this controversial bill, irrespective of the absurdity surrounding penalizing legal immigrants to keep illegal immigration in check. These are my points:

1. This is a good reminder that there are great opportunities elsewhere. USA is the world’s biggest importer, but there are tremendous opportunities in other parts of the world. Infosys, please start bidding on Indian projects as well.

2. This bill is no doubt the harbinger of a greater push towards immigration reform during this presidential term. Schumer has long been a proponent of meaningful immigration leading to a speedy path towards permanent residency. This bill lays the groundwork for such reform. It’s time to tell the world that America would rather import talent permanently than send it back.

3. This is the biggest reason – the bill inherently kills the ‘desi consultant’ business inside the US. These are the real culprits. Basically, these are small time body shops that work at the third or even fourth tier of the consulting business, are almost always owned by first generation Indian permanent residents with another primary source of income, have no business plan, are really H1-B dependent, and have no code of ethics. There are various reasons why someone would join such a company. For most, it’s the easiest path to getting an H1-B (and subsequently legal residence) after completing education in the US. With this new law, such companies would have to shell out extra for every new H1-B petition. This eats into the already meager margins at which these shady companies do business. But, the topic of small consulting companies deserves another blog post of its own.

4. Speaking as someone who earned two graduate degrees from a top American university, I wholeheartedly support any measure that provides confidence to American students that engineering degrees are good and that there is going to a be a job available for them when they graduate. This leads to the much greater issue in my opinion, that of regulating US Inc. such that while global talent and liberal immigration is welcome, steps ought to be taken to ensure a level playing field for people born in the country. It’s not their fault that everything is cheaper abroad. Almost every developed country has such protective measures in place. America should, too. Too bad it would need political might to rein in capitalism.

America is lucky to have a very active immigration debate in this day and age when every other country is on its toes to recruit talent globally. People want to move to America for a better life, better future, and for freedom to take risks that they couldn’t back home. I can only hope that something good comes out of bills like HR 6080. In the interim, I am confident that these steps would lay a strong groundwork towards making comprehensive immigration reform a more welcome agenda in the minds of Americans and would-be immigrants alike.

Cheers!

I hope you enjoy the new – posterous.cerebrawl.com!

The premise is that if you’re a budding entrepreneur with viable investment money on hand, you should be able to freely come to the US as a nonimmigrant to start your business. Hitherto, the only ways to come to the US without having been born here have been through a buffet of non-immigrant visas or being able to secure work in the country. The latter has always been classified as a dual-intent visa that allows you to also apply for permanent residency through employment based green cards. Notice the importance of intent. If you’re a student and you give the guy at the consulate the impression that you’re going to find a job after graduating, there are grounds to reject your non-immigrant visa.

This becomes an important issue to consider when you realize that MOST of the successful companies in the US were started by people who first came to the US on these student or other non-immigrant visas. Statistically, most successful startups are also conceptualized and governed by people in their late 20s or early 30s. Also, quite a few, if not all, entrepreneurs work for a while IN THE USA before they think, ‘Hmmm, I should start a business doing this’.

MISTAKE 1: Emphasis on intent

Now, once you’re in the USA, you complete your education from one of the top schools in the world. Even though you hardly have any American students in your Algorithms class, you are optimistic, and you get that degree. But wait, you get one more just because you love being in school. And here you are, one of the brightest people around, have a potential career, have a strong head on your shoulders, are optimistic, etc. What next? You apply for a job! Yey, right? No. Because…you’re now a potential immigrant, are suddenly a bad guy because you’re trying to reduce wages, and worst of all, you aren’t American. You are in line for a work permit.

MISTAKE 2: Treating international graduates like first time immigrants

But, before you get a work permit, you have to be worthy enough for a company to spend more than $3k on lawyer and application fees for you. On top of that, thanks to the xenophobia and immigration backlash, they have to contend with the fact that the other employees might link your getting hired to their kin losing jobs. I know it’s ass backwards, but bear with me. In the quest to get a work permit, who wins? Half of that $3k figure is actually lawyer costs. In a country where the insurance company makes more than the doctor this doesn’t surprise me one bit. Compare this to Canada, where just like healthcare, you don’t need a middleman to file your paperwork.

MISTAKE 3: Making it hard to actually get a visa

Now you have a visa, a job, and are making some money. You’re being a good non-citizen – paying more taxes than citizens (you can never avail a lot of benefits reserved for citizens), contributing to the society, making kind donations for the needy, obeying the civic laws, etc. Then, you realize that you’re actually good at what you do, and there’s a lot of sense in starting a business. Well, welcome to America! You can start a business but you cannot work for it! We like passive investment, but you cannot do anything more than putting in money. Which means, you’d have to have a full time job, worry about keeping it, all the while as you struggle to start your company and make it profitable. You have a choice – move to Canada or Chile while you’re still young or live the American H1B dream.

MISTAKE 4: Wanting the best but doing nothing to keep them here

So you eschew the idea of starting a new enterprise until you are a legal permanent residence and don’t have to worry about being employed all the time. Well, there’s an app…err I mean paperwork for that. And, if you are a citizen of China or India, you are looking at almost 6-7 years of patiently waiting before getting anything back out of that paperwork and large amounts of attorney fees. Depending on when you file for your permanent residency, you could all but forget about marrying that girl you knew back home, because she could marry you but not come back with you. Splendid.

MISTAKE 5: Making timely legal immigration some sort of a pipe dream

Once you get that ever so elusive green card, you’re fed up, tired, old, and the torture you faced has made you an immigrant hater yourself. Then, there’s the added pressure of hearing about all those successful peers that went home when there was time and made big bucks. So, what do you do with that green card? Well, you use it to help your retired parents spend the rest of their life with you here in America where you nearly got everything you wanted when you wanted.

There was a time when people actually went through all this effort, because frankly, there was no better place to work than in America. Things have changed A LOT since then. There’s a mass exodus of young non-immigrants from the US to other countries. These people came here, got educated, loved working hard, met great people, but they don’t want to toil away for a piece of paper that still wouldn’t release them from the xenophobia that they so wanted to overcome.

So, where does the Founders Visa fit in? Some say it should be an entirely new visa that looks at you as a capable entrepreneur, gives you a few years to prove it, and requires some amount of backing by established investors. If you fail, you leave the country.

Are you fricking serious? I am sure that’s so enticing.

Some argue that it should be an extension of the EB5 permanent residency category. The category that lets you come to the US, no holds barred, for a mere amount of $1,000,000 ($500,000 through a rural investment). That’s really it. Invest that amount of money and you’re guaranteed a happy retirement in the United States of America! All it takes is 2 months of paperwork and lawyer fees. Splendid again.

You know why the Founders Visa proposal sucks?

IT IS STILL A VISA AT THE END OF THE DAY

You are not inviting any talented people to the country by making such an entry conditional on their being successful. Are you serious? Do you ever go out during the day? Do you have a social life? How do you explain the pressure on these entrepreneurs who have to compete with undocumented immigrants (who, by the way have it way way easier)?

How many entrepreneurs would come to the US just to take a risk when Canada would simply look at their education and give them a permanent resident status? Do you think they would leave their families behind?

More importantly – How do you define success?

The Founders Visa suffers from all the mistakes mentioned above. Congratulations, you didn’t provide any solution.

IT IS STILL A VISA

Addendum: I realized later that my post might come across as starting off with the mistakes in the new proposal. That is not true. The main reason I list the problems with the current policies is that I believe they should be addressed before we start baking a second layer of our cake. Also, I believe that if the intent of the visa is to attract people who have never been to the US before, the facts that it is still a temporary permit and that it banks heavily on the beneficiary being successful are also the flaws of the proposal.

If the intent is to keep the bright people from leaving, then the mistakes listed need to be addressed. There’s just too much hard work involved in being successful, and the headache of worrying about a stable US presence just makes the proposal not worth it.

This Wednesday, I got the chance to debate just this with the CTO of an iPhone startup here in Washington, DC. While I am short on the person’s technical background, he did mention that his previous programming experience was doing website development using Flash and Dreamweaver.

The seed for the debate was laid last week when I met with their co-founder and while going over my experience with the SDK, briefly mentioned how elegant the app development workflow on the iPhone was, thanks due in large part to IB and the way it stores object information. I was then told that the company only believes in handcoding every single UI element for an iPhone app, and that it should be good reasoning out the benefits of each approach (hand coding vs. designing using the IB) with the company’s smartest person.

Having moved to Cocoa from a Java background, I can understand why a developer would not like the elegance and, arguably, added development steps mandated by the Interface Builder. Almost every programmer has been badly burnt by such tools in the past. And, almost all of these developers are only just now making a foray into Mac development because of how hot the market is right now. Every other programming framework has taught developers that it’s not the design that matters, rather the end product. Very few developers adhere to the keep it simple principle, and countless volumes have been written on why too much abstraction is actually a bad programming practice. While reusing code is a novel concept, there is a tradeoff with simplicity.

In the Mac world, such a conundrum does not exist. The tools for development are provided by the company that also happens to be the only company working on the Mac hardware and software ecosystem. They have a vested interest in making sure that development is consistently a wonderful experience for both the programmers as well as the testers. And, with a company that has such an academic backdrop of excellence, as Apple, chances are that they have spent a good amount of time in making sure that the development toolkit adheres to best practices in development.

Below are the points raised by the person and my reactions.

Interface Builder makes the project unwieldy and hard to understand.

This is absolutely not the case if you’re a good developer. One of the best practices I mentioned above is that application design is a separate task from application coding. Interface Builder lets you do the design work without worrying about what the code is going to look like. In almost all instances, it also provides you with a good way to enumerate the object and view interfaces that you would like to expose to other classes in your application. Design comes before coding, and by mixing the two, you’re absolutely laying the groundwork for making your application a terrible failure prone to App store rejection from the get go.

The reason your apps are difficult to understand is that the developer did not follow established norms when it comes to using IB. From Apple’s own documentation: ‘A very simple application might be able to store all of its user interface components in a single nib file, but for most applications, it is better to distribute components across multiple nib files’. The mainwindow.xib should be just that…the main window minus any views. This way, you minimize load times. Also, I follow the convention of having every view complex or custom view in its own nib. The formula I follow says that an nib should only have views that are needed at that particular application lifecycle state. This way, I know which nib to look at if I want to clarify some connections.

Basically, IB would only make the project unwieldy if a bad developer worked on it.

IB cannot do most customizations needed by apps

This argument lacks a backbone in 95% of the cases. You can perform almost all kinds of customizations using IB. Want a bunch of labels inside a UITableViewCell? How about a combination of labels and images? How about controls inside a UIScrollView? All this can be done using just the IB. Well, there are a lot of cases where you might want to handle customizations by code (complex composite cells for example), it doesn’t negate the fact that, even then, in the interest of keeping the design process consistent, you’re better off having an NIB before you customize. In fact, Apple recommends doing so because there is a lot of framework code that stands the chance of being over-ridden if you decide to do everything from container allocation to adding to a view programmatically.

That said, I would argue that over-customizing almost always leads to bad application sales. Almost all the best-selling apps for the iPhone maintain the signature look and feel of the preliminary pre-installed applications. There are no performance or behavioral gains from using non-native UI elements.

IB is for newbies; you learn with it, but give it up

Not unless you want to enforce bad design principles for the lifetime of all your subsequent Mac projects. As mentioned earlier, IB is a design as well as coding tool. It serializes objects in a file that is lazy loaded in a perfect order and with well-tested memory management in place. Also, doing so involves the use of a lot of frameworks that not only make life easier, but also reduce chances of code defects.

We have used design tools in the past, and UI development using code trumped all

This is just the side effect of using bad tools for a long time. Such thinking has to go. Apple developers have been working with IB for a few years now. The toolkit keeps on expanding and getting better. Don’t let your previous bad experiences let you make bad design decisions. Do it the right way. This is not an Adobe framework.

I am very interested in doing a followup to this post on a more technical level, but I really wanted to share with other fellow iPhone developers the importance of working with the IB, not against it. The tool is there for a reason. Learn to use it. Apple recommends IB for every project.

Remember, when it comes to software engineering, it’s not always the end result that matters, but also how much future proof that solution is. Being engineers, we’re also designers – software architects, and it is upto us to engineer something beautifully, or make our product look like a patchwork of sorts.

Now for the exciting part. I am married, drive a hybrid, don’t have roommates, and no longer commute 2.5 hours to and from the client site to work on some of the most technologically backward and ill-designed projects ever. I am now a more serious iPhone and Mac developer, thanks to the commute time saved, and have actually gained enough experience to put out apps (albeit small ones for now) on the App store.

I have gained more understanding of how small business in America works. I have seen the economy take one of the worst nosedives in my lifetime, and seen desperate efforts to bring it back on track. I have seen people responsible for the mess make it big, and I have seen people suffer. I have been humbled. I have come out stronger.

For those wondering what I am up to now, I am still the good old me, although with the wisdom of two. I am still diffident, so much so that I sometimes sell myself short, but it doesn’t matter. The people who are smart enough to realize my strengths are the ones that mean something. I am now, however, spending a lot of time pursuing my passion – learning to become a diligent software engineer, working on mobile services, next generation entertainment and communication software, and of course ECM. You can teach a violinist how to use their long fingers to type fast, but you can’t teach them how to compose poetry with their keyboards. Being able to do just that is something I am proud of. Thank you, school!

I am back, and hope to make this blog mine once again. Thanks for being a reader.