PHP Laminas / Zend Framework - On-Going Development
Budget: $15 – $25 USD
We're searching for a skilled developer familiar with ZF2 and Laminas, with a strong understanding of design patterns. This person will also enjoy technology, be familiar with Linux, structured data and be detail oriented. We support a wide range of solutions and good written skills are required to keep development facing documentation current.
We use Jira, Confluence, and Git.
The typical day is both project based work and support requests. We review our tasks, open up related documentation, and being our coding/development. As we are coding, we are updating the associated documentation aligned to the project. This is a master technical document, change log, and SRS/WBS, and related documentation.
An example may be this:
Task - Add ability for system to send email on order status change
Associated SRS - The customer needs to know when an order has shipped or been placed on hold.
WBS - Add a new module to handle email and create a service that can be called from the order controller. This should send an email to the account owner when an order is switched to the held or shipped status.
Prevent duplicate emails from sending in the event they switch the order status multiple times.
Master Technical Document.
EmailModule - Added a emailController that will create an email, insert it into queue, modify the queue, cancel an email, and schedule an email. Added a CronController that will send emails in queue.
Model - Added emailQueueEntity and emailQueueTable. The table has needed CRUD functions.
Service - Created a service that can be called from any controller in the project and use functions within the model.
Changelog - 9/23/2021 - Created email module and service. Jira Task ABC-143
Above is just an example of what we do when we're developing to keep documentation current and allow other developers and project managers to keep track of what has been done without needing to review code. This also helps us in the future because we can quickly review documentation and understand the project.
We use Jira, Confluence, and Git.
The typical day is both project based work and support requests. We review our tasks, open up related documentation, and being our coding/development. As we are coding, we are updating the associated documentation aligned to the project. This is a master technical document, change log, and SRS/WBS, and related documentation.
An example may be this:
Task - Add ability for system to send email on order status change
Associated SRS - The customer needs to know when an order has shipped or been placed on hold.
WBS - Add a new module to handle email and create a service that can be called from the order controller. This should send an email to the account owner when an order is switched to the held or shipped status.
Prevent duplicate emails from sending in the event they switch the order status multiple times.
Master Technical Document.
EmailModule - Added a emailController that will create an email, insert it into queue, modify the queue, cancel an email, and schedule an email. Added a CronController that will send emails in queue.
Model - Added emailQueueEntity and emailQueueTable. The table has needed CRUD functions.
Service - Created a service that can be called from any controller in the project and use functions within the model.
Changelog - 9/23/2021 - Created email module and service. Jira Task ABC-143
Above is just an example of what we do when we're developing to keep documentation current and allow other developers and project managers to keep track of what has been done without needing to review code. This also helps us in the future because we can quickly review documentation and understand the project.