more details ? ツ
A plan, for standing out from the crowd.
The Plan stage covers everything that happens before I start writing code, and it’s where a Project Manager earns their keep. Requirements and feedback are gathered from stakeholders and customers and used to build a product roadmap to guide future development.
Frontend, Accelerate with your team
Frontend development is not meant to be a solo activity.
Are you looking for someone who can help you achieve your business objectives with technical
solutions using React?
While working with me you can expect scalable and future-proof
solutions
that
follow best practices of engineering and deliver a native look and feel for the end-users.
But above all, I'm continuously learning about how to produce cleaner, modern, and standards-compliant code. Leveraging the latest micro-interactions and innovative front-end development techniques is a passion of mine.
I can also help you to solve organisational challenges by combining your deep domain knowledge with human-centred design thinking and best practice UX design methodologies.
Back End Development and APIs
SPA (single page application) is very cool. But JavaScript can also be used on the back end, or server, to build entire web applications. Today, one of the popular ways to build applications is through microservices, which are small, modular applications that work together to form a larger whole. let's build back end apps with Node.js and npm, Express framework, MongoDB and the Mongoose library.
Continuous everything...
Alongside the phases of the DevOps pipeline, you’ll commonly hear people talking about Continous Everything — Continuous Integration, Continuous Delivery, Continuous Deployment and more. This is because continuity is at the core of DevOps, and we tech people love our terminology and buzzwords. However, they do serve a purpose. Let’s break down each of these terms and how they relate to the phases of the pipeline.
-
Integration
One of the biggest difficulties in coordinating a software development team is managing the collaboration of many developers, often in remote locations, on a single codebase. A shared code repository is key to solving this problem, however, there can still be issues in when merging the changes made by multiple people on the same piece of code.
A change made by one developer may impact what somebody else is working on, and the longer that developers wait to integrate their changes back into the shared codebase, the bigger the drift, resulting in more effort and headache in resolving the issues and conflicts.
Continuous integration aligns with the Code and Build phases of the DevOps pipeline. It’s the practice of regularly merging a developer’s code into the centralised codebase and conducting automated testing to ensure that no regressions have been introduced. By merging smaller changes more regularly, these issues become smaller and easier to manage, improving overall productivity and sanity. -
Delivery
Continuous Delivery is an extension of Continuous Integration which automates the process of deploying a new build into production. The goals of Continuous Delivery is to:
-
ㅤ1. Perform automated testing on each new build to verify builds that are ready for release into production, and fail those which are not.
-
ㅤ2. Manage the automatic provisioning and configuration of deployment environments, as well as testing of these environments for stability, performance and security compliance.
-
ㅤ3. Deploy a new release into production when approved and manually triggered by the organisation.
Continuous Delivery aligns with the Test and Release phases of the pipeline, and allows organisations to manually trigger the release of new builds as regularly as they choose.
-
-
Deployment
Continuous Deployment is a more advanced version of Continous Delivery (which makes the reuse of the ‘CD’ abbreviation more acceptable). The goals are the same, but the manual step of approving new releases into production is removed. In a Continuous Deployment model, each build which passes all of the checks and balances of the pipeline are automatically deployed into production.
-
Feedback
CI and CD tend to get the glory when people talk about DevOps, but an equally important factor is Continuous Feedback. The whole point of DevOps is to release new features and fixes as quickly as possible so that the organisation can get feedback from customers, stakeholders and analytics as quickly as possible to make better decisions when designing the next set of changes. The whole point is to achieve a strong Continous Feedback loop to develop a better product.
It’s Continuous Feedback that ties the ends of the loop together, feeding back data and analytics from the Operate and Monitor phases back into the Plan phase to do it all over again.