plotly VS Nest

Github: https://github.com/plotly/plotly.py

First we need to install the Plotly. To create some very dynamic graphics, this tool helps a lot.

my good dude wake up and smell the plotly. Knowing the ins and outs of matplotlib is helpful but doing interactive stuff with jupyter I always use plotly.

Plotly documentation (https://plotly.com/python/)

I don´t know your workflow, but I use 2 markdown based presentations: obsidian advance slides and Quarto presentations. The former is a plugin for Obsidian, which is the software I use to take all my notes, write my thesis, etc., so It makes it extremely easy to make presentations since all my information is in Obsidian. In the other hand, Quarto is a publishing system (articles, presentations, websites books) that can be easily integrated with python and R. This makes it supper convenient for showing my data to my PI since I can analyze my data and at the same time make a presentation for the data. Besides this, Quarto also integrates with my Zotero library, so I can insert citations. Lastly, one thing that made my Quarto presentations infinitely better that the powerpoints, Is that I can insert interactive graphs with plotly, so when I'm showing my data, my PI is able to explore the data inside the presentation.

Plotly GitHub repository: https://github.com/plotly/plotly.py

I'm using plotly.py now. This is why I love this community.

Depending on the nature of your reporting requirements, you could output a formatted Excel document with Python and a library such as openpyxl, and shove that into your SharePoint environment. This would be less dynamic than PBI reports can be, but may be sufficient. If you want viz as well, you can use something like ggplot or Plotly. Again, less dynamic than PBI for the same effort.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/