<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[The Crowdlinker Chronicle - Medium]]></title>
        <description><![CDATA[A collection of content from developers, designers, digital marketers and product people who have an overflowing passion and love to share what they do. - Medium]]></description>
        <link>https://medium.com/the-crowdlinker-chronicle?source=rss----7a4337c5a051---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Crowdlinker Chronicle - Medium</title>
            <link>https://medium.com/the-crowdlinker-chronicle?source=rss----7a4337c5a051---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:19:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-crowdlinker-chronicle" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How AI Is Evolving the Role of PMs — Meet Spectr]]></title>
            <link>https://medium.com/the-crowdlinker-chronicle/how-ai-is-evolving-the-role-of-pms-meet-spectr-29d5ffe8ee0a?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/29d5ffe8ee0a</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 11:40:49 GMT</pubDate>
            <atom:updated>2026-09-21T11:40:19.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The team’s day, rebuilt around AI — Spectr.pm, built by Crowdlinker" src="https://cdn-images-1.medium.com/max/1024/1*I1KGyHY5z16pslhXBurqlQ.png" /></figure><p>A product manager’s job is more than writing stories for a backlog. It’s prioritizing what actually matters this quarter, keeping stakeholders aligned when they don’t agree with each other, defending a roadmap under pressure, watching a budget that’s tighter than the plan assumed, and saying no to good ideas that are wrong for right now. Writing the story is the last step, not the job.</p><p>None of that happens alone. Alongside the PM, the team carries just as much of the outcome: a designer catching a usability problem before it ships, a developer flagging that an estimate quietly doubled. A roadmap can be prioritized perfectly and still slip because the team wasn’t working off the same information the PM was.</p><p>That runs both ways. Developers and designers have to keep the PM updated too: a blocked ticket, a design that solves the wrong problem, a scope that’s grown since the kickoff. A PM who hears about any of that at the retro, instead of mid-sprint, has already lost the chance to do anything about it.</p><p>With that in mind: at <strong>Crowdlinker</strong>, we built <a href="https://spectr.pm/"><strong>Spectr</strong></a>. Its aim is simple: give the team back the hours that go into writing things down, chasing status, and re-explaining decisions, so there’s more of the day left for the work that actually needs a person.</p><p>1. <strong>Meetings turn into notes without a rewatch.</strong> Spectr connects to the recorder a team already uses, Fathom, Granola, or Read.ai, and writes up what was said and what needs to happen next, before anyone has to relisten at 1.5x speed.</p><p>2. <strong>Specs come from the conversation, not a blank page.</strong> Spectr drafts the spec straight from the meeting, or from a written requirement, with the project’s own history folded in, so nobody re-explains a decision the team made two months ago.</p><p>3. <strong>Stories land in the tracker ready to work.</strong> Once a spec is approved, the stories it produces go straight into Jira, Linear, or Shortcut, detailed enough for a developer to start without a clarifying Slack thread.</p><p>4. <strong>Requirements docs stay current.</strong> Instead of a doc nobody opens again after the kickoff, Spectr updates it as decisions change, so it’s still accurate in month three.</p><p>5. <strong>The project remembers what the team decided.</strong> Every meeting and requirement feeds a running memory, so a new hire or a returning stakeholder gets caught up without the PM repeating six months of context out loud.</p><p>6. <strong>Budget stops being a surprise at the retro.</strong> Spectr checks hours logged in Harvest against what a project scoped for, so the team sees a feature running over while there’s still time to do something about it.</p><p>7. <strong>Bugs and feedback sit next to the roadmap.</strong> Spectr pulls in what’s breaking in Sentry and what users are saying in PostHog, so it’s part of the same picture instead of a dashboard nobody opens until something’s on fire.</p><p>8. <strong>Everyone watches the same board update live.</strong> A status change shows up for the PM, the designer, and the developer at the same moment, so “where are we on this?” stops being a Slack message someone has to answer.</p><p>PMs, developers, and designers are adapting to a day with a lot less busywork in it, and a lot more room for the decisions only a person can make. Spectr doesn’t decide what to build or ship; that’s still the team’s call. What it removes is the searching, chasing, and re-explaining that used to eat most of a working day.</p><p>Feel free to learn more about Spectr <a href="https://spectr.pm/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29d5ffe8ee0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-crowdlinker-chronicle/how-ai-is-evolving-the-role-of-pms-meet-spectr-29d5ffe8ee0a">How AI Is Evolving the Role of PMs — Meet Spectr</a> was originally published in <a href="https://medium.com/the-crowdlinker-chronicle">The Crowdlinker Chronicle</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Docker with NestJS (or any NodeJS app)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-crowdlinker-chronicle/using-docker-with-nestjs-or-any-nodejs-app-e905b83275e?source=rss----7a4337c5a051---4"><img src="https://cdn-images-1.medium.com/max/1920/1*h_sJ4LW2P0mr7UbDXd6YNw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">I am going to make this simple for you &amp; tell you that the code I am going to provide you today can be easily customized for running not&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/the-crowdlinker-chronicle/using-docker-with-nestjs-or-any-nodejs-app-e905b83275e?source=rss----7a4337c5a051---4">Continue reading on The Crowdlinker Chronicle »</a></p></div>]]></description>
            <link>https://medium.com/the-crowdlinker-chronicle/using-docker-with-nestjs-or-any-nodejs-app-e905b83275e?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/e905b83275e</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[containerize]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Fri, 18 Jun 2021 19:07:41 GMT</pubDate>
            <atom:updated>2021-06-18T19:08:15.399Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Creating/Writing/Downloading Files in NestJS]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-crowdlinker-chronicle/creating-writing-downloading-files-in-nestjs-ee3e26f2f726?source=rss----7a4337c5a051---4"><img src="https://cdn-images-1.medium.com/max/740/1*5NO38em3EaUV8-79D8AVVQ.png" width="740"></a></p><p class="medium-feed-snippet">Working on a project, I realized there was no proper way mentioned anywhere on how we can create/write/download file functions in NestJS&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/the-crowdlinker-chronicle/creating-writing-downloading-files-in-nestjs-ee3e26f2f726?source=rss----7a4337c5a051---4">Continue reading on The Crowdlinker Chronicle »</a></p></div>]]></description>
            <link>https://medium.com/the-crowdlinker-chronicle/creating-writing-downloading-files-in-nestjs-ee3e26f2f726?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee3e26f2f726</guid>
            <category><![CDATA[files]]></category>
            <category><![CDATA[csv]]></category>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[creating]]></category>
            <category><![CDATA[export]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Wed, 02 Jun 2021 21:55:02 GMT</pubDate>
            <atom:updated>2021-06-02T21:55:02.636Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Best Way to Structure Your Directory/Code (NestJS)]]></title>
            <link>https://medium.com/the-crowdlinker-chronicle/best-way-to-structure-your-directory-code-nestjs-a06c7a641401?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/a06c7a641401</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[code-quality]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Fri, 17 Jul 2020 01:35:06 GMT</pubDate>
            <atom:updated>2020-07-17T01:38:38.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h_sJ4LW2P0mr7UbDXd6YNw.jpeg" /></figure><p>I’ve been building apps using NestJS for quite a while now and I want to share the best way to structure your directory/code with other developers new to this framework.</p><p>Before we begin, keep in mind that this structure is quite generic and <strong>might not work</strong> with some techniques like GraphQL. You could however modify it as per your requirements.</p><p>Now, let’s get straight to the point!</p><h3>Directory Structure 📂</h3><p>These are just the directory names. I will give more insights into how the files look inside these directories in their own particular section.</p><pre>src<br>├── authentication<br>├── common<br>│   ├── constants<br>│   ├── decorators<br>│   │   ├── metadata<br>│   │   └── requests<br>│   ├── exceptions<br>│   ├── guards<br>│   ├── helpers<br>│   │   ├── exceptions<br>│   │   └── responses<br>│   ├── interfaces<br>│   ├── middlewares<br>│   │   └── models<br>│   ├── pipes<br>│   ├── serializers<br>│   │   ├── exceptions<br>│   │   └── responses<br>│   └── validations<br>├── config<br>│   ├── api<br>│   ├── app<br>│   ├── cache<br>│   ├── database<br>│   │   └── postgres<br>│   ├── queue<br>│   ├── session<br>│   └── storage<br>├── database<br>│   ├── factories<br>│   │   ├── addresses<br>│   │   └── users<br>│   ├── migrations<br>│   └── seeders<br>│       ├── addresses<br>│       └── users<br>├── jobs<br>│   ├── consumers<br>│   │   └── verification-mail<br>│   └── producers<br>│       └── verification-mail<br>├── mails<br>│   └── verification<br>├── models<br>│   ├── addresses<br>│   │   ├── constants<br>│   │   ├── entities<br>│   │   ├── interfaces<br>│   │   └── serializers<br>│   └── users<br>│       ├── constants<br>│       ├── entities<br>│       ├── interfaces<br>│       └── serializers<br>├── providers<br>|   ├── cache<br>│   │   └── redis<br>│   ├── database<br>│   │   └── postgres<br>│   └── queue<br>│       └── redis<br>├── app.controller.ts<br>├── app.module.ts<br>├── app.service.ts<br>├── main.ts<br>└── seed.ts</pre><h4>Config ⚙️</h4><p>Let’s begin our tutorial with the initialization of our environment variables. I am using the package <a href="https://github.com/nestjs/config">@nestjs/config</a> in this use case.</p><p>The config/ folder consists of different sections of variable types to be loaded into our environment.</p><pre>src/config<br>├── app<br>│   ├── config.module.ts<br>│   ├── config.service.ts<br>│   └── configuration.ts<br>├── cache<br>│   ├── config.module.ts<br>│   ├── config.service.ts<br>│   └── configuration.ts<br>├── database<br>│   ├── mongo<br>│   │   ├── config.module.ts<br>│   │   ├── config.service.ts<br>│   │   └── configuration.ts<br>│   ├── mysql<br>│   │   └── [...]<br>│   └── postgres<br>│       └── [...]<br>├── queue<br>│   └── [...]<br>├── session<br>│   └── [...]<br>└── storage<br>    └── [...]</pre><p><strong>Note: </strong>Here [...] means same as other config folders.</p><p>You can see how unique &amp; common the structure is. This makes it easy for other developers that might be new to the project to quickly understand what each file does just by looking at the directory structure.</p><p>You can read more about how all the files in config works by looking at my other post: <a href="https://medium.com/the-crowdlinker-chronicle/creating-config-files-in-nestjs-dcd059ae15e4">Creating Config Files in NestJS</a>.</p><h4>Providers 📥</h4><p>Providers are basically going to be the core modules that initiate a connection between the app &amp; the provider engine (for eg. database).</p><p>This I believe is one of the simplest way to structure your providers folder:</p><pre>src/providers<br>├── cache<br>│   └── redis<br>│       └── provider.module.ts<br>├── database<br>│   ├── mongo<br>│   │   └── provider.module.ts<br>│   ├── mysql<br>│   │   └── [...]<br>│   └── postgres<br>│       └── [...]<br>├── mail<br>│   └── smtp<br>│       └── [...]<br>└── queue<br>    └── redis<br>        └── [...]</pre><p><strong>Note: </strong>Here [...] means same as other config folders.</p><p>Your provider.module.ts for each file would look something like this:</p><pre>import { DatabaseType } from &#39;typeorm&#39;;<br>import { Module } from &#39;@nestjs/common&#39;;<br>import { TypeOrmModule, TypeOrmModuleAsyncOptions } from &#39;@nestjs/typeorm&#39;;<br>import { MysqlConfigModule } from &#39;../../../config/database/mysql/config.module&#39;;<br>import { MysqlConfigService } from &#39;../../../config/database/mysql/config.service&#39;;</pre><pre>@Module({<br>  imports: [<br>    TypeOrmModule.forRootAsync({<br>      imports: [MysqlConfigModule],<br>      useFactory: async (<em>mysqlConfigService</em>: MysqlConfigService) <em>=&gt;</em> ({<br>        type: &#39;mysql&#39; as DatabaseType,<br>        host: <em>mysqlConfigService</em>.host,<br>        port: <em>mysqlConfigService</em>.port,<br>        username: <em>mysqlConfigService</em>.username,<br>        password: <em>mysqlConfigService</em>.password,<br>        database: <em>mysqlConfigService</em>.database,<br>        entities: [<br>          // ... All MySQL based schemas/entities<br>        ],<br>      }),<br>      inject: [MysqlConfigService],<br>    } as TypeOrmModuleAsyncOptions),<br>  ],<br>})<br>export <em>class</em> MysqlDatabaseProviderModule {}</pre><p>Notice how we are importing MysqlConfigModule &amp; injecting MysqlConfigService from the src/config/database/mysql folder.</p><p>IMO, this is as clean as it can get. You could try creating classes and directly inject a class by using useClass instead of useFactory but I feel it’s just not needed… especially because you need those environment variable values being passed here.</p><h4>Models 💾</h4><p>Models will simply be the parent folder that contains all model related data.</p><pre>src/models<br>├── addresses<br>│   ├── entities<br>│   │   └── address.entity.ts<br>│   ├── interfaces<br>│   │   └── address.interface.ts<br>│   ├── serializers<br>│   │   └── address.serializer.ts<br>│   ├── addressess.controller.ts<br>│   ├── addresses.module.ts<br>│   ├── addresses.repository.ts<br>│   └── addresses.service.ts<br>└── users<br>    ├── entities<br>    │   └── user.entity.ts<br>    ├── interfaces<br>    │   └── user.interface.ts<br>    ├── serializers<br>    │   └── user.serializer.ts<br>    ├── users.controller.ts<br>    ├── users.module.ts<br>    ├── users.repository.ts<br>    └── users.service.ts</pre><p>To know what the contents of each file are, please read my other post: <a href="https://medium.com/the-crowdlinker-chronicle/best-way-to-inject-repositories-using-typeorm-nestjs-e134c3dbf53c">Best Way to Inject Repositories using TypeORM (NestJS)</a>.</p><h4>Database Migrations/Seeders 📤</h4><p>The src/database folder is as simple as it can get:</p><pre>src/database<br>├── factories<br>│   ├── addresses<br>│   │   └── factory.ts<br>│   └── users<br>│       └── factory.ts<br>├── migrations<br>│   ├── 1590973586541-CreateAddressesTable.ts<br>│   └── 1592951122241-CreateUsersTable.ts<br>└── seeders<br>    ├── addresses<br>    │   ├── seeder.module.ts<br>    │   └── seeder.service.ts<br>    └── users<br>        ├── seeder.module.ts<br>        └── seeder.service.ts</pre><p>I’ve set my TypeORM config to generate migrations into src/database/migrations folder, you can do the same by updating the migrations key in your ormconfig.js file. You can read more about it <a href="https://typeorm.io/#/using-ormconfig">here</a>.</p><p>To learn more about how src/database/factories &amp; src/database/seeders work, please read my other article: <a href="https://medium.com/the-crowdlinker-chronicle/seeding-databases-using-nestjs-cd6634e8efc5">Seeding Databases Using NestJS</a>.</p><h4>Authentication 👨‍💻</h4><p>This folder is similar to other folders in src/models . The only difference you’d find here is the addition of the authentication strategy involved. You could keep the strategy in its own folder as well.</p><pre>src/authentication<br>├── dto<br>│   └── login.dto.ts<br>├── interfaces<br>│   ├── jwt-payload.interface.ts<br>│   ├── login.interface.ts<br>│   └── token.interface.ts<br>├── serializers<br>│   └── token.serializer.ts<br>├── auth.controller.ts<br>├── auth.module.ts<br>├── auth.service.ts<br>└── jwt.strategy.ts</pre><p>All files here work according to the <a href="https://docs.nestjs.com/techniques/authentication">authentication tutorial provided in NestJS’s documentation</a> itself. Nothing special here! 😄</p><h4>Common Files 🗃</h4><p>As you can see, src/common has the most number of directories here. I use this common folder to literally fill it in with any extra classes/files that might commonly be used by other modules in your app.</p><p>There is not much to explain here, except the fact that we are using NestJS’s core fundamentals (like <a href="https://docs.nestjs.com/guards">guards</a>, <a href="https://docs.nestjs.com/pipes">pipes</a>, <a href="https://docs.nestjs.com/custom-decorators">decorators</a>) in this folder &amp; some other common constants, interfaces &amp; helpers.</p><pre>src/common<br>├── constants<br>│   └── settings.ts<br>├── decorators<br>│   ├── metadata<br>│   │   └── user-types.decorator.ts<br>│   ├── requests<br>│   │   └── logged-in-user.decorator.ts<br>│   └── validations<br>│       ├── UserExists.ts<br>│       └── UniqueUserEmail.ts<br>├── exceptions<br>│   └── http-exception.filter.ts<br>├── guards<br>│   └── user-types.guard.ts<br>├── helpers<br>│   ├── exceptions<br>│   │   └── validation.helper.ts<br>│   ├── responses<br>│   │   ├── error.helper.ts<br>│   │   └── success.helper.ts<br>│   ├── number.helper.ts<br>│   ├── array.helper.ts<br>│   ├── query.helper.ts<br>│   ├── request.helper.ts<br>│   └── string.helper.ts<br>├── interceptors<br>│   └── http-cache.interceptor.ts<br>├── interfaces<br>│   ├── inputs.interface.ts<br>│   └── search.interface.ts<br>├── middleware<br>│   └── models<br>│       └── user.middleware.ts<br>├── pipes<br>│   ├── models<br>│   │   └── user-entity.pipe.ts<br>│   ├── search.pipe.ts<br>│   └── validation.pipe.ts<br>└── serializers<br>    ├── responses<br>    │   ├── error.serializer.ts<br>    │   └── success.serializer.ts<br>    ├── validation<br>    │   └── validation-error.serializer.ts<br>    └── model.serializer.ts</pre><p>One extra thing you’d see here is src/decorator/validations folder. This folder is based on custom validations built using class-validator .</p><p>You could also add a utils folder for custom classes… in this case, let’s say a custom logger class? So you could create a file in src/common/utils/logger 😀.</p><h4>Mails ✉️</h4><p>The mails folder will just consists of content to be used in your mailers.</p><pre>src/mails<br>└── verification<br>    └── content.ts</pre><p>This data.ts file would simply be a function returning string content for your mail.</p><p>Something like:</p><pre>const content = (firstName: string, verificationLink: string): string =&gt; {<br>  return `Hello ${firstName}, &lt;br&gt;&lt;br&gt; Please verify your &lt;a href=&quot;${verificationLink}&quot;&gt;account&lt;/a&gt;. Thanks!`<br>}</pre><h4>Jobs 👷‍♂️</h4><p>Finally, the jobs folder will contain your queue consumers/providers.</p><pre>src/jobs<br>├── consumers<br>│   └── verification-mail<br>│       └── verification-mail.job.consumer.ts<br>└── producers<br>    └── verification-mail<br>        └── verification-mail.job.producer.ts</pre><p>This is based on the default <a href="https://docs.nestjs.com/techniques/queues">queueing technique provided in NestJS documentation</a> using the package nestjs/bull .</p><p>Since this is literally from the docs, I am hoping you can literally relate the file names with the ones provided in the docs &amp; come up with your own solution.</p><h3>Conclusion</h3><p>I hope this helped all the other developers new to this framework in one or the other way.</p><p>If you’d like any help, feel free to contact me or my team @<a href="https://medium.com/u/1a54333c8b60">Crowdlinker</a>.</p><p>Don’t forget to share your comments down below. I’d love to hear &amp; see how other developers approaching towards this. 👍 🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a06c7a641401" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-crowdlinker-chronicle/best-way-to-structure-your-directory-code-nestjs-a06c7a641401">Best Way to Structure Your Directory/Code (NestJS)</a> was originally published in <a href="https://medium.com/the-crowdlinker-chronicle">The Crowdlinker Chronicle</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Way to Inject Repositories using TypeORM (NestJS)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-crowdlinker-chronicle/best-way-to-inject-repositories-using-typeorm-nestjs-e134c3dbf53c?source=rss----7a4337c5a051---4"><img src="https://cdn-images-1.medium.com/max/1280/1*w-ISpJdkmJ7RrsCHJXc_yg.png" width="1280"></a></p><p class="medium-feed-snippet">Taking Class-Transformer &amp; TypeORM in NestJS &amp; comparing them with Laravel Collections &amp; Query Builder, I am today going to explain how to&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/the-crowdlinker-chronicle/best-way-to-inject-repositories-using-typeorm-nestjs-e134c3dbf53c?source=rss----7a4337c5a051---4">Continue reading on The Crowdlinker Chronicle »</a></p></div>]]></description>
            <link>https://medium.com/the-crowdlinker-chronicle/best-way-to-inject-repositories-using-typeorm-nestjs-e134c3dbf53c?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/e134c3dbf53c</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[typeorm]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 21:10:00 GMT</pubDate>
            <atom:updated>2021-10-26T14:04:16.879Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Adding Options to your Database Seeder (NestJS)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-crowdlinker-chronicle/adding-options-to-your-database-seeder-nestjs-768beecbaba8?source=rss----7a4337c5a051---4"><img src="https://cdn-images-1.medium.com/max/1980/1*mVhnozDtp2jAnBgnxeaeFQ.jpeg" width="1980"></a></p><p class="medium-feed-snippet">Long ago, I published an article on &#x201C;Seeding Databases in NestJS&#x201D;. This article is basically a small icing on the cake to add some magic&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/the-crowdlinker-chronicle/adding-options-to-your-database-seeder-nestjs-768beecbaba8?source=rss----7a4337c5a051---4">Continue reading on The Crowdlinker Chronicle »</a></p></div>]]></description>
            <link>https://medium.com/the-crowdlinker-chronicle/adding-options-to-your-database-seeder-nestjs-768beecbaba8?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/768beecbaba8</guid>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[cli]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Thu, 30 Jan 2020 15:06:57 GMT</pubDate>
            <atom:updated>2020-01-30T15:06:57.893Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Creating Config Files in NestJS]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-crowdlinker-chronicle/creating-config-files-in-nestjs-dcd059ae15e4?source=rss----7a4337c5a051---4"><img src="https://cdn-images-1.medium.com/max/1980/1*mVhnozDtp2jAnBgnxeaeFQ.jpeg" width="1980"></a></p><p class="medium-feed-snippet">Getting values from an environment file isn&#x2019;t supposed to be as simple as creating a&#xA0;.env  file. In NodeJS, dotenv, is one of the most&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/the-crowdlinker-chronicle/creating-config-files-in-nestjs-dcd059ae15e4?source=rss----7a4337c5a051---4">Continue reading on The Crowdlinker Chronicle »</a></p></div>]]></description>
            <link>https://medium.com/the-crowdlinker-chronicle/creating-config-files-in-nestjs-dcd059ae15e4?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/dcd059ae15e4</guid>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[config]]></category>
            <category><![CDATA[variables]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 18:46:06 GMT</pubDate>
            <atom:updated>2020-01-08T18:46:06.130Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Seeding Databases Using NestJS]]></title>
            <link>https://medium.com/the-crowdlinker-chronicle/seeding-databases-using-nestjs-cd6634e8efc5?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/cd6634e8efc5</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[mysql]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Fri, 03 May 2019 02:51:46 GMT</pubDate>
            <atom:updated>2022-05-19T18:35:53.394Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMkClP0D2ZkWEXAPHYvy1Q.png" /></figure><p>NestJS is a highly scalable NodeJS framework revolutionizing the building of server-side apps. Its ability to create <a href="https://docs.nestjs.com/application-context">Application Contexts</a> allows developers to easily build micro-applications and take advantage of components and modules within that environment.</p><p>One can simply create a wrapper around Nest’s container that will hold all the instantiated classes. You can then grab an existing instance inside that wrapper and run functions inside it, such as clearing your app cache, rebuilding configuration files etc.</p><h3>What To Seed? 🤔</h3><p>Any kind of static data that is commonly shared between entities or is mainly used for testing is what one must focus on when seeding. These can either be base entities like Languages, or entities like Admin User Accounts which are mainly required when your application involves Authentication and User Role Management 💁‍♂️.</p><p>Language(s) being one of the simplest entities to explain, is what we are going to focus on today.</p><h3>Directory Structure 📂</h3><p>Nest promotes a strict modular approach, which we shall adhere to. This is how, we are going to store all files explained in this article.</p><pre>src /<br>├── database<br>│   └── seeders<br>│       ├── seeder.module.ts<br>│       ├── seeder.ts<br>│       └── language<br>│           ├── data.ts<br>│           ├── languages.module.ts<br>│           └── languages.service.ts<br>├── models<br>│   └── language<br>│       ├── entities<br>│       │   └── language.entity.ts<br>│       └── interfaces<br>│           └── language.interface.ts<br>├── providers<br>│   └── database<br>│       └── mysql<br>│           └── provider.module.ts<br>└── seed.ts</pre><h3>Providers</h3><p>Before we start, we need to connect to the database. In this post, we are going to use <a href="https://docs.nestjs.com/techniques/database">TypOrmModule to connect to a MySQL database</a>, however, you can create your own providers in a similar fashion for <a href="https://hackmd.io/p5KKglLuRLC0Us1yQxNjdg?both">MongoDB using the MongooseModule</a>. If your application requires you to connect to multiple databases, consider reading about <a href="https://docs.nestjs.com/modules">Dynamic Modules</a>.</p><h4>provider.module.ts</h4><pre>/**<br> * Import and provide base typeorm (mysql) related classes.<br> *<br> * @module<br> */<br>@Module({<br>  imports: [<br>    TypeOrmModule.forRootAsync({<br>      imports: [MysqlConfigModule],<br>      useFactory: async (mysqlConfigService: MysqlConfigService) =&gt; ({<br>        type: &#39;mysql&#39; as DatabaseType,<br>        host: mysqlConfigService.host,<br>        port: mysqlConfigService.port,<br>        username: mysqlConfigService.username,<br>        password: mysqlConfigService.password,<br>        database: mysqlConfigService.database,<br>        entities: [Language],<br>        synchronize: true,<br>      }),<br>      inject: [MysqlConfigService],<br>    } as TypeOrmModuleAsyncOptions),<br>  ],<br>})<br>export class MysqlDatabaseProviderModule {}</pre><p>Notice how we are using my Language Model directly in the entities array. This is different than the technique mentioned <a href="https://docs.nestjs.com/techniques/database">here</a>, especially because of an issue generally faced when creating production builds shared on its <a href="https://github.com/nestjs/nest/issues/1018">Github</a>.</p><h3>Models &amp; Interfaces</h3><p>Binding the model with an interface is good practice. With Typescript support out of the box, Nest makes this super easy for us.</p><h3>Interfaces</h3><p>This is a simple example of how we can create a language interface. There isn’t much to explain here, but if your Model has types etc, you can take advantage of <a href="https://www.typescriptlang.org/docs/handbook/enums.html">Enums</a> and then <a href="https://github.com/typeorm/typeorm/blob/master/docs/entities.md#enum-column-type">bind them to your Model</a>.</p><h4>languages.interface.ts</h4><pre>/**<br> * Language variable type declaration.<br> *<br> * @interface<br> */<br>export interface ILanguage {<br>  name: string;<br>}</pre><h3>Model / Entity</h3><p>It’s always good to have timestamps in your model. Other than that, creating a model is relatively simple. You can learn more about how to create models using TypeORM here: <a href="https://github.com/typeorm/typeorm">TypeORM’s documentation</a>.</p><h4>languages.entity.ts</h4><pre>/**<br> * Entity Schema for Languages.<br> *<br> * @class<br> */<br>@Entity({<br>  name: &#39;languages&#39;,<br>})<br>export class Language implements ILanguage {<br>  @PrimaryGeneratedColumn()<br>  id: number;</pre><pre>  @Column()<br>  name: string;</pre><pre>  @Column({<br>    type: &#39;timestamp&#39;,<br>    default: () =&gt; &#39;CURRENT_TIMESTAMP&#39;,<br>  })<br>  createdAt: string;</pre><pre>  @Column({<br>    type: &#39;timestamp&#39;,<br>    default: () =&gt; &#39;CURRENT_TIMESTAMP&#39;,<br>  })<br>  updatedAt: string;<br>}</pre><h3>Data</h3><p>To make things simpler, we will be saving all the Language data in a constant. However, if you plan on using a <em>faker</em>, consider taking a look at <a href="https://github.com/marak/Faker.js/">Faker’s documentation</a>.</p><h4>data.ts</h4><pre>export const languages: ILanguage[] = [<br>  { name: &#39;English&#39; },<br>  { name: &#39;French&#39; },<br>  { name: &#39;Spanish&#39; },<br>  { name: &#39;Russian&#39; },<br>  // ... and others ... <br>];</pre><h3>Services &amp; Modules</h3><p>Services act as an intermediary between the controller and the repository. It’s a term which you will find most commonly used when you search the internet for <strong>Service-Repository Pattern</strong>. You can read more about how to create Modules in NestJS <a href="https://docs.nestjs.com/modules">here</a>.</p><h3>Language Service</h3><p>Let’s start by creating the LanguageService which will take its repository as a dependency. The repository however is pre-provided to us by TypeORM itself, so we don’t have to create it.</p><h4>languages.services.ts</h4><pre>/**<br> * Service dealing with language based operations.<br> *<br> * @class<br> */<br>@Injectable()<br>export class LanguageSeederService {<br>  /**<br>   * Create an instance of class.<br>   *<br>   * @constructs<br>   *<br>   * @param {Repository&lt;Language&gt;} languageRepository<br>   */<br>  constructor(<br>    @InjectRepository(Language)<br>    private readonly languageRepository: Repository&lt;Language&gt;,<br>  ) {}</pre><pre>  /**<br>   * Seed all languages.<br>   *<br>   * @function<br>   */<br>  create(): Array&lt;Promise&lt;Language&gt;&gt; {<br>    return languages.map(async (language: ILanguage) =&gt; {<br>      return await this.languageRepository<br>        .findOne({ name: language.name })<br>        .exec()<br>        .then(async dbLangauge =&gt; {<br>          // We check if a language already exists.<br>          // If it does don&#39;t create a new one.<br>          if (dbLangauge) {<br>            return Promise.resolve(null);<br>          }</pre><pre>          return Promise.resolve(<br>            // or create(language).then(() =&gt; { ... });<br>            await this.languageRepository.save(language),<br>          );<br>        })<br>        .catch(error =&gt; Promise.reject(error));<br>    });<br>  }<br>}</pre><h3>Language Module</h3><p>The language module imports the TypeOrmModule for the Language entity along with its service that handles seeding of all languages.</p><h4>languages.module.ts</h4><pre>/**<br> * Import and provide seeder classes for languages.<br> *<br> * @module<br> */<br>@Module({<br>  imports: [TypeOrmModule.forFeature([Language])],<br>  providers: [LanguageSeederService],<br>  exports: [LanguageSeederService],<br>})<br>export class LanguageSeederModule {}</pre><h3>Main Seeder Module</h3><h4>seeder.module.ts</h4><pre>/**<br> * Import and provide seeder classes.<br> *<br> * @module<br> */<br>@Module({<br>  imports: [MysqlDatabaseProviderModule, LanguageSeederModule],<br>  providers: [Logger, Seeder],<br>})<br>export class SeederModule {}</pre><p>Notice how our main MySQL provider module is imported here. Loading of all classes is asynchronous by default but you can make them synchronous by importing providers in the method defined in <a href="https://docs.nestjs.com/fundamentals/async-providers">NestJS’s documentation</a>.</p><h3>Seeder Provider</h3><p>This is the final seeder class which has a seed() function that further calls the create() function in the LanguageSeederService.</p><h4>seeder.ts</h4><pre>@Injectable()<br>export class Seeder {<br>  constructor(<br>    private readonly logger: Logger,<br>    private readonly languageSeederService: LanguageSeederService,<br>  ) {}</pre><pre>  async seed() {<br>    await this.languages()<br>      .then(completed =&gt; {<br>        this.logger.debug(&#39;Successfuly completed seeding users...&#39;);</pre><pre>        Promise.resolve(completed);<br>      })<br>      .catch(error =&gt; {<br>        this.logger.error(&#39;Failed seeding users...&#39;);</pre><pre>        Promise.reject(error);<br>      });<br>  }</pre><pre>  async languages() {<br>    return await Promise.all(this.languageSeederService.create())<br>      .then(createdLanguages =&gt; {<br>        // Can also use this.logger.verbose(&#39;...&#39;);<br>        this.logger.debug(<br>          &#39;No. of languages created : &#39; +<br>            // Remove all null values and return only created languages.<br>            createdLanguages.filter(<br>              nullValueOrCreatedLanguage =&gt; nullValueOrCreatedLanguage,<br>            ).length,<br>        );</pre><pre>        return Promise.resolve(true);<br>      })<br>      .catch(error =&gt; Promise.reject(error));<br>  }<br>}</pre><h3>Building Application Context &amp; Running The Seeder</h3><p>The final steps involve writing a bootstrap function which will use NestFactory to create an application context.</p><h3>Bootstrap Your Micro-App</h3><h4>seed.ts</h4><pre>async function bootstrap() {<br>  NestFactory.createApplicationContext(SeederModule)<br>    .then(appContext =&gt; {<br>      const logger = appContext.get(Logger);<br>      const seeder = appContext.get(Seeder);</pre><pre>      seeder<br>        .seed()<br>        .then(() =&gt; {<br>          logger.debug(&#39;Seeding complete!&#39;);<br>        })<br>        .catch(error =&gt; {<br>          logger.error(&#39;Seeding failed!&#39;);</pre><pre>          throw error;<br>        })<br>        .finally(() =&gt; appContext.close());<br>    })<br>    .catch(error =&gt; {<br>      throw error;<br>    });<br>}<br>bootstrap();</pre><p>Notice how we have appContext().close() as the final promise action.</p><h3>The Command</h3><p>Last but not the least, simply add this script to your package.json. You can then run your seeder using npm or yarn or any package manager you are using.</p><h4>package.json</h4><pre>{<br>  // ... other package.json fields ...<br>  &quot;scripts&quot;: {<br>    // ... other scripts ...<br>    &quot;seed&quot;: &quot;ts-node -r tsconfig-paths/register src/seed.ts&quot;<br>  }<br>}</pre><h3>Conclusion</h3><p>Nest is a really powerful back-end framework. I strongly believe that it is going to transform coding in NodeJS. For more information on Nest, please visit its <a href="https://nestjs.com/">website</a> and consider <a href="https://docs.nestjs.com/support">supporting them</a> on OpenCollective or via Paypal.</p><p>Also, be sure to check out the next part of this article at ‘<a href="https://medium.com/the-crowdlinker-chronicle/adding-options-to-your-database-seeder-nestjs-768beecbaba8">Adding Options to your Database Seeder</a>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*bIjxjDfQz2_vXc9bbVPZKQ.png" /></figure><p>Let me know in the comments if you face any issues running this or need any other kind of assistance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd6634e8efc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-crowdlinker-chronicle/seeding-databases-using-nestjs-cd6634e8efc5">Seeding Databases Using NestJS</a> was originally published in <a href="https://medium.com/the-crowdlinker-chronicle">The Crowdlinker Chronicle</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create Your Developer Success Story]]></title>
            <link>https://medium.com/the-crowdlinker-chronicle/create-your-developer-success-story-527f0bad4bb5?source=rss----7a4337c5a051---4</link>
            <guid isPermaLink="false">https://medium.com/p/527f0bad4bb5</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Prateek Kathal]]></dc:creator>
            <pubDate>Fri, 31 Aug 2018 19:49:21 GMT</pubDate>
            <atom:updated>2018-08-31T20:09:05.242Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQ_RBb21jZguaGmo2MHOgw.jpeg" /></figure><p>Some developers code for <strong>coffee</strong> ☕️, some for <strong>money 🤑 </strong>and some for <strong>zen</strong> ☮️. Problem solving is one of the skills that makes them a great developer.</p><p>Is that enough though? Definitely not!</p><p>For clients, business comes first. Most clients care more about <strong>speed of delivery</strong>, which might not produce the best results. Imagine ordering a pizza and having it delivered to you in 15 minutes. It’s possible, but do you really expect it to be as good as the one that takes 30 minutes? Cooking requires time. It’s an art.</p><p>The outcome of any rushed work generally turns out to be undesirable.</p><p>Change in requirements may render any previously written code as <strong>useless</strong>. Furthermore, when clients disapprove of extending deadlines to accommodate these changes, we start noticing a decline in code quality.</p><p><strong>Failure is important for success</strong>, and for any developer, one of the biggest failures is writing <strong>“Bad Code”</strong>.</p><p><strong><em>What is a Bad Code?</em></strong></p><p>Any code which defies the laws of structuring, reusability, optimal performance and code readability is known as “Bad Code”.</p><p>Let’s not treat the word “Bad” as 😞 . <strong>You learn as you go.</strong> If you are new to coding, it’s okay to have some lines in your code that don’t make sense. However, it’s important to not sacrifice <strong>code quality</strong>, especially when you have tight deadlines. Developers should focus on the quality of code, and leave the deadlines up to the Project Managers.</p><p><strong><em>What are its disadvantages?</em></strong></p><ul><li>Hard to read &amp; understand</li><li>Overall <a href="https://smartbear.com/blog/collaborate/defining-code-quality/">quality</a> &amp; performance decreases</li><li>Harder to manage in the long run</li><li><a href="https://en.wikipedia.org/wiki/Duplicate_code">Repetition</a></li><li>Low Reusability</li><li><a href="https://softwareengineering.stackexchange.com/questions/102617/pointless-code-in-your-source">Pointless Code</a></li></ul><p><strong><em>Note:</em></strong><em> </em>Something bad in the eyes of one, may be good in the eyes of another.</p><p><strong><em>So then how do we differentiate between “good” and “bad”?</em></strong></p><ul><li>Keep four basic things in mind when coding — <strong>Readability</strong>, <strong>Structure</strong>, <strong>Performance</strong> &amp; <strong>Standards of Implementation</strong> (<a href="https://www.php-fig.org/psr/">PSR for PHP</a>, <a href="https://www.python.org/dev/peps/">PEP for Python</a>).</li></ul><p>In the first few years of a developer’s career, the main focus is on <strong>making the code/logic work</strong> rather than actually spending time structuring it. As a result, the code quality on a scale of 1 to 10 usually remains between 1 &amp; 5.</p><p>Going back to the first paragraph of this article, if you look closely at the line numbers, you’ll see a difference of <strong>90 lines</strong> between the two. This basically means that the person who wrote 100 lines of code didn’t put any effort into structuring it. On the other hand, the person doing the same thing in 10 lines is more or less following a certain pattern to structure the code.</p><p><strong><em>My code works fine, so why should I waste time restructuring it?</em></strong></p><ul><li>When working in a team, it’s important to follow a particular set of standards and patterns. This is so everyone can read and understand your code without physically coming to your desk and asking you what lines 100 to 200 are supposed to do.</li></ul><blockquote>No one pays you to code better, but the joy of money is valid only when you are working alone.</blockquote><ul><li>It’s not just about what you’re getting paid for, <strong>it’s about personal growth </strong>as well.</li></ul><blockquote><em>Working code may be good for business, but it will never be good for a developer if it isn’t easy to read.</em></blockquote><h4>Clear Your Concepts!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fv5V3XxJCV0pFu%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv5V3XxJCV0pFu%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fv5V3XxJCV0pFu%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/de4281b768ab1d7a5f7a09c8432b8361/href">https://medium.com/media/de4281b768ab1d7a5f7a09c8432b8361/href</a></iframe><p>Before you build a car, you must know how to build an engine. Similarly, before you build software or an app, you need to know how things actually work behind the scenes. <a href="https://meta.stackexchange.com/questions/12527/do-i-have-to-worry-about-copyright-issues-for-code-posted-on-stack-overflow"><strong>Don’t just copy and paste random code from StackOverflow</strong></a>. Try to get deeper into it and understand line by line what the outcome of that code will be. Once you do, you can rewriting the whole thing in your own way.</p><p>The following resources should get you started:</p><ol><li><a href="https://tomassetti.me/oops-concepts/">OOP</a> (Object Oriented Programming) — <a href="https://en.wikipedia.org/wiki/Object-oriented_programming">Wiki</a></li><li><a href="https://deviq.com/don-t-repeat-yourself/">DRY</a> (Don’t Repeat Yourself) — <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">Wiki</a></li><li><a href="https://www.toptal.com/software/single-responsibility-principle">SRP</a> (Single Responsibility Principle) — <a href="https://en.wikipedia.org/wiki/Single_responsibility_principle">Wiki</a></li><li><a href="https://medium.com/@Mahmoud_Zalt/software-design-patterns-simplified-8a72232d52b1">SDP</a> (Software Design Patterns) — <a href="https://en.wikipedia.org/wiki/Software_design_pattern">Wiki</a></li><li><a href="https://stackoverflow.com/questions/268258/how-do-you-make-code-reusable">Code Reuse</a> — <a href="https://en.wikipedia.org/wiki/Code_reuse">Wiki</a></li></ol><h4>Keep Reading!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FRZnTaU1aKBjJm%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FRZnTaU1aKBjJm%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FRZnTaU1aKBjJm%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="370" frameborder="0" scrolling="no"><a href="https://medium.com/media/35a1fcd7ecdc0c95b12d22a53be37f38/href">https://medium.com/media/35a1fcd7ecdc0c95b12d22a53be37f38/href</a></iframe><p>Imagine you ordered a chair from Amazon, which you will have to assemble once it gets delivered. Before you start assembling, you’ll need to read the manual. You don’t necessarily need to, but if you do, you’ll definitely learn something that you don’t already know!</p><p>Similarly, you can’t just build something without going through the docs. You can even go on Github and read other people’s code. Read articles related to the language that drives you. The more you read about it, the better you get at it!</p><blockquote>“It is what you read when you don’t have to that determines what you will be when you can’t help it.” ~ Oscar Wilde</blockquote><h4>Fix The Wrong, Don’t Work Around It!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl49JKSBAQJbauc8dW%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl49JKSBAQJbauc8dW%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl49JKSBAQJbauc8dW%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/95d881af14691d99e1d33105789c57b2/href">https://medium.com/media/95d881af14691d99e1d33105789c57b2/href</a></iframe><p>You may come across lines of code written by either you or someone else, that were written according to the old requirements. Don’t be afraid to change those lines, even though the whole thing is already working and you don’t want to mess it up. Honestly, just change them! Rewrite the whole thing according to the new requirements.</p><blockquote>Life becomes better when you FIX your problems, not work around them!</blockquote><h4>Go Through Your Code!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FXGTDeZkw7gedO%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FXGTDeZkw7gedO%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FXGTDeZkw7gedO%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="227" frameborder="0" scrolling="no"><a href="https://medium.com/media/f09ceb31c20fc7ba3ab8eb33f6f18e47/href">https://medium.com/media/f09ceb31c20fc7ba3ab8eb33f6f18e47/href</a></iframe><p>Once your finish writing your code, go through it. You may even find a better way to do the whole thing. Then you’ll realize how stupid you were earlier to have coded that way.</p><p>Trust me, you’ll achieve a sense of personal pride after rewriting the old logic, making it cleaner and more readable.</p><h4>Learn To Comment/Document</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F8icI2JUxMRk88%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F8icI2JUxMRk88%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F8icI2JUxMRk88%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="235" frameborder="0" scrolling="no"><a href="https://medium.com/media/702c729fbdd5029dc3fc22fdbf6abfb3/href">https://medium.com/media/702c729fbdd5029dc3fc22fdbf6abfb3/href</a></iframe><p>Comments allow anyone else going through your code understand it better. If you have something like this in your code a = 2b + c, no one will know why you used this particular formula or what you are trying to achieve with it.</p><h4>Get Help From Your Team!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3oz8xWBaQ2147TBbgc%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3oz8xWBaQ2147TBbgc%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3oz8xWBaQ2147TBbgc%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff7c3908bc534099ed29198c4bae82a0/href">https://medium.com/media/ff7c3908bc534099ed29198c4bae82a0/href</a></iframe><p>You don’t necessarily have to poke your team for every small thing you don’t understand, but you do need to ask when in doubt. For example, you should ask questions such as:</p><blockquote>“What do you think is a better way of solving this?”</blockquote><blockquote>“Do you think this is the right approach?”</blockquote><blockquote>“Can we do this instead of that?”</blockquote><p>But let’s say you asked…</p><blockquote>“This was working before and for some weird reason, it isn’t now. I don’t understand. Can you help?”</blockquote><p>No! You should only ask if you are stuck on the problem for way too long, but it is your job to find out why it isn’t working.</p><h4>Give Back To Your Team!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FiV0CvfydE1Quk%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FiV0CvfydE1Quk%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FiV0CvfydE1Quk%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="290" frameborder="0" scrolling="no"><a href="https://medium.com/media/a78dbdaf22c0969456817de095c37696/href">https://medium.com/media/a78dbdaf22c0969456817de095c37696/href</a></iframe><p>It’s not a “take what you can, give nothing back!” situation. You must learn to share and contribute to your team. <strong>Help them out</strong>, because they are probably trying to figure out the answers to questions that you yourself used to struggle with a few weeks ago. And if you don’t know, you’ll probably learn something new!</p><h4>Define Your Own Patterns!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FKVZWZQoS0yqfIiTAKq%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FKVZWZQoS0yqfIiTAKq%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FKVZWZQoS0yqfIiTAKq%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/0bfa5649bd0e4910a87a2b17939fd71d/href">https://medium.com/media/0bfa5649bd0e4910a87a2b17939fd71d/href</a></iframe><p>Don’t be afraid to create your own design patterns. As you create your own patterns, you might figure out better ways of structuring your code. Who knows, you could be writing your own articles on Medium! That said, don’t forget to follow the defined standards. They are called “standards” for a reason.</p><h4>Improvise &amp; Learn From Criticism</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FZIqbJ5Tbm6N0I%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FZIqbJ5Tbm6N0I%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FZIqbJ5Tbm6N0I%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="248" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a49956f32d977fe1cded0ca787b07a8/href">https://medium.com/media/5a49956f32d977fe1cded0ca787b07a8/href</a></iframe><p>It’s a long and hard process, but you should always strive to improve yourself. Remember that you improve for yourself, not just for the company you work for. Just because you don’t get paid to throw out your own garbage, doesn&#39;t mean you don’t do it!</p><h4>Code To Inspire</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26FKXKky5wJ2dIIN2%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26FKXKky5wJ2dIIN2%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26FKXKky5wJ2dIIN2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/208ba94e03c0871edbb9e6761e823f30/href">https://medium.com/media/208ba94e03c0871edbb9e6761e823f30/href</a></iframe><p>Write your code in ways that inspire. You don’t need to build an entire framework to inspire someone. <strong>Just code better</strong> and eventually, you’ll become an inspiration or a person to look up to.</p><blockquote>Coding is a term specific to Computer Science, but that shouldn’t stop you from being creative while coding.</blockquote><h4>Be Responsible, Be Accountable</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl0HlLyNNgSaSuPO4U%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl0HlLyNNgSaSuPO4U%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl0HlLyNNgSaSuPO4U%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/66152435fe99f4d3cdc4d2c0c3ff3646/href">https://medium.com/media/66152435fe99f4d3cdc4d2c0c3ff3646/href</a></iframe><p>You are solely responsible for the lines you write. If something ever goes wrong, RELAX, no one is going to kill you. Just take your time and fix it. Your project/product manager should understand that humans are bound to make mistakes, because they have probably made several of their own mistakes in their lifetime.</p><p>That’s it! If you keep these simple things in mind, you are bound to do something great in your life.</p><p>It is important to understand that the purpose of this article is not to criticize anyone’s methods. The main point of writing this article is to help developers understand what is necessary for them (not financially, but personally) and what things to keep in mind to have an <strong>aspiring as well as an inspiring</strong> career. As developers, we must understand that we learn as we go and we are bound to make mistakes, even if we have error-friendly documentation.</p><blockquote><em>Not everyone can be Superman, but anyone can be a Hero!</em></blockquote><p><a href="https://crowdlinker.com/">Crowdlinker</a> wants every developer to have a success story to share. If you believe you already have one, tell us about your journey so far in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=527f0bad4bb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-crowdlinker-chronicle/create-your-developer-success-story-527f0bad4bb5">Create Your Developer Success Story</a> was originally published in <a href="https://medium.com/the-crowdlinker-chronicle">The Crowdlinker Chronicle</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>