Hi there!

I've been a web developer for quite a while now and have experimented with both front and back-end development. However, recently I've been focusing more on back-end development.

I came across an interesting article on Habre that made me realize the benefits of using popular tools and frameworks with a large community instead of creating everything from scratch. This led me to "modernize" my approach to development.

Firstly, I decided to switch from self-written frameworks to Laravel. However, this required PHP version 5.6 or later which I had never worked with before. So, I installed nginx and the latest PHP version and began working with Composer.

However, I found the process of installing and using Composer confusing and overwhelming as it offered many different tools and frameworks to work with. This left me wondering if it was really necessary to know and use everything, and if it will take more time than creating code from scratch.

Overall, the article helped me to rethink my approach to development and consider using popular tools to improve efficiency and productivity.

A compositor allows for easy integration of third-party components and libraries by automatically downloading and registering them in the vendor folder through simple commands. This eliminates the need for manual installation, which can be tedious and time-consuming, especially when multiple libraries need to be connected.
Popular frameworks such as Laravel use this utility to obtain components from other repositories, simplifying installation and reducing red tape. Despite its importance, detailed information on syntax and usage can be found on the official website for those interested in learning more.

Do you have any questions about using a compositor for your own projects?

As you have already explained the concept of composer to you, let me help you with your list:

1) The transition is fully transparent. The key is to examine more contemporary projects carefully.

2) My suggestion would be to read the RFC and experiment with projects and demos.
 
3) Regarding arrays, I meant to refer to short syntax: [] and not instead.

4) To catch up, consider abandoning mcrypt and resort to built-in password solutions. You may refer to: php.net/manual/ru/book.password.php.

5-6) I highly recommend git flow, which I find very useful for everyday use.

Blank line.

8-10) Be cautious when selecting tools. Personally, I prefer netbeans+redmine (with a plethora of plugins)+jenkins+bash. However, all of this necessitates a gradual and subtle integration into your workflow.

11-12) It seems like you have learned everything on your own...

13-14) Though experience with specific implementations is helpful, it is better to possess an in-depth theoretical understanding of databases. But I recommend using postgresql as the default one.

There's no need to learn anything! You can easily whip up your own code for a bowl of noodles with just the "current level." So why bother?
It was tough in mid-2015 if you had no knowledge of vcs.
However, it's become feasible (and at times required) to carry on without migrations and instead rely on backups.

Making the switch from self-written frameworks to Laravel is a positive step, as it can save time and effort by leveraging the features and support of a widely-used framework.

Regarding your concerns about Composer, it's important to remember that while it offers many different tools and frameworks, you don't have to know or use everything. Composer is primarily a dependency manager for PHP, and it allows you to easily incorporate third-party packages and libraries into your project. This can significantly speed up development by allowing you to leverage existing solutions rather than reinventing the wheel.

As you continue to work with Composer, I recommend focusing on learning how to manage dependencies effectively and efficiently. You can start by understanding how to create and manage a `composer.json` file for your project, and how to use Composer's commands to install, update, and remove packages. Additionally, familiarizing yourself with popular packages and libraries within the PHP ecosystem can help you make informed decisions about which tools to incorporate into your projects.

In terms of time investment, while there may be an initial learning curve with adopting new tools and frameworks, the long-term benefits typically outweigh the upfront time investment. By leveraging well-maintained and widely-supported tools like Laravel and Composer, you can benefit from community contributions, bug fixes, and ongoing improvements, ultimately saving time and effort in the long run.

Remember that it's okay to start small and gradually expand your knowledge and usage of these tools over time. Focus on the specific features and functionality that can enhance your projects, and don't feel pressured to adopt everything at once.

Embracing popular tools and frameworks with a large community can provide valuable resources, support, and efficiencies that contribute to your success as a developer.


Transitioning to modern web development can be an exciting and rewarding journey. Embracing popular tools and frameworks, such as Laravel for back-end development and Composer for managing dependencies, can provide numerous benefits, including increased productivity and access to a supportive community.

As you continue your transition, consider the following steps:

1. Learning Curve: Understand that there may be an initial learning curve when adopting new tools and frameworks. Take the time to familiarize yourself with the basics of Laravel, Composer, and any other relevant technologies. Start by exploring the official dоcumentation, tutorials, and online resources.

2. Small Projects: Consider starting with smaller projects or components within larger projects to experiment with the new tools and frameworks. This approach allows you to gain hands-on experience without feeling overwhelmed by the scale of a full migration.

3. Community Involvement: Engage with the developer community through forums, social media, and local meetups. Sharing experiences, asking questions, and learning from others' experiences can be immensely valuable as you navigate the transition.

4. Continuous Learning: Keep an open mind and embrace continuous learning. Modern web development is evolving rapidly, and staying updated on best practices, new features, and emerging technologies is essential for long-term success.

5. Incremental Adoption: Rather than completely overhauling your existing workflow, consider incrementally adopting new tools and practices. Identify specific pain points in your current process and evaluate how the new tools can address them.

6. Seek Feedback: Once you've integrated new tools into your workflow, seek feedback from colleagues or peers. Their insights can help you identify areas for improvement and validate the benefits of your modernization efforts.