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.
fly apps move <app-name> --org <target-org>bd dolt start
bd dolt status # note the port numberConnection Name: <name-here>
Type: MySQL/Dolt
URL: :<port>/beads.beads/dolt/ and synced to GitHub via invisible refs (refs/dolt/data).brew install beads
sudo bash -c 'curl -L https://github.com/dolthub/dolt/releases/latest/download/install.sh | bash'
mkdir -p .beads/dolt
dolt clone git+https://github.com/<org>/<repo>.git .beads/dolt/beads
bd dolt start
bd listbd ready # see available work
bd list # all issues
bd show <id> # issue details
bd create --title="..." --type=task --priority=2 # create issue
bd update <id> --claim # claim work
bd close <id> # complete workbd dolt pull # pull teammate's issues
bd dolt commit # commit pending changes
bd dolt push # push your issues[
{"name": "Alice"},
{"name": "Bob"}
]{"name": "Alice"}
{"name": "Bob"}decoded = { "user_id" => 1 }
decoded[:user_id] # => nil ❌
decoded["user_id"] # => 1HashWithIndifferentAccess which removes this mismatch:payload = HashWithIndifferentAccess.new(decoded)
payload[:user_id] # => 1
payload["user_id"] # => 1params works the same way internally.HashWithIndifferentAccess is a class provided by ActiveSupport, so it exists only in Rails, not in core Ruby. It internally normalizes all keys (by storing them as strings) while allowing access using either symbols or strings. It’s designed specifically for boundary data—like JSON responses, JWT payloads, and request params—where key formats are inconsistent. By removing the need to care about key types, it prevents subtle nil bugs without forcing changes in how the rest of the code is written, which is why Rails uses it internally for paramsChat that has many Messages—you can create a message using @chat.messages.build instead of instantiating Message.new. This automatically sets the chat_id on the message, so it’s never niland the association is correctly maintainedon.schedule field. It uses UTC time format.on:
schedule:
# Runs at 5:30 AM and 5:30 PM UTC every day
- cron: '30 5,17 * * *'
# Runs every 15 minutes
- cron: '*/15 * * * *'
# Runs every Monday at 9:00 AM UTC
- cron: '0 9 * * 1'┌───────── minute (0–59)│ ┌─────── hour (0–23)│ │ ┌───── day of month (1–31)│ │ │ ┌─── month (1–12)│ │ │ │ ┌─ day of week (0–6, Sun=0)│ │ │ │ │* * * * *Highlight.jspnpm add highlight.jsimport hljs from 'highlight.js';
import 'highlight.js/styles/atom-one-dark.css';
const code = `function sum(a, b) { return a + b; }`;
const { value, language } = hljs.highlightAuto(code);
console.log(language); // e.g. "javascript"
console.log(value); // highlighted HTMLvalue to your React component and render it inside a code element with the hljs class for styling.master or main) using a single command:git branch --merged | egrep -v "(^\*|master|main)" | xargs git branch -dShowing page 1 of 83
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.