A technologist currently working in eHealth, loves to code, grow new developers and solve new problems leveraging old technology approaches.
I love opensource & knowledge sharing
Location
Kampala, Uganda
Education
BSc Civil Engineering
Work
Problem Solver and Solutions Strategist at Styx Technology Group
I am have maintained a legacy Laravel based solution (5.5), looking to start a green field project with Laravel 6, had a Symfony 4.1 solution and lost on which framework to use for a side project that I have been putting off for too long.
My heart is with API Platform (based on Symfony), but Laravel currently seems to be doing all the right things with developer experiences simplifying usages.
You are not crazy to leverage frameworks, because the more years you work with tech, the less code you want to write (since you will need to test, maintain and evolve it), as you get slower and have more responsibilities
The maintenance fees approach vary:
Support hours for keeping the system running (monthly and/or annual)
Cost updates as part of evolution of the system with new features
Not hide it in hosting fees as that gets seen by outsiders - so better not have questions in that area (so its generally a pass through cost with markup to cover hosting management time)
Working with API platform on a real project was really painful for us. We got rid of it completely in the latest version of our api. (Still running on the previous version).
A technologist currently working in eHealth, loves to code, grow new developers and solve new problems leveraging old technology approaches.
I love opensource & knowledge sharing
Location
Kampala, Uganda
Education
BSc Civil Engineering
Work
Problem Solver and Solutions Strategist at Styx Technology Group
I am have maintained a legacy Laravel based solution (5.5), looking to start a green field project with Laravel 6, had a Symfony 4.1 solution and lost on which framework to use for a side project that I have been putting off for too long.
My heart is with API Platform (based on Symfony), but Laravel currently seems to be doing all the right things with developer experiences simplifying usages.
You are not crazy to leverage frameworks, because the more years you work with tech, the less code you want to write (since you will need to test, maintain and evolve it), as you get slower and have more responsibilities
The maintenance fees approach vary:
API Platform (based on Symfony) is the best thing that happened to me this year. I would be putting up a post with my experience on it soon 😎
Working with API platform on a real project was really painful for us. We got rid of it completely in the latest version of our api. (Still running on the previous version).
What were the blockers that you faced? How did it not fulfil your needs? I am keen to learn as I keep an eye on it for a future API driven project
Oh I was never going to write what a framework does myself. Rather, just use a few stable packages for the small stuff.
I did the build my own framework thing 10 years ago. It's still in use. All this research is me moving away from the internal framework. :D
Great tips!