We discuss a compelling case against Object-Oriented programming, is it truly all bad? Plus the cold chills the new Rails Doctrine gives us, the worrying long-term ramifications of progress over stability & convention vs configuration strategy.

Plus a chat about the market position of Jetbrains’ AppCode, blaming Java & unplanning your work and travels.

Thanks to:

• Get Paid to Write for DigitalOcean

Direct Download:

MP3 Audio | OGG Audio | Video | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | Video Feed | Torrent Feed | iTunes Audio | iTunes Video

Become a supporter on Patreon:

Show Notes:

Hoopla

Unplanning your Work and Life

We don’t like planning…seriously we try to do as little of it as possible.

Object Oriented Programming is Bad

View post on imgur.com

• OO Ideal VS Reality
• Is Duke (Java) to blame?
• Too much state is the enemy

Rails Doctrine

• Progress Over Stability
• Response to Rails market position?
• Oh My Omakase

AppCode Review

Feedback

• Wesley