Talk: Clean Code
At the TYPO3 Barcamp in Vienna I spoke about Clean Code. What are the symptoms, cure and vaccination for Bad Code?
At the TYPO3 Barcamp in Vienna I spoke about Clean Code. What are the symptoms, cure and vaccination for Bad Code?
Developing software is challenging. Many workflows are simply too complicated and not intuitive enough. Individuals and interaction between people are hardly at the center of interest any longer. It seems as if the perfect process does not allow decisions of the involved individuals anymore. Is this still as intended by the Agile Manifesto? In this article I would like to introduce a simple agile development process that is built with humans in mind.
Ackee is an analytics tool that captures statistics about website visits. Unlike other applications in this area, Ackee does not use cookies at all. With the help of the provided Docker image, the tool can easily be installed on a self-hosted Dokku server.
One of the most important principles of software development is the Separation of Concerns, according to which different concerns are to take place in separate sections of a program. The creation of objects and the execution of business logic are two different concerns. The Dependency Injection design pattern helps to separate the two concerns.
There are many code styles. Is indented with tabs or with spaces? How many spaces? – A uniform code style facilitates the work in the team, but this is made more difficult by incorrect default settings in the editor. The EditorConfig offers help when dealing with different code styles.
Personally I like to look at the commit history of different projects. Often I find that the commit messages provide only little information about the actual changes in the code. Good commit messages help in the review process, when creating changelogs, to be capable of tracking the changes to the source code made by other software developers. This means that good commit messages show whether you are a team player or not.