I'm working as a free software architect and developer since 2011. 

Software architect and developer

I have used the clean architecture in more than 10 projects for several different customer since 2015 and also used it before even I didn't know that what I did was called the clean architecture.
I also created an example implementation on github https://github.com/link-intersystems/clean-architecture-example.

Since 2011 I work as an independent software developer and coach teams about clean code.

I earned the "Sun Certified Programmer For The Java 2 Platform 1.4" in 2003. Since then I'm developing enterprise applications with Java. Either JEE or Spring Hibernate. I'm also experienced in developing rich client application with eclipse RCP or just based on pure Java Swing.

Since 2006 I focus on code quality, writing clean code, deal with software design and architecture. A lot of software is not well structured or must be re-structured to fulfill new requirements. To refactor code is one central skill that a developer must have to gurantee quality and maintainability.

I started developing Eclipse plug-ins in 2005 during my diploma theisis. Since then I usually developed plugins to create tools for development teams that ease and support the development. In this context I also developed Eclipse RCP applications.

I first came in touch with maven during a project in 2007. My task was to migrate the build process from ANT to Maven. To achieve this I also had to implement maven plug-ins, so called mojos. Since then I'm using Maven as my favorite build tool.

I developed a lot of maven plug-ins for my customers and even for myself. Some can be found at
- https://github.com/link-intersystems/maven

In 2015 I entered a new project and one of the first tasks was to migrate the source control management system from subversion to git. The subversion repository had a very long history of about 10 years. During the migration process I also had to remove build artifacts from the history, especially build result artifacts. At this time I dived into the internals of git, wrote a blog and even created a small swing app to ease such tasks. Take a look at my blogs 

- https://www.link-intersystems.com/blog/category/tools/git/
and the application
- https://github.com/link-intersystems/GitDirStat

Since then git is my favorit source control management and I even use it as a database for applications some times.

Learning the internals of git also helped my to understand other concepts faster like a blockchain, because git is a blockchain under the hood. It is a distributed, revision-safe file system.

I really like gerrit. It is one of the best code review tools that integrate with git. Some time ago I also configured gerrit to let the build server jenkins participate in the review process. In this case jenkins gets notified when a new commit is pushed to gerrit, it builds that commit and only if the build and tests are successful it gives a verify vote. Then only positive tested code can be integrated into the master. This increases the code quality and other developers can be sure that the master is always buildable and tested. Gerrit is a really great tool.

Personal details

René L.

Summary

Technical skills

Work Experience