Best Practice – What are the most commonly understood characters / symbols for chat interactions?

As you mentioned earlier, different icons are used in different apps. This makes it difficult to determine a generally understandable standard. I remember Jakob Nielsen saying, "Users have spent most of their time on other websites." With this attitude, Here's what I would do::

  1. Identify the target user group for the app you are designing for and
  2. Understand which messenger / chat tool you are most likely to be used to. then
  3. Design symbols that are very similar to those of the most popular messenger for the target group

Example:

WhatsApp appears to be the world's most widely used messenger [data] by number of users. However, if your target audience is primarily based in China, WeChat will most likely be used frequently. So you can use WeChat to inspire your icon designs. These designs could be tested with real users to make sure they understand the interactions supported by the symbols.

You can also view text only as an alternative to symbols or symbols in connection with a text label.

c – Dereferencing invalid ** exactly like (int) – standard practice?

I tried printing the return value of a thread and found that the term double blank pointer still confuses me.
My understanding was that a void * is a pointer to any type of data that can be dereferenced with an appropriate conversion, but otherwise the "levels" of referencing are preserved as with regular typed pointers (ie you cannot expect them to be the same Value you get put in**(int **)depth2 by dereferencing it just like once *depth2. ).

However, in the code (below) that I scraped together for my thread return printing, it seems that I am do not dereference a Empty pointer if I only occupy it (int). Is this a case where the address is used as a value – if so, is this the normal way to return from threads? What else am I missing?

(I'm aware that the safer way to manipulate data within the thread can be caller-level storage, but I'm fairly interested in this case and what I don't understand about the invalid pointer)

Thanks a lot!

#include 
#include 
#include 


void *myThread(void *arg)
{

    return (void *)42;
}

int main()
{
    pthread_t tid;
    void *res;                                        // res is itself a void *

    pthread_create(&tid, NULL, myThread, NULL);
    pthread_join(tid, &res);                          // i pass its address, so void** now
    printf(" %d n", (int)res);                       // how come am i able to just use it as plain int?

    return 0;
}

Best Practice – What are the most commonly understood characters / symbols for chat receipts?

I'm designing an in-app chat feature that allows users to get live support from chat agents

My question is what are the most commonly understood characters / symbols for chat records like

  1. Send
  2. cleverly
  3. not sent
  4. delivered
  5. not delivered
  6. read

I see that WhatsApp uses ticks and double ticks to change color when reading while Facebook Messenger users do something else. What would be more common practices if you design for it without complicating things? Are all of these receipts needed?

Multi-factor – is using desktop 2FA clients like Authy Desktop a good practice?

Basically, 2FA is based on the idea that using a service requires not only something that you own, but also something that you own.

I'm pretty confident that this offers pretty good security, especially when used on iOS (which has better system-level app separation). However, I'm not sure if I should add a desktop 2FA utility.

As I understand it, an attacker would have to intercept my password (probably through a keylogger on my desktop computer where I log in the most) and access to my phone or the key stored on my phone. But I can probably imagine that someone who can set up a keylogger could steal enough information to reuse any 2FA system available on my desktop computer.

When I write this, I understand that this is based on the perception that:

Computer integrity <phone integrity <iOS integrity

Computers are more likely to be damaged by the garbage heap that I install on them and their more important "openness" to system changes.

Smartphones have a more restrictive ecosystem and a shorter lifespan, which reduces the likelihood of infection.

Comparatively, iOS is the most closed ecosystem in which, unlike Android, most accesses are not opened in the API and the app check is more thorough.

Python – best practice for configuring the dynamically generated file

I created the file like this in views.py.

csvDir = 'exportedCsv/'
file_path = csvDir + 'test.csv'
df.to_csv(path_or_buf=file_path,sep=',',float_format='%.2f',index=False,decimal=",",encoding='utf_8_sig')

Generate a file dynamically and enter the file path in HTML.

Now there is my file in /exportedCsv/test.csv

However, I have no way to access it via HTML.

My idea is fundamentally wrong ???

What should I do if I want to create a CSV file and let the user download it?

GUI design – is it bad practice to use button styles for text input?

I was recently introduced to a user interface that uses bootstrap button classes to style text input, e.g. E.g. Https://jsfiddle.net/k7g2Lv43/

I personally really don't like it and I think it shouldn't be done, but I couldn't explain why, so I said nothing (I'm not a UX / UI designer).

Is it bad practice and if so why?

Website Designing – Designing With Your Customers: Good Or Bad Practice?

There is nothing wrong with customers creating their own designs. In fact, this can be very useful, but be aware …

… if they feel that the designs are useful in practice and not, it could jeopardize the relationship.

Some customers like to show and talk about examples of the competition, others create Excel spreadsheets with requirements, others like to draw their ideas on paper, others create complete designs themselves, etc. etc. It is just another way of communicating what they want and / or need. And that's good! But stay ahead of all difficulties and be clear and honest from the start. Tell them that you are only using the material they created as a reference for your own designs. They don't want customers to insert hours and hours into a design that they believe will be used when it isn't. Still leave a door open, especially if you don't have much experience. If your designs are good enough to use parts of them unchanged, you might be able to learn something from them too :]

Accessibility – Best Practice for Abbreviated Words in Navigation Links?

If a smartphone user increases the font size on our website, I consider changing the text of navigation elements to an abbreviated "short text" version, e.g. For example, "Continuing Professional Education (CPE) ratings" would be changed to "CPE ratings". For accessibility reasons, should a screen reader read the full text and ignore the short text – or should the screen reader simply read the short text? In some cases, the abbreviated text sounds strange when read aloud, e.g. B. "Orntn" for "orientation".

What is the simplest version of the best practice application architecture for a backend in C # and ASP.NET Core WebAPI?

I know that in some contexts DDD, CQRS and EventSourcing are the best course of action, but in my case this would be too complicated for two reasons:

  • My team is a beginner and we want them to be productive as early as possible
  • It's really easy to use, but obviously the complexity can increase over time

This question is an attempt to reformulate this question: what is a simple implementation of the onion architecture for C # ASP.NET Core WebAPI and SQL db that is not fully DDD and CQRS?

My previous thoughts are:

  • Using onions or neat architecture is better than the old n-tier model and not difficult to learn. This makes it easier to test the domain entity level
  • The API should not return data as objects of the domain entities, but should be assigned to separate view models

I'm not sure whether to design the database and SQLs manually and then use Dapper or use something like EntityFramework Core code first.

I wonder if CQRS would be a good idea without DDD.

I would also like to say a little about our simple application. It is intended for an amusement park where seasonal workers in various departments have to undergo some training. You should be able to register for a course, cancel your registration, and the instructor in charge of the course should be able to mark your registration with participation and approval. There are also some reports that read and display all of this data. This is version 1.

Version 2 is an admin dashboard for registering users as trainers and administrators (who can view all reports). Administrators should also be able to map which departments need which training.

Perhaps many will consider this to be opinion-based, but I believe that it should be possible to define a few broad steps in a tutorial about the application architecture, and although the exact order may be controversial, I expect some kind of consensus on which steps to take should be considered. So that's my question; What specific topics / learning steps are there in this context in the application architecture about simple layering, n-tier and onion / clean – and under CQRS, DDD EventSourcing?