Dr Alexander Mikhalev AlexMikhalev

Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
NEVER edit .env or any environment variable files—only the user may change them.
Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
Moving/renaming and restoring files is allowed.
ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't really have SREs and they make engineers pretty much do everything,

Problem

When I use docker to work with the shared workspace with host under Ubuntu, I find that files created by docker user is owned by root. This is not the same with macOS.

Maybe this is becuase docker is run by root user and the default user mapping mechanism is to map container-root to host-user or host-root. So can I map the container-root or container-any-user to host-current-user?

Fortunately the latest docker supports the re-map the container user to any host user via Linux namespace. Refer to this.

	#![allow(unused)] // silence unused warnings while exploring (to comment out)

	use std::{error::Error, str};

	use s3::bucket::Bucket;
	use s3::creds::Credentials;
	use s3::region::Region;
	use s3::BucketConfiguration;

	// Youtube Walkthrough - https://youtu.be/uQKBW8ZgYB8

	# github生成的两把钥匙
	client_id = 'e3a53e8921975c37fe3d'
	client_secret = '739a252f5022855aadcc832a2facd86b1b836ef6'
	from flask import Flask, \
	redirect, \
	jsonify
	from furl import furl
	import requests
	import json
	from flask import request

	config:
	aws:region: us-east-2
	my-project:HASURA_GRAPHQL_DATABASE_URL:
	secure: <snipped>

	from transformers import BertForQuestionAnswering
	import torch

	bert_name = "bert-large-uncased-whole-word-masking-finetuned-squad"

	model = BertForQuestionAnswering.from_pretrained(bert_name, torchscript=True)
	model.eval()

	inputs = [torch.ones(1, 2, dtype=torch.int64),
	torch.ones(1, 2, dtype=torch.int64),

	#!/bin/bash
	#json per line (same result, but for example can use jq to set _id)
	7z x -so $1 \| jq -c . \| couchimport --db mydb --type jsonl

Dr Alexander Mikhalev AlexMikhalev

Table of Contents

Problem

Linux namespace