Skip to main content

A US Visa Experience

A US Visa at last, just B1 to be exact but somewhat fulfilling . After several hours of anxiety and waiting for a make or break interview with the consul , I nailed it. It came after several weeks of document preparation of course .

So here are some tips that I gained from the experience which may help :
1. Take time to read the instructions that comes with the DS157 form.
2. Fill up carefully the DS156 online and the DS157 manually.
3. Prepare the documents needed . If you have invitation letters , official letters from the company or any important documents that may be connected with your purpose of visiting the US , review them and make sure they are complete and authentic.
4. Prepare documents that may establish "strong ties" with Philippines ( reasons that will make you comeback). These may be in the form of bank statements , land titles , car registrations , existing contracts and others (some even brought photos of their family). I was not asked to show it to the consul but just bring it to be sure.
5. Come early on the day of the interview and make sure all your documents are with you.
6. As much as possible wear something smart casual and comfortable.

Some tips during the interview:
1. Be cool and keep an eye contact with the consul.
2. Answer all questions honestly.
3. Provide the additional documents he may ask . Be polite in giving honest reasons if those documents are not present.

Additional Tips:
1. Ask questions, some friends or colleagues that have undergone the application process can tell you a thing or two.
2. Read some forums regading the topic.

I find myself lucky in situations like this. On some interviews and applications (which maybe for employment or otherwise) I usually nail it on the first try. Marriage , of course is another story . Ill try to nail it the second time I suppose (hahahah)..


joms said…
can't help but to laugh in these lines:

"I usually nail it on the first try. Marriage , of course is another story . Ill try to nail it the second time I suppose"

just keep on nailing and don't screw yourself :) sheesh, i was supposed to comment on your US visa experience but, that one made a hard hit. haha. apir!
Marvin said…
yeah right...maybe ill just screw around till somebody nails me hahaha

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless