alexruzenhack

CREATE FUNCTION dermage_regua.gender(currentGender varchar(1)) RETURNS varchar(1) CHARSET utf8
BEGIN
	declare gender varchar(1);
	IF currentGender IN ('F','M') THEN SET gender = currentGender;
	ELSE SET gender = 'F';
  	END IF;
	RETURN gender;
END

alexruzenhack

Verify services

Status of all services:

service --status-all

Status of any service:

service wildfly status

alexruzenhack

Rails assets per controller

Check if asset exists with find_asset before include it.

<!-- Include javascript per-controller - vendor plugins -->
<%= javascript_include_tag params[:controller] 
        if ::Rails.application.assets.find_asset("#{params[:controller]}.js") %>

alexruzenhack

USE [nomeSeuBancoDeDados];
CHECKPOINT;
GO
CHECKPOINT; -- run twice to ensure database file wrap-around last transactions
GO
-- 200 MB
DBCC SHRINKFILE(nomeSeuBancoDeDados_log, 200);

alexruzenhack

-- step 01 - Set the database into emergency mode
ALTER DATABASE yourDatabase SET EMERGENCY;

-- step 02 - Emegency mode repair
ALTER DATABASE yourDatabase SET SINGLE_USER
DBCC CHECKDB(yourDatabase, REPAIR_ALLOW_DATA_LOSS);

-- steop 03 - Unlock the database setting it into multiuser again
ALTER DATABASE yourDatabase SET MULTI_USER;

alexruzenhack

-- ============================================================================
-- 1. Limitamos o tamanho do log a 200MB com variação de 50MB;
-- alter log size of database
USE [yourDatabase];
GO
ALTER DATABASE [yourDatabase]
  MODIFY FILE
  (NAME = yourDatabase_log,SIZE = 200MB, FILEGROWTH = 50MB);
GO

alexruzenhack

public enum Status {
	P("Pending"),
	A("Approved");

	private String name;

	Status(String name) {
		this.name = name;
	}

alexruzenhack

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

alexruzenhack

Tutorial

• Customomizing ASP.NET Core Part 01: Logging

Comparizon between providers

• NLog vs. log4net vs. Serilog
• NLog vs log4net vs Serilog: Compare .NET Logging Frameworks

Stackoverflow

alexruzenhack

1. Criar nova branch com as alterações realizadas na base do código
   • git checkout -b <branch name>
2. Adicionar alterações na staging area
   • git add <. para adicionar tudo | path endereço do arquivo>
3. Criar um commit descritivo da tarefa realizada, dos arquivos alterados
   • git commit -m "Descrever atividade"
4. Puxar alterações da master para o repositório local
   • git pull origin master
5. Atualizar a branch com as alterações da master, se existirem alterações

• git merge master