yh2n · April 16, 2019 14:38
diff --git a/gistfile1.txt b/gistfile1.txt
 Web forms always require special attention when it comes to programming. From the user standpoint, it is a place where we are 
 being asked to partipicate (sometimes reluctantly) and interact with an application, often to provide information that can be 
 redundant.
 I have learned that in order to ease the user experience, forms need to be well designed while conveying a feeling of
 familiarity; very informative (being explicit about the required field and the characters needed to create a valid password);
 offering proper feedback (intelligle error and not too abrupt error messages, state in clear manner the reason why
 the form can not submitted). Betwween the forms I have implemented for some personal projects and the contract work that I do
 with Independant Curators International, I have always treated web forms with a special attention by using my personal
 experience.

 I have some experience with Google analytics, since the company I am in contract with uses that tool, although on very basic 
 level. By virtue of being an international organization, they get request from all over the world and they primary look
 at source of the traffic, the amount of requests/subscription immediately following a show in a certain country, what the 
 most popular content on the website is.

 As far as as third-party integration go, I have used the Google geolocation API when building an Chat application -that I ended modifying for a larger project. I found it fairly easy to use thanks to clear documentation and lots of online resources/examples.
 I have also used the Discogs API when building Sylent -an application providing information anout a recording. It is actually 
 the first API I used and it was quite challenging at first. It wasn't very clear what path I needed to follow to access the 
 data I needed. I also ran in some issues when they made some changes to their policy and required an additional set of
 credentials (Oauth) in order access their database, without any prior notice or communication with the users (they eventually back tracked).
 More recently I used the Stripe API for a projects that allow users to collect payments. It can be a daunting task and seem 
 challenging but the basic implementation was actually -surprisingly- straightforward. Routing from the front end to the
 backed just required to be rigourous with the value of the fiels sent (setting the currency, making  sure the amount is 
 converted to cents etc).Their documentation is very clear and and the user interface allows for extensive testing and mock payments.
	Web forms always require special attention when it comes to programming. From the user standpoint, it is a place where we are
	being asked to partipicate (sometimes reluctantly) and interact with an application, often to provide information that can be
	redundant.
	I have learned that in order to ease the user experience, forms need to be well designed while conveying a feeling of
	familiarity; very informative (being explicit about the required field and the characters needed to create a valid password);
	offering proper feedback (intelligle error and not too abrupt error messages, state in clear manner the reason why
	the form can not submitted). Betwween the forms I have implemented for some personal projects and the contract work that I do
	with Independant Curators International, I have always treated web forms with a special attention by using my personal
	experience.

	I have some experience with Google analytics, since the company I am in contract with uses that tool, although on very basic
	level. By virtue of being an international organization, they get request from all over the world and they primary look
	at source of the traffic, the amount of requests/subscription immediately following a show in a certain country, what the
	most popular content on the website is.

	As far as as third-party integration go, I have used the Google geolocation API when building an Chat application -that I ended modifying for a larger project. I found it fairly easy to use thanks to clear documentation and lots of online resources/examples.
	I have also used the Discogs API when building Sylent -an application providing information anout a recording. It is actually
	the first API I used and it was quite challenging at first. It wasn't very clear what path I needed to follow to access the
	data I needed. I also ran in some issues when they made some changes to their policy and required an additional set of
	credentials (Oauth) in order access their database, without any prior notice or communication with the users (they eventually back tracked).
	More recently I used the Stripe API for a projects that allow users to collect payments. It can be a daunting task and seem
	challenging but the basic implementation was actually -surprisingly- straightforward. Routing from the front end to the
	backed just required to be rigourous with the value of the fiels sent (setting the currency, making sure the amount is
	converted to cents etc).Their documentation is very clear and and the user interface allows for extensive testing and mock payments.