Don't build your own framework | Dev Diaries

preview_player
Показать описание
I used to work at a place that built and maintained its own framework. It all worked fine, until the day it didn't.

Dev Diaries is a series where I talk about my own real-life experiences. This story happened almost 10 years ago at one of my previous jobs, but it has always stuck with me.

Music by Kevin Macleod — Night on the Docks
Рекомендации по теме
Комментарии
Автор

I was searching for how to build a framework 😂😂

safalstha-dd
Автор

If you do build and maintain an in-house framework, make sure you have good tests and keep all projects up-to-date.
We do use an in-house framework since 2015 (PHP 7.0 release). We use semantic versioning scheme, in-house composer registry, and keep all projects's dependencies up to date (forced by CI).
Of course we had bugs. All builds are automatic though, so it takes us only about half a day to update all sites and services to the latest framework version.

ThomasIngolstadt
Автор

I'm glad i disregarded this advice and built my own framework anyway. It came out great and i'm glad i did it!

What you're explaining is bad design. If you are bad at design, i agree, don't build your own framework. But if you are good at it and you think you have a better idea, please do it.

neptronix
Автор

And you think widely used libraries with large communities don't produce bugs? log4j anyone? Everybody makes mistakes, sometimes they're bad. Don't question everything when you do everyday mistakes.

ifox
Автор

That's a terrible advice backed up by corporate crap that doesn't apply when you are doing the framework as you would like and not as someone else might want that's on a higher pay-grade.
Have a good test-suite, do beta-testing and overall - build a community behind it beforehand, even on Twitter or something. It's not going to be an effective beta testing if there's only 5 people trying it out on their leisure. Same cannot be said about corporate "cooking" - mostly, proprietary code that doesn't get beta releases for larger audience to test, it's like shot in the dark.
Building in public cannot be compared with inside frameworks.

ward