wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

sadekbaroudi

<?php

        $sugar_config_si = array (
            'default_currency_iso4217' => 'USD',
            'default_currency_name' => 'US Dollars',
            'default_currency_significant_digits' => '2',
            'default_currency_symbol' => '$',
            'default_date_format' => 'Y-m-d',
            'default_decimal_seperator' => '.',
            'default_export_charset' => 'ISO-8859-1',

amusarra

<?php
/**
 * Project: SugarCRM Logic Expression for checking User role
 * Original Dev: Antonio Musarra, January 2014
 * @2009-2014 Antonio Musarra <antonio.musarra[at]gmail.com>
 *
 * Desc: SugarCRM Logic Expression ext class
 *
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by

chicks

Apache:
  - Activated 'KeepAlive' connections
  - Lowered keep alive timeout from 15 seconds to 2 seconds
  - Increased the number of minimum workers from 8 to 16
  - Activated server status page (/server-status)

APC (Alternative PHP Cache):
  - Set cache size to 256MB (ideal for SugarCRM workload)

Memcache:

chicks

#! /usr/bin/env php
<?php

# Stuff we have to do
if(!defined('sugarEntry'))define('sugarEntry', true); 

function usage() {
    global $argv;
    return "\n" . $argv[0] . " <path to sugar>\n";
}

jonathanmoore

Share Counts

I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.

If you want to roll up all of these into a single jQuery plugin check out Sharrre

Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.

Twitter