The Art Of Clean Code by Victor Rentea

Whatever paradigm, language, technology stack or devops strategy is used, we will always write code. And that code will need to be understood, maintained and evolved by various developers for many years, hopefully. It will be read 10x more time than it took to write it!

Then, tell me, how do you write your code ?

Stop rushing, and start writing professional code. You'll need to learn to introspect your design, to make it express your thoughts in code. It may take years of practice to reach that point, but the path starts with some basic guidelines and 'code smells' that you ought to know, along with a core toolset of refactoring techniques.

As simple as some of these might seem, they will become the starting point of a lot of discussions about core principles of good software design, such as DRY, SRP, DIP, and KISS. Come and enjoy an entertaining, tangible presentation of key concepts in Clean Code, that will allow you to easily coach others, back at work.

Looking forward to share my passion with you: writing expressive code that is a pleasure to work with.

PS: In the end, let's talk a bit about writing clean code using Java8 lambdas/Streams, shall we? :)

Victor Rentea (Java Craftsman)
Sr. Engineer & Technical Lead at IBM Romania.
Independent Trainer & Coach.

I worked hard on backend systems over the last 10 years, solving technical challenges of a broad range of enterprise Java applications as a developer, lead and consultant. 4 years ago, after I had devoured Uncle Bob’s Clean Code book, I joined the ‘coding craftsmanship’ move.

Of course, soon after I started preaching about it as an independent trainer/coach. This Clean Code, TDD, Pair Programming stuff it’s just too fun too keep it for oneself. For hundreds of days I’ve spread the word to more than 1000 trainees in all kinds of settings (even faculty lectures), usually bundled together with other training modules that I’ve gradually developed, such as Spring, JavaEE, JPA, Design Patterns, and the like. You can find the entire curricula on my website.

My extensive experience as a trainer allowed me to refine a very entertaining presentation style, spiced with jokes, non-IT-world analogies, and examples that is able to make any developer profile understand even the most advanced design discussions.

Recently however, I realized how much I enjoy meeting smarter people, so I’ve started talking at international conferences such as Devoxx MA and VoxxedDays Bucharest and Belgrade.

[john_rambo_]

Excellent1 He is the next Uncle Bob for sure. :)

[ak-otwn]

41:52 is the most "non-understood" part of the talk. So what is better to use in this case? The method in left or the stateful class on right?

[Fabs]

Great talk, concise and to the point.

[LivenLove]

regarding 41:57 having a class instead of method is stateful, which has its own disadvantages..what should be the approach to reactor in such case?? extracting new methods is also not a solution due to multiple returns. I did not get what is the ideal way to refactor such long methods

[stevenchen]

English is my second language. I have hard time to understand his accent. but Professor Posnett asked to watch, nightmare

[cseshivaprasad]

Nice coverage of Bad Code writing and tips to correct it.

[akshaykamathb]

0:46 "The Coding Dojo" by Emily batch

[danflemming]

Don't take the advice to add TODO comments. It's fine when you commit LOCALLY. But don't push it to the repository, remove any TODOs.
Like Uncle Bob said, TODO always actually translates to "never do"

This is now a 3 years old presentation, and maybe Victor has changed his mind.

[dodalovic]

Just buy clean code from Uncle Bob. This guy squashed too much for one session