Changes

Jump to navigation Jump to search
m
no edit summary
Line 65: Line 65:  
I have been working as a software engineer for 6 years and I have been programming in Python for most part of it.
 
I have been working as a software engineer for 6 years and I have been programming in Python for most part of it.
 
** Worked as a contractor at Google for 1 year 5 months (Python throughout)
 
** Worked as a contractor at Google for 1 year 5 months (Python throughout)
*** Obtained Python readability (Google seal of approval that I can write readable Python code) from [http://en.wikipedia.org/wiki/Alex_Martelli Alex Martelli]
+
*** Obtained Python readability (Google's internal seal of approval that I can write readable Python code according to their guidelines) from [http://en.wikipedia.org/wiki/Alex_Martelli Alex Martelli]
 
*** Improved quality of code by performing code reviews on daily basis for the team (for about 6 months)
 
*** Improved quality of code by performing code reviews on daily basis for the team (for about 6 months)
 
* Passionate about Opensource
 
* Passionate about Opensource
** Quit my jobs as software engineer in an MNC and went to work for an NGO as their IT manager
+
** Quit my job as software engineer in an MNC and took up the position of IT manager for a local non-profit organization
 
*** Had the opportunity to fully realize my long-time passion for Open Source Software (OSS)
 
*** Had the opportunity to fully realize my long-time passion for Open Source Software (OSS)
 
*** Delivered the solutions using exclusively OSS
 
*** Delivered the solutions using exclusively OSS
Line 75: Line 75:  
**Won appreciation award for the self-initiative of single-handedly developing a custom test automation framework for streamlining QA
 
**Won appreciation award for the self-initiative of single-handedly developing a custom test automation framework for streamlining QA
 
**Received first prize in intra-college software competition
 
**Received first prize in intra-college software competition
**At the NGO, managed the development of web applications. Increased the number of unique visitors to the website over 30 fold within a year. Saved around 20% in operational costs through streamlining various processes.
+
**At the non-profit, managed the development of web applications and increased the number of unique visitors to the website over 30 fold within a year. Saved around 20% in operational costs through streamlining various processes.
    
===Myself and the community===
 
===Myself and the community===
Line 82: Line 82:  
<!--Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.-->
 
<!--Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.-->
 
:Sugar (& OLPC), I believe, is based on the principles of Constructionism. Discoverability and learnability of the system features with minimal external help hence becomes very important factors. This project will pave way for a framework for improving the discoverability of the features of the system in a customized manner depending upon the individual using the system. I am going to bank upon only one factor: age. But once the framework is mature (12-24 months), I can imagine various plugins that take into account other differences: culture, previous experience with technology, physical disabilities - to name a few. This will immensely improve the system's reach and usability among the millions of children using it every day. This could also enable activity and system developers to target certain features at specific users without worrying too much about whether it makes sense to have it for all users or whether the UI is getting too complicated or the system is going to suffer from feature creep .. etc.
 
:Sugar (& OLPC), I believe, is based on the principles of Constructionism. Discoverability and learnability of the system features with minimal external help hence becomes very important factors. This project will pave way for a framework for improving the discoverability of the features of the system in a customized manner depending upon the individual using the system. I am going to bank upon only one factor: age. But once the framework is mature (12-24 months), I can imagine various plugins that take into account other differences: culture, previous experience with technology, physical disabilities - to name a few. This will immensely improve the system's reach and usability among the millions of children using it every day. This could also enable activity and system developers to target certain features at specific users without worrying too much about whether it makes sense to have it for all users or whether the UI is getting too complicated or the system is going to suffer from feature creep .. etc.
; 2. Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
+
; 2. <!--Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed.--> Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?
:I would like a deployment center at UBC, Vancouver. I will also work with my university in locating students to try out the UI through the university's summer programs and other outreach efforts such as Science exhibition fairs.  
+
:I would like a deployment center at UBC, Vancouver. I will also work with my university in locating students to try out the UI through the university's summer programs and other outreach efforts such as Science exhibition fairs. If possible I would like to observe children using the UI before beginning coding.
 
:Optional, after GSoC: I am also interested in observing how children with radically different levels of exposure to technology react to Sugar. I will be travelling between Canada and India (once a year). Hence, if it is possible, I would also like to visit a center at India when I am there and observe how differently the children who have minimal (affordability and) exposure to technology react to the design of SugarUI / OLPC.
 
:Optional, after GSoC: I am also interested in observing how children with radically different levels of exposure to technology react to Sugar. I will be travelling between Canada and India (once a year). Hence, if it is possible, I would also like to visit a center at India when I am there and observe how differently the children who have minimal (affordability and) exposure to technology react to the design of SugarUI / OLPC.
 
; 3. What will you do if you get stuck on your project and your mentor isn't around?
 
; 3. What will you do if you get stuck on your project and your mentor isn't around?
Line 109: Line 109:  
         as a research scientist in a usability lab
 
         as a research scientist in a usability lab
 
       work with children in making computer a viable part of their creativity tool-set.
 
       work with children in making computer a viable part of their creativity tool-set.
 +
 +
  Research Ideas
 +
    One exciting idea, that I have been dwelling on from my undergraduate years and made an unsuccessful attempt at college, is on adaptive interfaces. I want to research on interfaces that are a breeze to use irrespective of the different types of users and systems. The interface adapts statically and dynamically to both the users on one end and the system on the other. The static adaptations depends on pre-generated profiles for the systems and users. The dynamic adaptations depend on various factors like the current avg. load on the system, time of the day/year, weather, current social scenario and ultimately self-learning from the demonstrated preferences of the user.
 +
 +
    
=====TODO=====
 
=====TODO=====
48

edits

Navigation menu