How I think about automation
Code, cloud infrastructure, AI automation, and open source are the threads running through this profile. The diagram brings those interests together in an example of how a larger system could be built and operated.
Infrastructure and apps can move independently, with environment readiness connecting them. A change gets reviewed, provisioned, and verified; an application gets built once, tested, and promoted. Existing infrastructure can be reused when it already meets the app's needs. For coupled changes, add compatible infrastructure first, deploy the app, then clean up obsolete resources.
I'm interested in AI that helps with the whole loop: understanding dependencies, drafting code and tests, explaining changes, investigating failures, and turning findings into useful PRs. Automated checks, human review, and feedback keep that loop grounded. The amount of process should fit the project.
apiVersion: humans.dev/v13 # 13+ years, still backwards compatible
kind: AutomationEngineer
metadata:
name: siddharth-abbineni
aliases: [wapenshaw, tHeSiD]
labels:
role: sr-technology-automation-engineer
also: [ai-automation, cloud-architect, solutions-architect]
spec:
replicas: 1 # working on automating this too
interests: [ai-automation, developer-tools, cloud-platforms, open-source]
clouds:
primary: azure
failover: [aws, gcp]
languages: [rust, go, python, csharp, typescript]
strategy:
type: RollingUpdate # automate, observe, repeat
resources:
requests:
toil: "0"
limits:
manual-steps: "0"
status:
phase: Running
conditions:
- type: AzureCertified
status: "True"
count: 4
- type: OpenToInterestingProblems
status: "True"
$ ping siddharth
64 bytes from siddharthabbineni.in · 64 bytes from linkedin · 64 bytes from x.com · 0% packet loss


