At Codemancers, we believe every day is an opportunity to grow. This section is where our team shares bite-sized discoveries, technical breakthroughs and fascinating nuggets of wisdom we've stumbled upon in our work.
:inline it does not depends upon a scheduler anymore. Use perform_later as per your requirements and that will perform the job instantly.
psql postgres if we face the below error:psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file or directorybrew services start postgresql@15 Bootstrap failed: 5: Input/output error
Try re-running the command as root for richer errors.
Error: Failure while executing; `/bin/launchctl bootstrap gui/501 /Users/<user>/Library/LaunchAgents/[email protected]` exited with 5.brew services stop postgresql@15 rm -f /opt/homebrew/var/postgresql@15/postmaster.pid (apple sillicon install it at opt/homebrew)brew services start postgresql@15 brew services info postgresql@15config.hosts << "www.example.com"
CIDR Block(Classless Inter-Domain Routing) 
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name -f output-file.sql``
pg_dump with DROP table queries (clean dump):
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --clean -f output-file.sql
pg_dump for schema only:
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --schema-only -f output-file.sql
pg_dump for data only:
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --data-only -f output-file.sql
pg_dump for data only (no schema, INSERT commands only):
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --data-only --inserts -f output-file.sql`sidekiq-scheduler if your schedule file is named as sidekiq.yml make sure to add the schedule config entry.:scheduler: -> :schedule .:scheduler:
:schedule:
fetch_user_info_from_slack:
cron: '0 6 * * * Asia/Kolkata'
class: FetchSlackUserInfoJob
queue: 'default'
description: 'This job fetches user info from slack and updates the database'same AMI, you should first ensure that the AMI is available in both regions. If it's available in both regions (i.e.- "us-east-1" and "us-east-2") , you can proceed to use the same AMI for both instances. Otherwise, you should use two different AMIs.provider "aws" {
alias = "us-east-2"
region = "us-east-2"
}
resource "aws_instance" "instance" {
provider = aws.us-east-2
ami = "ami-id-1"
instance_type = "t2.micro"
}
provider "aws" {
alias = "us-east-1"
region = "us-east-1"
}
resource "aws_instance" "instance1" {
provider = aws.us-east-1
ami = "ami-id-2"
instance_type = "t2.micro"
}Git rebase is a command to reapply commits from one branch onto another, effectively rewriting the commit history.git rebase main to start.git add <file>.git rebase --continue.git push <remote> <branch-name> —-force.
<<-EOF and EOF are Terraform's heredoc syntax, This syntax enables the creation of multiline strings in Terraform configuration files without the need to manually insert newline characters (\
).
terraform showhcl
provider "aws" {
alias = "us-east-2"
region = "us-east-2"
}
resource "aws_instance" "example" {
provider = aws.us-east-2
ami = "ami-id"
instance_type = "t2.micro"
}
provider "aws" {
alias = "us-east-1"
region = "us-east-1"
}
resource "aws_instance" "example1" {
provider = aws.us-east-1
ami = "ami-id"
instance_type = "t2.micro"
}AWS EC2 instance.provider "aws" {
region = "us-east-2"
}ngrok to expose your localhost , you can serve that in a static domain.ngrok http --domain=<your-domain>.https://ngrok-free.app|ngrok-free.app <port>curl -sLO https://github.com/tailwindlabs/tailwindcss/releases/latest/download/tailwindcss-macos-arm64
chmod +x tailwindcss-macos-arm64
mv tailwindcss-macos-arm64 tailwindcss./tailwindcss init // this will create tailwind.config.js file./tailwindcss -i input.css -o output.css --watch // this will generate a output.css file, so make sure to link it in your root file--minify flag./tailwindcss -i input.css -o output.css --minify
touch filename : Used to create an empty file .git remote : The command is used to manage remote repositories.git reset HEAD~1 : Removes the most recent commit from the current branch without modifying the working directory.git pull origin branch_name : Fetches changes from the specified branch (branch_name) on the origin remote repository.upsert_all or insert_all are used. They will be directly converted to raw sql queries and executedShowing page 17 of 42
AI is everywhere but it's unclear which investments will actually move your metrics and which are expensive experiments.
Most AI projects fail at the data layer. Pipelines, quality, access all need work before LLMs can deliver value.
Your engineers are shipping product. They don't have capacity to also become AI specialists with production-grade experience.
Aging, undocumented codebases make AI integration slow, risky, and expensive. They need to move first.