Behavioral: Communicating on Remote Teams
Show how you default to written communication, provide context asynchronously, and keep distributed work moving across timezones.
Focused explanations and longer guides, with worked scenarios, common mistakes and interview exercises across every chapter.
Showing 97–120 of 825 articles
Show how you default to written communication, provide context asynchronously, and keep distributed work moving across timezones.
Negotiate from a researched range, discuss total compensation, and keep the conversation collaborative without ultimatums.
Make the case for paying down technical debt by tying it to incidents and velocity, and proposing small, incremental work.
Use build args for build-time configuration, keep secrets out of them, and understand how they interact with the cache.
Speed up image builds with BuildKit cache mounts, multi-stage builds and dependency-first layer ordering.
Start only the services you need with Compose profiles, and keep the default set small for focused local development.
Ship images without a shell or package manager, copy only the runtime, and accept the debugging trade-off.
Scan images for known CVEs in CI, set a policy that blocks the build, and rebuild when base images are patched.
Why the first process in a container must reap children and forward signals, and how to avoid zombies and ignored shutdowns.
Authenticate to private registries with credential helpers, pull secrets in Kubernetes, and scoped tokens.
Choose between no, on-failure, always and unless-stopped, and combine a policy with health checks to avoid crash loops.
Store ephemeral, sensitive data in memory with tmpfs mounts, and set size limits so memory use stays bounded.
Set, test and clear bits, exploit XOR properties, and count set bits with the Brian Kernighan trick.
What a detached HEAD is, when it happens, and how to keep commits made in that state.
Automate checks with client and server hooks, share them through a framework, and enforce the same rules in CI where they cannot be bypassed.
Track large binaries with Git LFS, keep pointer files in the repository, and plan for LFS storage and access.
Fetch less history and content with shallow and partial clones, and understand what you give up.
Understand remote-tracking refs, the difference between fetch and pull, and how tracking branches stay in sync.
Sign commits and tags, verify signatures, and enforce them to prove who authored a change.
Embed another repository with submodules or subtrees, and choose based on how often it changes and who owns it.
Mark releases with annotated tags, push them explicitly, and treat a tag as immutable.
Check out several branches at once in separate directories with git worktree, sharing one object database.
Reserve space for media with aspect-ratio, combine it with object-fit, and avoid the layout shift the old padding hack caused.
Style a parent based on its children with :has(), handle form states, and use it without hurting performance.
No notes match that… try another filter.