Anyway I won some beautiful presents offered by the sponsors:

• Doctrine Book (I was thinking to buy it because I wan to jump from Propel to Doctrine)
  
• USB Fan + Light (kicks ass as Pascal said)
  
• elephpant (I’ve already other 2, but the one won has a bigger value!)
  

1day1ticket doesn’t stop so I’ll try to do my best also in August crossing my fingers to reach the goal: be in Paris next February! The bigger problem will be that I can’t use svn with my mobile connection, no I haven’t a xDSL at home because this is Italy…

The Myth of the Genius Programmer

A pervasive elitism hovers in the background of collaborative software development: everyone secretly wants to be seen as a genius. In this talk, we discuss how to avoid this trap and gracefully exchange personal ego for personal growth and super-charged collaboration. We’ll also examine how software tools affect social behaviors, and how to successfully manage the growth of new ideas. I like the idea “be a small fish” that you can see at time 19:20. It’s really difficult to improve your skills when you’re the big fish, isn’t it?

Do You Believe in the Users?

Too many programmers have forgotten about the lost art of customer service. All software has users, though most developers have forgotten how to respect them, trust them, or “sell” their software to them in an exciting (but honest!) manner. This talk will focus on anecdotes and strategies for keeping software design uncomplicated, making software fast, and putting usability above programming convenience. We’ll also focus on the importance of keeping a healthy illusion of simplicity, while allowing abstractions to deliberately leak for power-users.

Finally

Resources like these are very interesting from my point of view. Be able to follow some kind of sessions could be fundamental when you can’t meet often your friends/colleagues to work with and discuss some problems at an high level. Do you agree?

I like conferences where I can meet friends and work side by side with them learning something new every time. Is there anything better than sharing knowledge with friends? I don’t know.

Did you attend your nearest Test Fest? Do you have any suggestion for a better time writing tests?

I’m not going to write about one framework or another, this isn’t a war, I just want to think about the real advantages of using a development framework developed by other people like communities or companies (or maybe a mix of these 2 solutions). So, what are the main advantages?

Work on the business logic of you projects

The first reason to use a public framework (not developed by you) is that you can spend more, and better, time on the business logic of your projects. You don’t have to work on the framework, just on your projects. You know that 99% of our (as developers) needs and problems (projects related) were just solved by others. Tools provided in a lot of frameworks will help you to solve those problems, often in a good way thank to the community contribute.

Don’t reinvent the wheel

Many times we work on similar problems. It’s not a good practice to loose time reinventing the wheel on every project. We can use this time to do better things and add real value to the project. Automate repetitive tasks it’s essential and this should be a priority for all developers.

Documentation

Documentation is one of the most important feature of a successfull product. A good framework must have a good documetation indipendently from the complexity of the framework itself. Looking at a framework developed internally it’s easy to have no documentation because you haven’t had time to do that. You spent a lot of time building your framework, you can’t spend other to document it. If you are the only developer using that framework the problem is little, but what happens when another developer joins the team? Things starts to be harder…

Look for skilled developers

You need to look for a new developer to join the team. If you use a non public framework you can’t search skilled developers about that. If you use a public framework you can search skilled people in the framework you use for your projects. The new developer starts to be productive in a faster way because he doesn’t have to study a new framework without documentation. So you can see that documentation is important.

Do you want to add other advantages to complete this short list?

• Practical SVN for PHP Developers
• Svn Best Practices
• PHP Deployment With SVN
• Subversion – Ubuntu documentation

Have a good reading! And if you want to contribute to this list add your suggest in the comments below. Thanks.

If you find some typos or something that you can say in a different way please contact me.