Progressing to security or OWASP conferences, I’m
treated slightly like a pariah for using scripting languages instead
of Java or .NET. And even within the PHP world, there’s continually
a zend Framework person or 2 that treats me a bit like an
over-excited kid for loving Laravel. Thus over the past year or so
I’ve extremely come to adopt many personal philosophies that puts
everything into perspective.
 |
| Laravel Development Services |
My first philosophy is that you simply should
always select the correct tool for the task, and ne'er attempt to
adhere to a “one solution fits all” mentality. We all need to
create the correct call once it comes to that skills we dedicate our
time and energy into learning and mastering. but there's no tool
which will do everything within the very best way.
My second philosophy is to choose the cleanest,
simplest solution possible. You must continually select less
complicated, light-weight tools, unless your immediate want is for
something larger or heavier. Developers generally get held with the
“yes, but can this scale?” Mentality. Scalability are some things
to always consider, but don’t get held with how your app can
operate if you suddenly become one of biggest companies in the world,
or how it'll stoppage 5-10 years from currently.
If you’re working
on an app which will still exist in its current state in 5-10 years
without being completely re factored, then you have got to ask
yourself if you want to be doing maintenance work for an organization
like this. If you’re selecting tools and frameworks that are
overkill for your use case, then you’re progressing to be
over-engineering your application, wasting way more time, effort, and
money within the process than you'd be refactoring years down the
road. Instead, look at the only tool, then raise yourself if there's
a solid, empirical reason why this tool or framework isn’t
applicable for the task at hand, and if there's, then go the next
step up to one thing larger, and ask yourself constant question.
This leads me to my third philosophy: select tools
and frameworks that match your personality and career goals. If
you're the type of one who gravitates toward what’s acquainted and
comfortable, then select tools that don’t modification much. If
you’re the type of one who needs the protection and predictability
of operating for a large corporation and being part of a awfully
large development team, then select tools which will get you there.
If you want to figure for smaller corporations and startups, or if
you want to figure for digital agencies, then select tools which will
get you there. There are countless different kinds of opportunities
out there, thus select what you would like to be, and go be it.
And finally, my fourth philosophy: don’t take
what any developer says at face price. We’re all distinctive
people, with our own history, our own personalities, our own
experiences, and our own values and goals. We’re all progressing to
have (or develop) our own opinions on things. There’s continually
progressing to be someone who can attempt to crush your spirit for
creating your own decisions and having your own opinions. but one
thing that I’ve encountered a lot is that there are a lot of
developers who have created their minds up concerning frameworks
without really understanding what they’re talking concerning.
Many
times, developers can simply regurgitate somebody else’s opinion
that they’ve detected somewhere else. It’s fine if you have
robust opinions against Laravel or Ruby on Rails, but if you’re
progressing to tell me it’s the incorrect tool for a job, then
you’re progressing to have to be compelled to have some very
specific and empirical reasons. And if you are doing have some
specific examples of why it’s the incorrect tool, then these
reasons should apply on to the task at hand, and to not some
hypothetical project that doesn’t apply to the current situation.
contact us for any query related to Laravel Development Services.
