Sure, though I've also read people in your position are better at building apps with JS if they're new to it because things like PHP are completely different in how you start growing an app (classical vs prototypal inheritance) not to mention that if you also do PHP instead of just straight JS you're getting used to and learning 2 languages that are completely different in how you code. In either case you're right you have to learn JS anyway, here are the best resources after codeacademy basics stuff:

JavaScript: The Definitive Guide: Activate Your Web Pages (Definitive Guides):

http://www.amazon.com/JavaScript-Definitive-Guide-Activate-Guides/dp/0596805527/

JavaScript: The Good Parts:

http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742/

Programming JavaScript Applications: Robust Web Architecture with Node, HTML5, and Modern JS Libraries:

http://www.amazon.com/Programming-JavaScript-Applications-Architecture-Libraries/dp/1491950293/

A cool talk from last year of the Fluent conference (and the author of that last book) explaining how different something like PHP and JavaScript are and why JS doesn't deserve the bad rap it used to get (He's a pretty cool guy from Adobe and I got to talk to him last week about all of these things we're talking about right now and where web development is heading, and why JS as a single language for the web can work even better):

http://www.youtube.com/watch?v=lKCCZTUx0sI

This was a really cool overview on JS today, and you get to see Unreal Tournament and the Unreal 4 engine run in a web browser:

http://www.youtube.com/watch?v=aZqhRICne_M

When I said "I can see how maybe they could be useless to you.", that's because I instantly know what kind of programmer you were. You're a low level guy.

I have a copy of "Algorithms in a Nutshell" (http://www.amazon.com/Algorithms-Nutshell-In-OReilly/dp/059651624X) but I never finished it. My favorit programming book may be "Patterns of Enterprise Application Architecture" (http://www.amazon.com/Patterns-Enterprise-Application-Architecture-Martin/dp/0321127420). Neither of these books are language specific, but I don't think they could be further apart in every way. Both are very valuable and I appreciate that they both exist.

There is a good number of reasons that you should maximize your use of the built-in PHP functions (http://webandphp.com/5reasonstomaximizeyouruseofPHP%E2%80%99sbuiltinfeatures). My book is an attempt to come up with a system that will help you learn all of the built-in PHP functions by giving a realistic use case that could be applied in your everyday work.

Being a PHP programmer, it is much more useful to know what functions PHP has for array sorting, than it is to know how to implement array sorting in PHP code.

I learnt by reading PHP and MySQL for Dynamic Web Sites
It is written for PHP 5.6 so it is outdated (unless they have updated it since)


The follow on book is also worth reading. It helped me understand how to use OOP in PHP

PHP Advanced and Object-Oriented Programming

When I read these books they were written for PHP 5.6. PHP is now on 7.2 and there has been a lot of features since then. It'll still help you get a practical grasp of PHP.

As cout112 suggested, PHP the right way is a really good resource too. I highly recommend going through some of the pages.

Best of luck with the new job.

> Any tutorials on this or the best practices in using PHP in a good programming structure with OOP.

There is no good books for PHP, but you can try to read something like this:

• https://www.amazon.com/dp/0672330164/?tag=stackoverfl08-20
  
• https://www.amazon.com/dp/0136300707/?tag=stackoverfl08-20
  
  > to be changeable in the future and so I can use the same code for other projects.
  
  Why can't we just change code? Because we can break it. Why we break code? Because of high coupling. How can we reduce it? We can think more on how to split code over independent units. How can we achieve that? Write more unit tests which will line boundaries of your units. TDD for example may help you alot. This also allow you to experiment with code much more often.

In the real Command Pattern, commands do have an execute method.

This excellent book by Uncle Bob devotes a great deal of time to that pattern if you'd like to learn more about it:

https://www.amazon.com/Agile-Principles-Patterns-Practices-C/dp/0131857258

You are totally wrong with this. To build up a community while creating an open source project, its better/easier to keep people updated with what I'm doing while I'm working on it. This will build up an elite community around the project and when it will be stable, some developers will already like to contribute to it, if the project is good enough.

There is various books related to that topic including the 100$ startup.

Also, this project is separated in multiple projects because they are multiple projects. For example, it will be possible to use the sharding project without using everything else. Same goes for each of these 5 sub-projects.

By fragmenting the big project in smaller one, it makes each part easy to use separately, which make the code highly re-usable, scalable and maintainable.

Symfony2 and Doctrine also tries to separate packages. For example, I used the Annotation package of Doctrine inside my own project. This was possible because they made it a separate package at first.

Hope this makes sense.

Every quality software should have tests. So...

Read the unit tests / features tests first. Those will show you how a specific piece of the code works.

Also:

1. Play with composer packages.
   
2. Learn about PHP SPL
   
3. Learn about design patterns and beyond
   
4. Learn TDD, setup PHPUnit, Behat, Mink, PHPSpec
   
5. Read PHP The Right Way
   
6. Learn about clean code, EBI, DCI and how to put MVC on a shorter leash here: http://ikke.info/clean_code.html and here http://ikke.info/todo.txt and check out the #cleancode IRC channel on freenode
   
7. Read a couple of books like: PHP Objects, Patterns and Practice or Code Complete or Clean Code or The Pragmatic Programmer or The Mythical Man-Month
   
8. Start an open-source project or contribute to one
   
   
   There are a lot to learn and if you really like programming you will never stop learning.
   
   

Actually i would suggest you to start learning OOP and maybe investigate the MVC design pattern, since those are both of subjects which average CodeIgniter user will be quite inexperienced in. While you might keep on "learning" frameworks, it is much more important to actually learn programming.

Here are few lecture that might help you with it:

• [Inheritance, Polymorphism, & Testing][2]
  
• [Advanced OO Patterns][3] ([slides][4])
  
• [Unit Testing][5]
  
• [The Principles of Agile Design][6]
  
• [Global State and Singletons][7]
  
• [Don't Look For Things!][8]
  
• [Beyond Frameworks][9] ([slide][10])
  
• [Agility and Quality][11] ([slides][12])
  
• [Clean Code I: Arguments][13]
  
• [Clean Code III: Functions][14]
  
  This should give you some overview of the subject .. yeah, its a lot. But is suspect that you will prefer videos over books. Otherwise, some reading materials:
  
  
• [PHP Object-Oriented Solutions][15]
  
• [Design Patterns Explained][16]
  
• Patterns of Enterprise Application Architecture
  
  You will notice that a lot of materials are language-agnostic. That's because the theory, for class-based object oriented languages, is the same.
  
  Also I would recommend for you to look into following concepts of object oriented programming:
  
  
• SOLID principles
  
• Law of Demeter
  
• Separation of concerns
  
• Inversion of control
  
  
  
  [2]: http://www.youtube.com/watch?v=4F72VULWFvc
  [3]: https://vimeo.com/21173483
  [4]: http://qafoo.com/talks/11_02_phpuk_advanced_oo_patterns.pdf
  [5]: http://www.youtube.com/watch?v=wEhu57pih5w
  [6]: http://www.infoq.com/presentations/principles-agile-oo-design
  [7]: http://www.youtube.com/watch?v=-FRm3VPhseI
  [8]: http://www.youtube.com/watch?v=RlfLCWKxHJ0
  [9]: https://vimeo.com/21145583
  [10]: http://www.slideshare.net/stuartherbert/beyond-frameworks
  [11]: https://vimeo.com/20610390
  [12]: http://www.slideshare.net/sebastian_bergmann/agility-and-quality-php-uk-2011
  [13]: https://vimeo.com/13439458
  [14]: https://vimeo.com/12643301
  [15]: http://www.amazon.com/PHP-Object-Oriented-Solutions-David-Powers/dp/1430210117
  [16]: http://www.amazon.com/Design-Patterns-Explained-Perspective-Object-Oriented/dp/0201715945
  

PHP Objects, Patterns and Practice - Expert's Voice in Open Source -

I am only on page 65 and I got a good grasped of OOP.


Building PHP Applications with Symfony, CakePHP, and Zend Framework

Another great book. Especially if you havent decided which framework to go with.

+1 on those books. Also:

• Building Microservices -> a fast introduction to Microservices, talks a lot about how to split concerns - touching a lot of DDD concepts - on a big app
  
• Enterprise Integration Patterns -> not all of it, but if you move to an event-based app it helps a lot
  
• Domain-Driven Design in PHP -> still only half the book in Leanpub, but really promising
  

Thanks for the quick reply :) I will try to give it a read.

Just to be sure these are the books you suggested:

• Pattern-Oriented Software Architecture, A System of Patterns
  
• Component Based Development for enterprise level applications

I have included some links for more information about myself in the original post.

To have a better idea of the type of person I am these are the books within my arms reach right now:

Design Patterns: Elements of Reusable Object-Oriented Software

[Refactoring: Improving the Design of Existing Code](
http://www.amazon.ca/gp/product/0201485672)

The Mythical Man-Month

Along with some other ~50 similar books I've read.

Intro to PHP/MySQL: http://www.amazon.com/Head-First-MySQL-Lynn-Beighley/dp/0596006306

More advanced SQL knowledge: http://www.amazon.com/Head-First-SQL-Brain-Learners/dp/0596526849

More advanced PHP knowledge: http://www.amazon.com/PHP-Object-Oriented-Solutions-David-Powers/dp/1430210117

Go in that order, you'll be very comfortable in a few months.

Hey, I briefed over some of the comments here, and while I feel a number of them are useful and necessary, I think you need an actual hard copy book to start with, rather than jumping right the hell into the manuals.

The book I started with, with absolute minimal programming experience (just some C++ classes in high school), is Larry Ullman's PHP book. I started on the second edition, and it was everything I needed to get started programming with PHP and making dynamic applications. It should cover basics of MySQL and top the book off with regular expressions, which are absolutely necessary to any serious web developer, and he makes everything feel very accessible.

After some months of that and programming, you would be ready to enhance your skills, and his follow up Advanced PHP book covers a lot of interesting and esoteric areas. It might be more than you need, but it does start off with some practical chapters in OOP and classes.

In-between the two, he wrote a MySQL and PHP combination book that sort of acts as a stepping stone between the beginner's book and the advanced book, and it might actually be the most you need to program in PHP, but I found the Advanced book handy to use, and the first book I linked you was my personal guide and reference for about a year and a half as I grew in my skill set.

I read this when I was studying for my exams last year and found it quite good.

Chris Shifflett's book is very good: http://www.amazon.com/Essential-PHP-Security-Chris-Shiflett/dp/059600656X

I think this is often due to developers not understanding what clean code is or how to motivate it in instances where it will take significantly more time to write than throw-away code. I absolutely love Uncle Bob's Clean Code book, but even more than that, his Clean Coder book talks about the skills to be a professional developer. Skills which include being able to say "no" to poor management decisions and communicate and code professionally.

If the reader must choose between the two, I would recommend the latter. And I do, to all junior developers who ask...

Books

• Clean Code
  
  
• Practical Object-Oriented Design in Ruby - same concepts apply to PHP
  
  
• Modern PHP
  
  
• PHP The Right Way
  
  
• PHP Objects Patterns and Practice
  
  
• Patterns of Enterprise Application Architecture
  
  
• Design Patterns (Gang of Four)
  
  
• Domain Driven Design by Eric Evans
  
  

  Stuff to watch
  

  
  

• https://github.com/phptodayorg/php-must-watch
  
  
  

  Blogs
  

  
  

• 8th Light - lots of stuff from Bob Martin here
  
• Mathias Verraes
  
• Anthony Ferrara
  
• Phil Sturgeon
  
  

  Other resources
  

  
  

• If you want to get into Laravel (and you should get into Laravel), get a Laracasts subscription

Scalable Internet Architectures by Theo Schlossnagle. He was my boss at OmniTI and knows his stuff.

This is completely unrelated to PHP. What is this post doing here?

• Don't Make Me Think by Steve Krug.
  
  
• Rocket Surgery Made Easy by Steve Krug.
  
  
• About Face 3 by Alan Cooper.

https://www.amazon.com/PHP-Programming-Cookbook-Doug-Bierer-ebook/dp/B01BU1B7CC

https://www.amazon.com/Modular-Programming-PHP-Branko-Ajzele/dp/1786462958/ref=sr_1_1?s=books&ie=UTF8&qid=1484089887&sr=1-1&keywords=modular+programming+with+php+7

Both of them are quite in-depth,well written.Second one is about design patterns AND the second half has a Symfony shop with detailed explanations.Not the usual lukewarm,boring, yet another PHP book.