Friday, 28 December 2012

Salesforce

http://blog.jeffdouglas.com/2009/04/08/start-developing-with-salesforcecom-today/

http://www.youtube.com/watch?v=ae_DKNwK_ms


  1. Salesforce.com Developer Edition – This is fully functioning, non-expiring developer account that you can use for virtually any type of development. There are some limitations (e.g. storage, licenses) but nothing that should get in the way of platform, appexchange or integration apps. Plus Developer accounts have access to pre-release functionality. What more could you want out of life?
  2. Force.com IDE – This is an Eclipse-based IDE that allows you to write, compile, test and deploy your code. It also has an integrated scheme browser allowing you to view your org’s object schema as well as construct and execute SOQL queries. This is the first app that I open each day.
  3. Apex Explorer – This is a Windows tool that allows you to browse your org’s schema and construct and execute SOQL queries. Essentially the same as the Force.com IDE but no code development features.
  4. Documentation – Documention for Apex, Visualforce, SOQL, Web Services, AJAX, etc. is available with helpful, detailed code examples. Most of what you need can be found atdeveloper.force.com.
  5. Dicussion Boards – The Salesforce.com is a vibrant and extremely helpful community. Post any questions or issues you have and you should receive a timely response from other community members or perhaps even a Salesforce.com Product Manager or senior developer.
  6. Understanding of OOP – Having a basic understanding of object oriented programming will make life easier but it’s not a deal breaker.
  7. Open Mind – Be open to new ways of doing things. Programming in a multi-tenant environment has it’s advantages as well as its disadvantages. Fortunately, the advantages well out weight the disadvantages. It takes some getting used to but it’s not rocket science.

Thursday, 25 October 2012

Linux command line commands

ls - list all files in the current directory.
ls -lart file_name - shows the permissions of the file
history |grep xxx - find xxx in the previous commands.
dir - list the directories in the current directory.
rsync -a patch/ syn/     - copies and replaces if necessary the content of patch folder to the syn folder.
ps aux |grep <name_of_the_process%>
kill -9 <PROCESS_ID>
unzip <file_name.zip> - will unzip the files to ./<file_name> folder
rm -r -f <dir_name>     - removes the directory quietly and recursively
mkdir -p <dir_name>   - creates directory and doesn't complain if it is already exists.
whoami                        - prints the name of the current user.
pwd                             - prints the current directory full path
df -lh                             - Disk space stats

vi <file_name> - Opens text file
    i    - To start typing after you open the file using vi command.
   :q! - Quit the text editor and don't save.
   :wq - Quit the text editor and save.
   :w! - Quit the text editor and save(even readonly files).

chmod u+x file_name     add execute permission to the current owner of the file.
chmod u+rw file_name     add read and write permission to the current owner of the file.
stat -c %a file_name  gives you a numeric value of the permissions.