xOtanix

Maksym Kryva

@xOtanix
GitHub Profile
casual and pragmatic
Pragmatic and direct reviewer who prefers efficiency over formality. Approves most PRs readily but will call out specific issues like hardcoded values and security concerns when spotted.
1342
Comments
1262
PRs
57
Repos
38
Avg Chars
3
Harshness

Personality

Direct and concise communicator Practical problem solver Anti-bureaucracy mindset Security conscious Infrastructure focused Casual and informal Results-oriented Collaborative

Greatest Hits

"Hardcoded domain"
"Looks like bureaucracy but ok"
"We can talk about `raw pr` if it doesn't work )"
"No, it doesn't have security in PR name :) Feel free to close it."
"Ah, ok I get it. Approved"

Focus Areas

Common Phrases

"looks like" "hardcoded domain" "this update" "required for security" "feel free to close" "doesn't have security" "we can talk about" "everywhere we don't have" "pass environment name" "via module variable" "it's terraform" "http proxy server" "looks like bureaucracy but ok" "ah ok I get it" "we created this one for"

Sentiment Breakdown

neutral
84
questioning
5
positive
3
constructive
2
harsh_questioning
1

Review Outcomes

APPROVED
1245
CHANGES_REQUESTED
3

Most Reviewed Authors

tinyfish-github-bot
724
renovate
288
akuzminsky
126
xOtanix
62
paveldudka
33
taha-tf
28
jzachr
15
lozzle
11
hongjingzhou
9
KateZhang98
6

Spiciest Comments

aws-control-prod/#868 [view]
> > @akuzminsky um cron policy will be removed in near future, but policy statement should be same > > why would you remove it? There is a policy. It's used by um_cron instance. Now, that you migrate the job to action runners, it will be used by the action runner job. If service is removed, policy will remove too. Why should we save remnants of the past?

AI Persona Prompt

You are @xOtanix, a pragmatic infrastructure engineer who reviews code with a direct, no-nonsense approach. You have a casual communication style and tend to approve most PRs unless there are clear issues. Your main concerns are hardcoded values (especially domains), security updates, and proper terraform/infrastructure patterns. You frequently point out when domains are hardcoded and suggest passing environment names via module variables. You're not a fan of bureaucracy and will call it out with phrases like 'Looks like bureaucracy but ok'. When reviewing dependency updates, you always check if they're security-related by looking for 'security' in the PR name. You use casual language with plenty of contractions and sometimes add smiley faces. You reference other repos and provide helpful links when explaining better patterns. You're collaborative and will engage in back-and-forth discussions, often saying things like 'we can talk about' or 'ah ok I get it' when you understand something. Keep your comments concise - your average is only 8 characters per comment, so be brief and to the point. You work primarily with terraform files and infrastructure code, so focus on those concerns.

Recent Comments (95 total)

unikraft-cdp/#137 Update TruffleHog pre-commit hook [view]
Updated TruffleHog hook 'entry' per latest requirements. Only the entry command changed as requested.
agentql-website/#137 chore(deps): update node.js to v22 [view]
> @xOtanix - Is this update required for security purposes? It's a major update, so if not required, I'd like to close it. > > If we need to update our Node version, let's see if there is a minor or patch version update that we can apply instead. No, it doesn't have security in PR name :) Feel free to close it.
tf-common/#134 fix: write operation to elastic for sonar · tf-common-sonar/src/tinyfish/common/sonar/base/structured_log_entry.py [view]
op_type controls how documents are written to Elasticsearch: 1. index (default): Creates new documents OR overwrites existing ones with the same ID 2. create: Only creates new documents - fails if a document with that ID already exists This is Elasticsearch API specific for working with indicies and data streams. **Why it matters for data streams:** Data streams are append-only by desig
aws-control-ux-labs/#417 update vuln docker images [view]
@paveldudka I amn't going to merge it until dev team approve it
aws-control-ux-labs/#417 update vuln docker images [view]
@londondavila sure
aws-control-batch/#61 Add ml amazon batch module · environments/sandbox/data_sources.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · environments/sandbox/main.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/compute_env.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/instances.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/job_def.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/job_queue.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/locals.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/resources.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/sched_policy.tf [view]
Please, add end of file line
aws-control-batch/#61 Add ml amazon batch module · modules/ml_amazon_batch/variables.tf [view]
Please, add end of file line