baydakovss

agent-proxy — see the bloat in Claude Code's requests

A zero-dependency logging proxy that sits between Claude Code and the Anthropic API. It forwards every request untouched, streams the reply straight back (so the CLI is unaffected), and writes a readable Markdown document for each request — led by a ranked table of what is eating your context.

Run it

baydakovss

" Location for installing plugins
call plug#begin('~/.vim/plugged')

" Other plugins are specified with user/repo on Github or x.vim on vimscripts
" Git integration (status bar and commands like Gblame)
Plug 'tpope/vim-fugitive'
" Add info to sidebar about git
Plug 'airblade/vim-gitgutter'
" Add file-management commands like :Delete, :Move, and :Rename
Plug 'tpope/vim-eunuch'

baydakovss

/* Useful celery config.

app = Celery('tasks',
             broker='redis://localhost:6379',
             backend='redis://localhost:6379')

app.conf.update(
    CELERY_TASK_RESULT_EXPIRES=3600,
    CELERY_QUEUES=(
        Queue('default', routing_key='tasks.#'),

baydakovss

aws logs describe-log-groups | jq ".logGroups[].logGroupName" | grep -E "homeplus|mcdonalds" | xargs -n 1 -t aws logs describe-log-streams --query "logStreams[*].lastEventTimestamp" --log-group | jq "max/1000|floor" | xargs -t -n 1 date -r

# aws logs describe-log-groups | jq ".logGroups[].logGroupName" 
# Get LogGroup names

# grep -E "homeplus|mcdonalds" 
# (Optional) Filter LogGroup names

# xargs -n 1 -t aws logs describe-log-streams --query "logStreams[*].lastEventTimestamp" --log-group | jq "max/1000|floor"
# Get last event timestamp for each LogGroup. 

baydakovss

#!/bin/bash

# Assume the role using locally configured AWS credentials, then pass the assumed role to the container via environment 
# variables!

ASSUMED_ROLE=$(aws sts assume-role \
        --role-arn "arn:aws:iam::000000000000:role/our-role-to-assume" \
        --role-session-name "session_name" \
        --output text)

baydakovss

a4b.amazonaws.com
access-analyzer.amazonaws.com
account.amazonaws.com
acm-pca.amazonaws.com
acm.amazonaws.com
airflow-env.amazonaws.com
airflow.amazonaws.com
alexa-appkit.amazon.com
alexa-connectedhome.amazon.com
amazonmq.amazonaws.com

baydakovss

Frontend Masters: AWS for Frontend Engineers

You should have the following completed on your computer before the workshop:

• Install the AWS CLI.
• Have Node.js installed on your system. (Recommended: Use nvm.)
  • Install yarn with brew install yarn.
• Create an AWS account. (This will require a valid credit card.)
• Create a Travis CI account. (This should be as simple as logging in via GitHub).

baydakovss

docker node ls -q | xargs docker node inspect -f '{{ .ID }} [{{ .Description.Hostname }}]: {{ .Spec.Labels }}'

docker node inspect --pretty swarm
ID:                     xa56lddvm1la1i8f444zw4mop
Labels:
 - env=prod

baydakovss

docker run --name registry -p 5000:5000 --mount "type=bind,source=$PWD,target=/var/lib/registry" registry
docker: Error response from daemon: invalid mount config for type "bind": invalid mount path: 'C:/Users/user/sources' mount path must be absolute

# right way
export MSYS_NO_PATHCONV=1

# workaround - double //
source=//c//Users//user//sources//project

baydakovss

# Problem
# Mounting folders outside the users folder on windows is not working
cd ~/sources/../
docker run --rm -it -v .:/mnt alpine ls -1 /mnt
empty

# Workaround:
Since Docker Machine mounts Windows user folder we will deceive it.
# Windows
Move source folder to c:/Users/username/