Opinionated Software Development Frameworks

Karl L Hughes
Jan 28, 2017 · 1 min read

For the past year I’ve been experimenting with frameworks in different languages. I picked up a Rails app for the first time since version 3, I put together a couple Slim apps, I build one microservice in Flask, I’ve been doing a some Express work this month, and we just started using Angular 2 at The Graide Network in addition to CodeIgniter and Laravel.

All these frameworks have different meta-opinions about the role they should play in my code. They range from the very opinionated (Rails, Laravel) to barely being more than a router (Express, Flask). As a developer with several years of experience, I have some of my own opinions, but I must admit I do still enjoy frameworks that have more of their own.

A few reasons I like opinionated frameworks:

  • Relieve me of the cognitive load surrounding how and where I should write code
  • Give me more common ground with other developers using the framework
  • Answers common architectural questions for me.

The downsides are basically just corollaries, and I get that there are pros and cons to each approach. At the end of the day, most web applications have 5–6 core functions that I think every framework should have an opinion about, even if the framework’s paradigm can be broken.

What I’m reading

Written by

Technology team builder, software engineer, and startup enthusiast. CTO at @GraideNetwork and helping technology speakers succeed at @cfp_land.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade