Recommended Partitioning/Disk software for combining multiple hard drive images as respective boot partitions on one hard drive

I have three separate bootable hard drives running their own respective versions of Windows 10 each with different proprietary software on them that do not mix with each other due to specific requirements for each. Therefore, rather than to have three separate laptops, I wish to image each of these hard drives to one NVME drive on a tablet I purchased for this.

What is the best software for this?
Does it matter if the drives are UEFI or BIOS as long as they are all the same?
Any other hiccups anyone foresees?

applications – When sending an MMS, how are the recommended contacts populated?

So – my girlfriend went to send a video and I noticed that another guy’s name popped up when sending the MMS as a recommended recipient. To my knowledge as a techie, the algorithm selects only contacts that you’ve been in touch with.
The options were from different apps and this one in particular from Twitter. She said she had no clue but I am wondering the opposite.

What would my fellow techies say? I.e you select a video file on your android to send and contacts populate from various sources.

performance tuning – A Function of Arguments or a Function of a List of those Arguments – Which is Recommended?

Which is recommended from a programming perspective and has better performance in memory and speed given guaranteed identical output – a function taking many arguments and then referring to those arguments directly or a function taking a single list containing those arguments as elements and then referring to those elements using Part()?

That is, if n is large or f is called many times, which of the following is better to use given the output is the same?

f(x1_,x2_,...,xn_):=(*body refers to x1,x2,...,xn directly*)

or

f(list_):=(*body calls list((1)),list((2)),...,list(n)*)

For small n, standard practice is to use the former, but I am wondering if things change for very large n.

ergonomics – Which screen PPI / scaling is recommended for a computer display?

This is a tricky one to answer!

Firstly, DPI and PPI aren’t the same thing conceptually. One is a measure of the dots per inch on a printed output and one the pixels per inch of a digital display.

I believe as a result you’re kinda talking cross purposes. The windows DPI setting of 96 is the default https://support.corel.com/hc/en-us/articles/115001485408-Display-Options-How-to-change-DPI-Scaling-Level-for-displays-in-Windows-10-#:~:text=DPI%20setting%20controls%20the%20size,has%20setting%20of%2096%20DPI.

And by changing this what you’re effectively doing is scaling a ratio (as I understand it) the number of “dots” (which doesn’t make much sense in digital displays) which would make up an inch (I assume, given the windows dialog) of screen. What this results in, (by reducing DPI) is more pixels representing the same inch that 96 would have, thereby given a fixed hardware resolution display making the screen elements appear smaller.

As a side point, Windows 10 has done away with this dialog and shows interface scaling as a percentage.

So, context aside, your original question asks what the optimum PPI / scaling is recommended for reading a typical computer display. What you’re asking is at least two questions.

The reason it’s at least questions is that the output “size” of text on screen is a function of both PPI and scaling. For example, a 24″ 4k monitor with a high DPI and scaling of 200% will look identical (in size) to a 24″ 1080p monitor with a scaling of 100%. The 4k monitor will look sharper at this setting because there are 2x the pixels per inch and techniques like pixel rounding and smoothing are less pronounced.
This is especially true of mobile devices which may have a very high hardware PPI, but internal scaling (on android its just “smallest to largest” which they control. I’m not aware of the technical scaling factors used here, I cite it to illustrate that different devices handling scaling differently in their terminology.

Finally, we come to “optimum” there are many ways to look at this:

  • Minimum text size to meet WCAG accessibility guidelines, but beyond this, recommended best practice for “base” font sizes. 9pt/12px has been given as the literal minimum before you starting failing A11y checks and should certainly not be used for body text for example where something close to 16px as a minimum would be recommended.
  • Optimum font spacing, line lengths and justifications, for readability (https://www.w3.org/TR/WCAG21/#visual-presentation)
  • Optimum for your content, userbase and use cases -For example if you’re expecting users to read in specific environmental conditions, you should consider this

Those three points alone could warrant and answer each, all longer that this answer!
DPI as a number in that context is largely meaningless, because it’s a measure from a single OS 20 years ago.

In summary, there is no optimum, scaling is a user controlled preference and should be treated as such, if a user chooses to change it, you should accommodate it (https://www.w3.org/TR/WCAG21/#resize-text).

ergonomics – Which screen DPI / scaling is recommended for a computer display?

Assuming a font size of 9 pt (pretty widespread minimum font size), what PPI / scaling is recommended for reading it from a typical computer display? Is the 96 PPI standard close to optimal, or is it just a legacy of old days when higher display PPI were not possible?

Windows dialogs certainly suggest it’s the optimum:
enter image description here

mysql – Is this method for loading data in a C# application recommended?

Add a Repository layer which would be between Data and Service layers. Never use Service directly to Data layer. The Service layer suppose to hold the business logic that would be applied on the Repository layer. Each Service can work with one or more repositories, but each repository should only work with one entity.
Here is an example :

public class PersonRepository
{
    public List<Person> GetPeople() { /* Dapper code here */  }

    public void InsertPerson(Person person) { /* Dapper code here */  }
}

public class PersonService 
{
    private readonly PersonRepository _personRepo = new PersonRepository();
    
    public List<Person> GetPeople() 
    { 
        // if there is some business logic needed 
        // you can add it here 
        return _personRepo.GetPeople();
    }
    
    public List<Person> InsertPerson(Person person)
    { 
        // if there is some business logic needed 
        // you can add it here 
        _personRepo.InsertPerson(person);
    }   
}

Each Repository should validate the object against the entity requirements (e.g. database table).

Each Service should validate the object against the business logic requirements.

In your view model, class properties should be at the top of the class not in between, and sort them by private properties first, then public properties comes after.

This part :

 // Contructor
public MainViewModel()
{
    // Create database service and assign it to the readonly property
    DatabaseService databaseService = new DatabaseService();
    _databaseService = databaseService;

    LoadData();

    InsertDataCommand = new RelayCommand(InsertData);
}
   
// Load data method
protected void LoadData()
{
    if(People == null)
    {
        People = new ObservableCollection<Person>();
    }
    People.Clear();
    _databaseService.GetPeople().ForEach(record => People.Add(record));
}

can be simplified by this :

 // Contructor
public MainViewModel()
{
    _databaseService = new DatabaseService(); 
    LoadData();
    InsertDataCommand = new RelayCommand(InsertData); 
}

// Load data method
protected void LoadData()
{
    People = new ObservableCollection<Person>(_databaseService.GetPeople());
}

proxmox – What would the recommended setup for a high-availability cluster in our startup?

We’re planning our setup using Proxmox and were hoping to get some feedback as to how good of an idea is it:

So our current setup is 4 servers with wildly different specs:

  • All of them have 2x Intel(R) Xeon(R)

  • All of them have either 128GB or 512GB RAM

  • All of them have at least one hardware RAID storage of varying specs and size

  • All of them have at 2 other drives of varying specs

  • One of them randomly shuts down for reasons to be inspected

  • All of them reside in one rack

All of which will be running Proxmox

Our goal is hosting of:

  • Internal Services (Git, Matrix)
  • Legacy client projects ( Mail servers, static websites )
  • New projects ( Dynamic websites, requiring databases, persistent storage etc )

We want to be resilient against failures of any hard drive, RAID or entire server. We are currently en route to deploy with Nomad and Ceph.

For the company however, it is important to offer a certain ease of use for the non-DevOps programmers – i.e. ability to deploy an app without having to know the details of the cluster. ( That was the initial reason Kubernetes was rejected, because of complicated setup of new apps ). That is not possible afaik on our current setup either .

What would be the best course of action for us in this scenario? Disregard our current path (Nomad, Ceph), if there is a easier, more functional way, we will take it.

Our questions mainly are:

  • What would be the an appropriate orchestration software for our case ( we are currently split between Kubernetes and Nomad ) ?

  • What would be an appropriate storage solution for our case? ( Ceph vs ZFS pools maybe?

  • What would be an appropriate DevOps automation pipeline?

    • Due to the ease-of-use by programmers, we would require to be able to deploy an app, test it, allocate storage and other resources, without the knowledge of the cluster.

Thank you

Is it recommended to install other applications in SharePoint Servers Farm?

The management want to combine all the test applications inside one server to reduce the cost of test servers and test environments. So all stand alone applications such as ASP.NET web applications, ASP.NET Web services will be moved to the SharePoint Farm. Is it good practice to move them here and what are the implications? considering this is test environment.

Is it recommended to create Office 365 groups to manage the users permissions on SharePoint sites

In on-premises world, we use to create security enabled distribution lists to manage the users’ permission inside SharePoint sites. but inside Office 365 we get these options for granting users’ permissions inside SharePoint sites:-

enter image description here

So is it fine/recommended to create separate Office 365 groups just to manage the users’ permission inside SharePoint sites? or it will be overhead? as currently we only have 2 communication SharePoint sites, so is it fine if we create 10 Office 365 groups to add them to different libraries and lists inside the 2 communication sites? I know that creating Office 365 group will automatically create a SharePoint modern team site, so that why i am asking f this will be an overhead in our case..