Elgg is an open, flexible social networking engine, designed to run at the heart of any socially-aware application. Building on Elgg is easy, and because the engine handles common web application and social functionality for you, you can concentrate on developing your idea.
Elgg is open source. That means, when you use Elgg, you have the benefit of being part of a large developer community, with the security and stability that hundreds of eyes can provide. It’s also headed and used by Curverider and its partners, so you can be assured that it’s in commercial use and will cope with the demands of a popular application.
Elgg comes with advanced user management and administration, social networking, cross-site tagging, powerful access control lists, internationalisation support, multiple view support (eg cell phones, iPhone), an advanced templating engine, a widget framework and more.
There are several options:
- Use Elgg’s out of the box features; this is called a vanilla install
- Add more by installing plugins – for example, blogs, forums, social bookmarks
- Develop your own features, or hire someone to do this for you
Project Home Page
Mike Brittain wrote:
In the months prior to leaving Heavy, I led an exciting project to build a hosting platform for our online products on top of Amazon’s Elastic Compute Cloud (EC2). We eventually launched our newest product at Heavy using EC2 as the primary hosting platform.
We set out to build a fairly standard LAMP hosting infrastructure where we could easily and quickly add additional capacity. In fact, we can add new servers to our production pool in under 20 minutes, from the time we call the “run instance” API at EC2, to the time when public traffic begins hitting the new server. This includes machine startup time, adding custom server config files and cron jobs, rolling out application code, running smoke tests, and adding the machine to public DNS.
What follows is a general outline of how we do this.
PHP is the world’s most popular server-side Web scripting language. This reference card was created to help you quickly navigate some of PHP’s most commonplace features, including objectoriented programming, array and string manipulation, regular expressions, and MySQL integration.
Features include Configuration, Popular PEAR Packages, Object-Oriented PHP, Regular Expressions, MySQL Integration, Hot Tips and more.
PHP Refcard – Download
François Zaninotto wrote:
When faced with the alternative between an off-the-shelf CMS or a custom development, many companies pick solutions like ezPublish or Drupal. In addition to being free, these CMS seem to fulfill all possible requirements. But while choosing an open-source solution is a great idea, going for a full-featured CMS may prove more expensive than designing and developing your own Custom Management System.
Given number of available open-source CMS solutions, building one on your own sounds like a stupid idea. But if your website is 50% content management and 50% something else, you probably need to start with a web application framework like Symfony or Django, rather than a CMS. These frameworks provide plugins that do part of the Content Management job already, so creating a CMS today is like assembling Lego bricks to build something that exactly fits your needs.
A recent Gartner Research study found that 10 percent of the PHP community are corporate IT developers, and predicted that during the next five years, that number will grow to 40 percent. That’s good news for PHP developers looking for corporate gigs, and very good news for PHP tools maker Zend Technologies, which cited the Gartner finding at the Zend/PHP Conference last week as evidence of widespread, more strategic adoption of PHP in enterprises.
Zend is trying to position its products, the PHP development framework Zend Framework and the PHP IDE Zend Studio for Eclipse, as the de facto standards for enterprise PHP web development as the language becomes more mainstream. If Zend is judged by the company it keeps, then it has chosen its allies well, forging relationships with IT heavyweights such as IBM, Oracle, Microsoft, and most recently, Adobe.
36 steps to success as technical lead
- Define early on what success means for you, the team and the business.
- Believe in the project: idea, architecture, time, team.
- Understand the domain, the business requirements and the technical challenges.
- Know your team: strengths, weaknesses, ambitions and personalities.
- Have a plan as a result of a planning activity.
- Be part in the design of everything.
- Get your hands dirty and code.
- Act as a communication proxy for your team.
- Make sure everybody understands the big picture: their work has implications.
- Fight for architecture and design consistency.
How not to lead geeks
- Downplay training.
- Give no recognition.
- Plan too much overtime.
- Use management-speak.
- Try to be smarter than the geeks.
- Act inconsistently.
- Ignore the geeks.
- Make decisions without consulting them.
- Don’t give them tools.
- Forget that geeks are creative workers.
Nine things developers want more than money
- Being set up to succeed.
- Having excellent management.
- Learning new things.
- Exercising creativity and solving the right kind of problems.
- Having a voice.
- Being recognized for hard work.
- Building something that matters.
- Building software without an act of congress.
- Having few legacy constraints.
Top 10 ways to demotivate your programming team
- Set up impossible deadlines.
- Let them work overtime.
- Don’t allow breaks.
- Place a ban on laughing.
- Break the coffee machine.
- Don’t shield them from the dirty daily business.
- Don’t challenge them.
- Underpay them.
- Bribe them.
- Infiltrate a team member who is demotivated anyway.
Don’t bring me solutions, bring me problems
(Don’t tell me how you want it to work, tell me what you want it to do)
- Where all think alike, no one thinks very much.
- Suggesting solutions kills creativity.
- Don’t bring me solutions, bring me problems.
Classic mistakes enumerated
- Undermined motivation.
- Weak personnel.
- Uncontrolled problem employees.
- Adding people to a late project.
- Noisy, crowded offices.
- Friction between developers and customers.
- Unrealistic expectations.
- Lack of effective project sponsorship.
- Lack of stakeholder buy-in.
- Lack of user input.
- Politics placed over substance.
- Wishful thinking.
The practices discussed in this article are based on Ezequiel Cuellar’s observations. These practices will help any software development team as they come up against common obstacles. They will also contribute to a solid foundation for healthier development and help speed up production. The seven practices are:
- Improve business processes before starting development.
- Create a solid software development team.
- Improve processes for service requests.
- Minimize reporting of software metrics.
- Improve communication with the business team.
- Use the right programming language.
- Use the right IDE.
The practices target problems that are better addressed at the management level. Usually, developers can only report the issues to upper management for consideration. Because project managers have the necessary level of authorization, they are the ideal candidates to promote these practices within the organization.