On the first Wednesday of each month, at 11am PST, I organize a webinar. For about an hour we talk about software development, object-oriented programming and project management.
February 1, 2017: How to Deal With Conflicts in a Software Team We'll discuss what is the most effective attitude towards conflicts in a software team, which is aiming for higher quality. The discussion will be based on this blog post: How Much Do You Love Conflict?
January 11, 2017: Gradients of Immutability We discussed what immutability really was, with a few example in Java and EO (new language we're developing now). The discussion was based on this blog post: Gradients of Immutability.
December 7, 2016: Who Is a Project Manager? We discussed what was the role of a project manager in a software project and how it was different from other roles. The discussion was based on this article: Who Is a Project Manager?.
September 7, 2016: Printers Instead of Getters in OOP Getters are evil in OOP, but what is the alternative? Printers is the way to go. The discussion was based on this article: Printers Instead of Getters.
August 3, 2016: The Philosophy of Bugs We discussed what bugs were for, how they must be understood by the management, how many of them we should expect to find and what is in general the right philosophy of bug tracking. This article were mentioned: When Do You Stop Testing?.
July 7, 2016: Smart Classes and Functionality-Poor Interfaces We discussed why
java.io.InputStream design was wrong, what Smart-Classes are for and why interfaces must be functionality poor. The discussion was based on this blog post: Why
InputStream Design Is Wrong
June 1, 2016: How to Cut Corners and Stay Cool we'll discuss how to cut corners and stay cool and how to turn chaos into discipline. The discussion will be based on these articles: How to Cut Corners and Stay Cool and It's Not a School!.
May 4, 2016: Java Annotations Are a Big Mistake We discussed why Java annotations were actually a mistake in object-oriented programming and how they motivated us to break object's consistency and turn it into a data bag. The discussion was based on this article: Java Annotations Are a Big Mistake.
April 13, 2016: Who is Software Architect? Software architect is responsible for failures and is powerful enough to make and overrule any decision. But that is not it. We also talked about delegation of responsibility and micromanagement. Mostly, this webinar summarized what these articles are talking about: Are You a Micromanager? and Who Is Software Architect?.
March 2, 2016 Takes, Java Web Framework, Intro This was be a very practical Java coding webinar. We created jare.io, a web system, using Takes Framework, immutable objects and the best practices of pure fanatical object-oriented programming. We used this blog post as a guidance: Java Web App Architecture In Takes Framework
February 3, 2016 Daily Stand-Up Meetings Are Evil We talked about famous daily meetings and why they were actually a bad idea in a properly managed and disciplined software project. The discussion was based on this post: Daily Stand-Up Meetings Are a Good Tool for a Bad Manager
January 6, 2016 Why ORM is an Anti-Pattern? We discussed why Object-Relational Mapping (ORM) was actually an anti-pattern and its usage must be replaced with SQL-speaking objects. The discussion was based on this blog post: ORM Is an Offensive Anti-Pattern.
December 1, 2015 Dependency Injection Container is a Bad Idea We discussed why Dependency Injection (DI) containers were not a good idea in object-oriented programming and what they should be replaced with. The discussion was mostly be based on DI Containers are Code Polluters.
November 4, 2015 What Fake Objects Are For? We discussed the role of fake objects and the importance of their existence in every object-oriented library. The discussion was based on this post: Built-in Fake Objects.
October 7, 2015 A Few Thoughts About Constructors in OOP We discussed the role of constructors in OOP and a few best practices for their design, including primary vs secondary and code-free design. The discussion was based on these articles: There Can Be Only One Primary Constructor and Constructors Must Be Code-Free.
September 2, 2015 What's Wrong About Utility Classes? We discussed a very common design pattern known as "Utility Class" and its negative effects on the quality of design in object-oriented world. The discussion was be based on this post: OOP Alternative to Utility Classes.
August 5, 2015 Don't Create Objects That End With -ER We talked about class naming principles and a very typical problem of misusing "-er" suffix for them, for example in Managers, Observers, Controllers, Filters, Helpers, etc. The discussion was based on this post: Don't Create Objects That End With -ER.
July 1, 2015. Why Getters-and-Setters Is An Anti-Pattern? We discussed why Getters-and-Setters, a very popular design pattern in object oriented languages, is instead an anti-pattern and must be avoided. The discussion was be based on this blog post: Getters/Setters. Evil. Period.
June 3, 2015. What's wrong about NULL in OOP? This webinar was about NULL references/pointers in object-oriented programming and their negative effect on the entire design of your application. The webinar was mostly motivated by this post: Why NULL is Bad?. My attitude towards NULL references is very negative, so be prepared for an OOP "radicalism" there.
May 6, 2015. Immutable Objects vs Common Sense. The second webinar, about immutable objects and their pros and cons in an object-oriented programming. The webinar was based on this post: Immutable Objects Are Not Dumb. I made a few slides for this webinar, to illustrate my point better. There were some interesting questions asked too.
Apr 8, 2015. Objects vs Static Methods. The first webinar, where we discussed the difference between static methods and objects in object-oriented languages, like Java. Of course, I'm in favor of objects :) The webinar is basically motivated by this earlier post: Composable Decorators vs. Imperative Utility Methods. It took a bit longer than an hour.