Si se gana la vida desarrollando sitios de WordPress, es muy probable que tenga al menos una familiaridad superficial con PHP y probablemente un poco más.
Quizá pueda personalizar los temas, o incluso crear uno desde cero, y actuar como el administrador adecuado para sus clientes. Aun así, es probable que se encuentre con una ocasión en la que su conjunto de habilidades no coincida con lo que quiere el client. Y eso puede ser un verdadero fastidio. Se ve obligado a subcontratar parte de su proyecto o rechazarlo por completo. Ninguno de los dos escenarios es ideal.
If you are encountering this problem more and more frequently, it might be time to consider adding back-end development to your list of offerings. Regardless, there are a few things to consider before jumping into back-end development.
Developing outside of WordPress
Back-end development means that you will venture outside of the WordPress development territory that you are most familiar with. This can be scary, as venturing into something new is scary. What I'm trying to say is that not everything will look like this. functions.php. And that's incredibly cool, it's always important that you know that.
Una de las cosas más importantes que encontrará se llama Programming Orientada a Objetos (o OOP para abreviar). WordPress no lo usa, pero es viable que desee agregarlo a su lista de servicios debido a su flexibilidad. A la vez, es utilizado por muchos otros frameworks (más sobre eso más adelante).
So for the uninitiated, OOP uses classes to group functions. These functions can be referenced later to put them into action. Instead of writing a series of functions like you do in PHP (an immediate cause and effect approach) with OOP, you have to sit back and think about how your code will be structured before writing a single line. That may sound daunting, but if you have a penchant for organization, you can really excel here.
A great example of this type of development is provided by Jay Hoffman of Torque. Is he Standard WordPress Plugin Template por Tom McFarlin, que ofrece una vista de gran angular de cómo se puede utilizar OOP. Se trata de crear una estructura primero y luego crear lo que be que desees hacer.
When you build with WordPress, it's easy to take a lot of things for granted. It comes equipped to do a lot of things without lifting a finger. Which I am definitely not going to complain about. Regardless, if you venture outside of WordPress, you'll quickly notice that other frameworks don't have everything built in, which means you'll need to create them yourself. What you think will be less bloated than WordPress, but it will a lot of more work. That is only a realistic and fair warning and is not intended to discourage you from trying. I'm just a big believer in approaching things with my eyes wide open.
Front-end development handovers
As a front-end developer, you probably have a lot of experience working with PHP and generally researching the code in WordPress theme files. And while that will undoubtedly help you make the leap into back-end development, preparation is not the only and final, sorry to say.
Seguro, traerá una sólida comprensión de HTML y PHP a la mesa. Con suerte, al mismo tiempo algo de Javascript. Sabrá todo acerca de cómo se combinan todos los bits importantes de código para crear un sitio Web. Y probablemente podrá ver el código en la mayoría de los sitios y entender lo que estaba haciendo el desarrollador, incluso si no puede escribir ese fragmento de código en particular en este momento.
Y puesto que estamos hablando de cosas del lado del server aquí, sería negligente si no mencionara el hecho de que todo el tiempo que ha pasado arreglando sitios de WordPress servirá. Si alguna vez se ha enfrentado a un sitio roto, ¿quién no? – conoce el orden de las operaciones a seguir para solucionarlo. Esta operación paso a paso es algo que se aplica de forma directa al desarrollo de back-end y que probablemente usará de forma regular.
Learn something new
Although there is absolutely no reason why to have To gain access in back-end development, it can be a smart move for many WordPress developers. Why? It all comes down to one key term: diversification.
The more development areas you know, the more jobs you will get. You can consider it as additional tools in your toolbox. All of these skills you accumulate translate directly into dollars and cents in terms of what you can create for your clients. And the fewer times you need to outsource aspects of a project or even reject projects, the better off.
Of course, there is something to be said about being a specialist. That certainly has its advantages at the same time, especially if you are known as the best in the game. But since that title is reserved for a few, it might be a better option to diversify your portfolio and offer a wider range of services so that you can serve a wider variety of clients.
So where should you start? What aspect of backend development should you dive into first? Well, it's your decision. There are many options available, which can be a bit overwhelming. Too many options can sometimes be a burden. Try to think about what aspects of development you are comfortable with right now and what you would like to explore further. If you're already pretty good at PHP, you might want to try Laravel. If you are good with Javascript, Fast it might be a good option to follow.
If you like to live dangerously, immerse yourself in Ruby on Rails. And that's just scratching the surface. There are too many frames out there for me to name here. You just have to know that there is no law that says you must master everything. But if you want become plus competente en el desarrollo de back-end, sus opciones están muy abiertas. Y cada uno dispone de una amplia documentación de apoyo y participación de la comunidad para ayudarlo en cada paso del camino. Y cuanto más aprenda, más descubrirá cómo todos estos marcos pueden funcionar juntos con un target en mente: crear mejores sitios web.
conclusion
It is normal to have doubts at the prospect of continuing with back-end development when you have been working as a front-end WordPress developer for some time. But just because something can be perceived as challenging doesn't mean you should avoid it. In fact, learning new skills can strengthen your service offering and make you a vital developer in high demand for a wider variety of clients.
And at the very least, you should see your front-end development skills improve. The better you understand how things work on the back end, the more adept you will be at writing clean code and anticipating potential problems. Basically, what I'm saying is this: even if you decide not to offer this service to customers, learning it will not hurt.
Do you offer back-end development alongside front-end work? Thinking of expanding your skill set? Or are you happy with where you are? I'd love to hear your thoughts!
