<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>library on Neolisk's Tech Blog</title><link>/tags/library/</link><description>Recent content in library on Neolisk's Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>neolisk@gmail.com (Victor Zakharov)</managingEditor><webMaster>neolisk@gmail.com (Victor Zakharov)</webMaster><copyright>©2020-2024 Victor Zakharov. All Rights Reserved</copyright><lastBuildDate>Sat, 24 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/library/index.xml" rel="self" type="application/rss+xml"/><item><title>Don't Reinvent the Wheel</title><link>/posts/2024-02-24-dont-reinvent-the-wheel/</link><pubDate>Sat, 24 Feb 2024 00:00:00 +0000</pubDate><author>neolisk@gmail.com (Victor Zakharov)</author><atom:modified>Sat, 24 Feb 2024 10:48:14 -0500</atom:modified><guid>/posts/2024-02-24-dont-reinvent-the-wheel/</guid><description>In the dynamic world of software development, the inclination to &amp;ldquo;reinvent the wheel&amp;rdquo; represents a common challenge. Developers, driven by a desire for customization and control, often venture into creating bespoke solutions for problems that have already been addressed.
This approach, while showcasing technical prowess, can lead to inefficiencies, consuming precious time and resources that could be better allocated to enhancing the core value of the project. Recognizing this, the strategic use of third-party component libraries emerges as a compelling alternative.</description><dc:creator>Victor Zakharov</dc:creator><category>development</category><category>architecture</category><category>workflow</category><category>components</category><category>library</category></item><item><title>Angular - Enterprise Library Workflow</title><link>/posts/2022-09-06-angular-enterprise-lib-workflow/</link><pubDate>Tue, 06 Sep 2022 00:00:00 +0000</pubDate><author>neolisk@gmail.com (Victor Zakharov)</author><atom:modified>Sun, 11 Sep 2022 17:02:40 -0400</atom:modified><guid>/posts/2022-09-06-angular-enterprise-lib-workflow/</guid><description>In this workshop, we will create an Angular library, publishable to NPM, with multiple entry points, unit tests and CI/CD in GitHub. Source code for each step will be provided, as well as complete solution in a GitHub repo. Licensed under MIT, use it however you wish. You can skip the intro and see the steps here.
Why this article? Getting Started Conclusion Out of Scope Why this article? A little introduction into why I think an article like this is necessary and why existing internet resources are not enough.</description><dc:creator>Victor Zakharov</dc:creator><category>angular</category><category>development</category><category>library</category><category>npm</category></item></channel></rss>