Private Repositories vr. Public Repositories

Private Repositories vr. Public Repositories

What is a repository?

A repository is a place where you post information , project data and others, is a space in the cloud ( Internet ) , which serves to keep our information safely . A repository helps us to have better control of information, so the information will always be current and can make checkpoints more often.

When you develop a project, it is good practice to put the project in a repository. This is because if for some reason the project is damaged, you can return to the last working version without problems. If the project is lost or the computer you are working is damaged , please download the latest version of it.

part 1 - Why use a public repository ?

When you want to present and publish their projects and holding, use github is very important, because this is a public github repository. Thus, you can have a personal resume with all your projects, and so show your development computer engineer. 

part 2 - Why use private repository? 

When major projects are done, you need to be securely supported and information. It is also important, because only people related to each project will have access to each repository. 

In the end, the important thing is to use a repository to have projects safely and always updated backup.

Facebook & Development Environment

Facebook & Development Environment

Part 1 - Logging in using Facebook  

At first, I did not know how the system has many applications for facebook to login and comment can from different applications. After some research I understood that there is a deferential logging for mobile with Android, iOS and web applications.

As I began to develop with Facebook login, it was necessary to have a series of files made by Facebook, this is because you need to have certain security measures established by them. Once done, it's easy to add buttons add comments and share information on a specific topic.

One of the main rules is, the application can run in a just server, this can be local (within the same computer) or be on the internet. This means that if the application running off of a server, cannot connect to Facebook.

Part 2 - Installing the development environment of an existing project

When the project starts, we have all the tools necessary for their development. Not so with frequent, so you need to have to download programs, applications and files to run what currently exists.

When we proceeded to install tools databases MySQL and PostgreSQL as is necessary to pay attention to the usernames and passwords that are put during installation. This was because of the project demanded a username and password specific to access everything the right way.

Another point to consider is that although succeed in obtaining the same tools and the same versions, you can have problems. This will depend on the operating system you are using, for example, might not work in Windows, but a Mac to work properly.

Finally, once it manages to make everything work properly, you need an installation manual of the different environments they create. This in order to make the project maintainable into the future.

What is a "User Story"?

What is a "User Story"?

When a project is developed, you must first know exactly what you need to do the project. What is the main objective? This point, normally you should know if the project has a significant degree, but this usually does not happen, so it is necessary to have that dialogue with the customer.

You can create a relation of 1-1. Each use case project to a "user story". This is because both have a series of steps. A "user story" should have one main objective, it is performed by an actor, has a post-status and steps.

This can be very similar to an operation contract in a use case.

The steps are defined for a specific scenario, for example, at which time you can apply a "user story" specified.

A scenario is defined by a specific context, with specific characteristics. These specific features are defined by the client, based on what he wants to do when in that scenario.

Once you have the title of "user story", the user or actor, specific objective and that is what should be done. Now you have to define how to develop the specific scenarios.

To define the steps, you have keywords, which are: 'Given', 'When', 'Then', 'And' and finally 'BUT'.

The following is an example of a user story:

Feature: User management

  As a User

  I want to edit my personal information.

  So that I should be able to edit or delete my information.

  Scenario: Delete account

    Given that I want to delete my account.

    When I press the delete account.

    Then the system should ask: Are you sure?

    When you press "Yes", the account will be deleted.

    But if I press "No", the operation is cancelled.