segregation | R package to calculate entropy | Analytics library

I keep my service interfaces as lean are possible, normally they are @FunctionalInterface. I try to follow there the interface segregation principle.

Is a good practice that my service implementation implements multiple interfaces if they share most of there dependencies? or should I create a separate implementation for each interface?

I have an excel sheet with following columns and values:

Master sheet before segregation of data year wise manually: Workbook for all years

Master sheet after segregation of data year wise: Workbook 2020

My excel contains 10000 plus lines like this.

Now, I do a pivot and apply Project ID in the filter section of pivot and arrange the 3 remaining columns in the following manner:

Pivot sheet Column format after filtering it by project ID is as follows:

Now with this data, following are my steps to achieve needed result:

1. Segregation of workbooks by year and creation of separate excel worksheets inside each workbook based on ProjectID number.
2. I create sheets based on all unique project IDs I have in master sheet. With name of the sheet being project ID (Example - My sheet name will be 1001, 1002, 1003, etc)
3. I would like to copy the pivot filtered data according to project ID and put it in corresponding sheet names.

I already did, Step 1. Manually with help of data filters option in excel, Step 2. with a VB code below:

I'm using xslt to transform xml to html. Here is .xml file.

I have a website that has multiple pages and uses Firebase as backend. I've already implemented firebase auth for the login and I have knowledge of using onAuthChangeState. The problem is now I am trying to find a way to stop the users from accessing other pages without the login page. I want to have some kind of like a "session or token" in php that acts as a key in order for the user to access the page. NOTE! I did not use php because I am also using firebase as a means for hosting my site. BTW Most of the sources I saw only uses a single page and uses a lot of style.display = "none or block", I don't want to go this route, As I like to be more organized and have a proper management in terms of code segregation. That is why I have multiple pages eg; Login.html, Page2.html.

I know how to use javascript redirect

I have been learning lately about microservices architecture and it's features. in this source it appears that event sourcing is replacing a database, however, it is later stated:

The event store is difficult to query since it requires typical queries to reconstruct the state of the business entities. That is likely to be complex and inefficient. As a result, the application must use Command Query Responsibility Segregation (CQRS) to implement queries.

In the CQRS Page the author seems to describe a singular database that listens to all events and reconstructs itself.

What is actually needed to implement event sourcing with a queryable database? particularly:

Where is the events database? Where is the queryable database? Do I need to have multiple event stores for every service or can I store events in a message broker like Kafka? is the CQRS database actually is one "whole" database that collects all the events? And how can all of this scale?

I'm sorry if I'm not clear with my question, I am very confused myself. I guess I'm looking for a full example architecture of how things will look in the grand picture.

Is there a way to tell Git to create packfiles based on file types, and to specify the delta-ification and zlib compression for those classes / types?

I have a rather large repository, much of which is composed of image assets and translation files (.po), the latter actually being the largest fraction of the working copy and the repository data.

• For the image assets, neither delta nor zlib compression are useful: the images are already compress (so they don't compress well under zlib) and delta compression does nothing useful when small changes tend to cascade through the compressed image (and are rare anyway, usually once the asset is committed it's either left alone forever or replaced wholesale).
• For the PO files, while they're technically text files I would expect them to delta-compress very badly for this specific repository: the historical generator / exporter would export the translations in essentially random order so from one export to the next it's as if the entire file has been rewritten.

As a result, when the repository is repacked I'd like to try packing the images together neither delta-compress nor zlib-compress them, and the PO files together and zlib-compress them (at the maximum possible level) but not delta-compress them. This way they ought not waste cycles on useless compression work, and should avoid polluting the compression of more "normal" code files.

However my previous experiments in packfiles did not go well. Is there builtin support for this sort of segregation & configuration which I missed, or would I need to build the packs by hand using low-level commands or even libgit2 directly?

I am new to Programming and started learning Python recently. I really appreciate your help regarding this issue!

I have a list of two sub-lists containing two items in each. I also have another list called Parts that dictates the segregation of those items. While the below codes seem to work properly, but don't do the job right when the sublists of the Parts(partition sizes) list are the same/identical. Need some expert help or advice.

Note: The sum of int in the Parts sublist is equal to the length of the corresponding Items sublist.

Screenshot of the Issue

Written Code is below:

I got a list that contains 9 data frames and each data frame contains the following lines:

I am planning to use Azure boards as ALM tool. I need to segregate users who can create Epic, Features or User Story in Azure boards. Team A will consists of business stakeholders and should have access to create Epic, Team B consisting of Product owners should have access to create Features, and Team C consisting of developer should have access to creation and modification of user story.

I have inherited default agile process type. Is it possible to attain this level of permission segregation in Azure Boards?

Thank you in Advance.