Articles
Tags: CI, CD, Continuous Integration, Continuous Deployment, Continuous Delivery
CI/CD stands for Continuous Integration and Continuous Deployment or Continuous Delivery. These practices are interconnected but serve different stages in the...
Show full article
CI/CD stands for Continuous Integration and Continuous Deployment or Continuous Delivery. These practices are interconnected but serve different stages in the development lifecycle of applications.
Continuous Integration (CI)
CI is the practice of frequently integrating code changes into a shared repository, ideally several times a day. The main goal of CI is to detect and fix integration errors as quickly as possible. Automated build and test steps are integral parts of CI, ensuring that new code changes do not break the application. CI helps maintain a high-quality codebase and accelerates the development process by providing immediate feedback on the integration status.
Continuous Deployment/Delivery (CD)
CD extends CI by automatically deploying all code changes to a testing or production environment after the build stage. There are two main concepts within CD:
-
Continuous Deployment: This practice goes one step further than continuous delivery. Here, every change that passes all stages of your production pipeline is released to your customers automatically, without explicit approval required for each release. It's a more automated approach, ensuring that new features, fixes, and changes are quickly delivered to users in a seamless manner.
-
Continuous Delivery: This is the practice of automating the entire software release process. The code changes are automatically built, tested, and prepared for a release to production. It enables developers to ensure that their code is always in a deployable state. The final deployment to production often requires manual approval, although the process up to that point is automated.
Relationship and Differences
- CI is a part of CD: CI focuses on the early stage of the development process, where code is integrated and tested. CD builds upon CI, extending the automated pipeline to include automatic deployment to production environments.
- Focus: CI focuses on the integration and testing of code, ensuring compatibility and identifying bugs early. CD focuses on ensuring that this integrated and tested code can be deployed to users as efficiently and quickly as possible.
- Goal: The goal of CI is to maintain a healthy codebase by integrating and testing code changes frequently. The goal of CD is to shorten the cycle time from code development to deployment, making software delivery more efficient.
In summary, CI/CD is a methodology that encompasses both Continuous Integration and Continuous Deployment/Delivery. CI is the first part of the process, ensuring code is always ready for deployment, while CD takes the process further by automating the deployment of this code to various environments.
Show preview
Tags: javascript, coding, js
One of the most compelling features of JavaScript is its support for asynchronous programming. This is a method of handling operations that allows other tasks to...
Show full articleOne of the most compelling features of JavaScript is its support for asynchronous programming. This is a method of handling operations that allows other tasks to continue running in the background while awaiting the operation's completion.
In JavaScript, Promises and async/await syntax are two features that make asynchronous programming more manageable.
A Promise is an object representing a value which may not be available yet but will be resolved at some point in the future. Promises can help you manage asynchronous operations without getting stuck in callback hell.
Async/await is a syntactic sugar built on top of Promises, introduced in ES2017, which makes asynchronous code look and behave more like synchronous code. The async keyword makes a function return a Promise, and the await keyword can be used inside an async function to wait for a Promise to be resolved.
These features have dramatically improved JavaScript's ability to handle complex operations without blocking the main thread, thereby enhancing the user experience on JavaScript-powered websites and applications.
Show preview
Tags: Ruby, OOP, Dave Thomas, Object Model
Quite interesting and useful talk from Dave Thomas, back from 2009.
Self - if you understand "self", and if you can work out what "self" is, at any point in your...
Show full articleQuite interesting and useful talk from Dave Thomas, back from 2009.
Self - if you understand "self", and if you can work out what "self" is, at any point in your running code, you basically understand all there is to know about metaprogramming.
If your doing metaprogramming, whenever you get stuck trying to work out "How come thats nil", I guarantee, if you track the value of self, you'll understand it"
- Instance variables: look up in "self"
- Methods: look up in self's class
Youtube link to his speech.
Show preview
Tags: The Best!, Ruby
Because Ruby is the most convenient programming language, and while people are programming - convenience means a lot!
Ruby вернулся в первую десятку рейтинга...
Show full article
Ruby вернулся в первую десятку рейтинга TIOBE, и аналитики считают это хорошим знаком. Язык появился очень давно, но оставался в тени до релиза Ruby on Rails в 2006 году. Фреймворк подкинул его на тридцать позиций вверх до топ-10 и обеспечил звание «Язык 2006 года».
После пика популярности в 2008 году Ruby начал сдавать позиции под натиском новых языков, но теперь постепенно взбирается обратно. По мнению экспертов, подобная динамика свидетельствует о естественном росте популярности.
Because Ruby is the most convenient programming language, and while people are programming - convenience means a lot!
Show preview
Tags: Patterns, GRASP, Gof, Anti-patterns, Refactoring, SOLID
Depend on abstractions, not on concretions.
Модули верхних уровней не должны зависеть от модулей нижних уровней. Оба типа модулей должны зависеть от...
Show full article
Depend on abstractions, not on concretions.
- Модули верхних уровней не должны зависеть от модулей нижних уровней. Оба типа модулей должны зависеть от абстракций.
- Абстракции не должны зависеть от деталей. Детали должны зависеть от абстракций.
Что такое модули верхних уровней? Как определить этот уровень? Как оказалось, все очень просто. Чем ближе модуль к вводу/выводу, тем ниже уровень модуля. Т.е. модули, работающие с BD, интерфейсом пользователя, низкого уровня. А модули, реализующие бизнес-логику — высокого уровня.
Что такое зависимость модулей? Это ссылка на модуль в исходном коде, т.е. import, require и т.п. С помощью динамического полиморфизма в runtime можно обратить эту зависимость.
Источник
Show preview