uzbekdev1

public class Solution {
    public int CalPoints(string[] ops) {
        var score = new List<int>();

        for (int i = 0; i < ops.Length; i++)
        {
            string c = ops[i];

            if (c == "+")
            {

uzbekdev1

# Method: POST
# Headers
# Authorization Bearer eyJhbGciO... (access token)
# Content-Type: application/json

# Body
# {
# 	"username": "test-user",
# 	"groups": ["Comp1"], // doesn't work, even if it is in the docs
# 	"lastName": "test",

uzbekdev1

//ConfigureServices

services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
.AddJwtBearer(options =>
{
	options.MetadataAddress = "https://{host}/auth/realms/{realm}/.well-known/openid-configuration";
	options.RequireHttpsMetadata = true;
	options.IncludeErrorDetails = true;
	options.SaveToken = true;

uzbekdev1

private void btnDecrypt_Click(object sender, EventArgs e)
        {
            byte[] data = Convert.FromBase64String(textBox4.Text); // decrypt the incrypted text
            using (MD5CryptoServiceProvider md5 = new MD5CryptoServiceProvider())
            {
                byte[] keys = md5.ComputeHash(UTF8Encoding.UTF8.GetBytes(hash));
                using (TripleDESCryptoServiceProvider tripDes = new TripleDESCryptoServiceProvider() { Key = keys, Mode = CipherMode.ECB, Padding = PaddingMode.PKCS7 })
                {
                    ICryptoTransform transform = tripDes.CreateDecryptor();
                    byte[] results = transform.TransformFinalBlock(data, 0, data.Length);

uzbekdev1

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

uzbekdev1

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

uzbekdev1

# -------------------------
# HTACCESS FILE
# -------------------------

AddDefaultCharset utf-8
Options +FollowSymLinks

# RESTRICTIONS
# Disallow direct access to this file and any log / cache file
# Prevent directory browsing

uzbekdev1

# Dokcer info
docker info

# create custom bridge network
docker network create mynet
docker network inspect mynet

# rabbit1 is hostname , erlang cookie is defined to facilitate cluster

#Node 1

uzbekdev1

bcdedit /set hypervisorlaunchtype auto

uzbekdev1

services.AddControllers().	(options =>
{
	options.SerializerSettings.DateTimeZoneHandling = DateTimeZoneHandling.Local;
});