HN user

azophy_2

39 karma

meet.hn/city/id-Bandung

Socials: - x.com/azophy - github.com/azophy - abdurrahman at adianto dot id - linkedin.com/in/abdurrahman-shofy-adianto

Interests: Web Development, Startups, Social Impact, Open Source, DevOps, Cybersecurity

---

Posts8
Comments51
View on HN

Location: Indonesia Remote: Yes Willing to relocate: No

Technologies: Python, TypeScript/JavaScript, Go, PHP, FastAPI, Next.js, React, Node.js, PostgreSQL, MySQL, Redis, Docker, Kubernetes, AWS, GCP, Supabase, LangChain, LLMs, RAG, GraphQL, REST APIs

Résumé: https://s.id/resume-abdurrahman-fullstack Email: abdurrahman dot shofy at gmail dot com

AI-oriented Fullstack Engineer with 9+ years of experience building production web applications, data-intensive systems, and AI-powered products.

Recently, I've been building end-to-end AI workflows for a startup, covering recording UX, transcription, content generation, video rendering, analytics, evaluation workflows, and LLM integrations. I enjoy taking AI features from prototype to production and building the engineering systems needed to make them reliable.

Previously worked as a Software Architect for the West Java provincial government, helping improve engineering practices across 60+ engineers, leading performance optimization efforts for high-traffic systems, and building internal automation tools that saved thousands of hours of manual work.

Selected experience:

- Built and shipped production AI workflows using LLMs, transcription, content generation, and video rendering - Developed RAG systems, natural-language-to-SQL pipelines, and AI evaluation/regression testing workflows - Led database optimization initiatives on large legacy systems handling millions of records - Experience across backend engineering, frontend product development, cloud infrastructure, CI/CD, and software architecture - AWS Certified Solutions Architect – Associate

Looking for senior fullstack, backend, AI engineer, or technical lead opportunities. Remote preferred.

shameless plug: I've been tinkering with a tool to make SSH certificate-based login a bit easier. it's called Sshifu.

basically, you set up a sshifu-server that acts as a certificate authority + SSO server. then on your SSH servers, you configure them to trust this CA (there are helper npx commands / bash scripts to make this easy).

after that, for each user who wants access, they just run:

npx sshifu <sshifu-server-url> <ssh-server-url>

this starts the SSO login flow, sets up the CA public key if needed, and immediately opens an SSH session.

npx is just the easiest way to get started, there are other install options too.

I built this as a smaller alternative to Smallstep / Teleport. it's still very early and mostly vibe-coded, but it's already scratching my own itch.

would love to hear what you guys think

repo: github.com/azophy/sshifu

I feel that stacked PR in git should be common knowledge, however many of the documentations are scattered. I found stacked.dev but feels that its not exploring pure-git workflow that well. thats why I tried to collect all of those docs into a single website that's dedicated into that singular workflow. would love to get any feedback:

https://stacked-pr.github.io

(disclaimer: partly supported by AI, but most of the writing structure were made by hand)

  Location: Indonesia
  Remote: Yes
  Willing to relocate: No
  Technologies: Go, Python, Typescript/Javascript, PHP, PostgreSQL, MySQL, Redis, Docker, Kubernetes, Linux, GraphQL, RestAPI, GCP, AWS, React, Vue
  Résumé: https://s.id/resume-abdurrahman
  Email: abdurrahman dot adianto dot id
Backend engineer with 8+ years of experience. Worked with Go, Python, Typescript, and PHP. Have experience with DevOps & Software Architecture roles. Currently looking for remote work outside of Indonesia

the change from docker classic swarm into current docker swarm happened years ago. from what I can tell, usage-wise there are not much difference between the two.

however the sad thing is currently swarm is held by other company (mirantis) after being sold by docker inc. and the new company doesn't seem that invested in improving swarm. you could say its in life support now save for a few community contribution

more explanation by dockerswarm.rocks website: https://dockerswarm.rocks/swarm-or-kubernetes/

  Location: Indonesia
  Remote: Yes
  Willing to relocate: No
  Technologies: Go, Python, Typescript/Javascript, PHP, PostgreSQL, MySQL, Redis, Docker, Kubernetes, Linux, GraphQL, RestAPI, GCP, AWS, React, Vue
  Résumé: https://s.id/resume-abdurrahman
  Email: abdurrahman dot shofy at gmail dot com
Backend engineer with 7+ years of experience. Worked with Go, Python, Typescript, and PHP. Have experience with DevOps & Software Architecture roles. Currently looking for remote work outside of Indonesia
  Location: Indonesia
  Remote: Yes
  Willing to relocate: No
  Technologies: Python, Django, FastAPI, Typescript, NestJs, PHP, Laravel, PostgreSQL, MySQL, Redis, Docker, Kubernetes, Linux, GraphQL, RestAPI, GCP, AWS, React, Vue
  Résumé: https://s.id/resume-abdurrahman
  Email: abdurrahman dot shofy at gmail dot com
Backend engineer with 7+ years of experience. Mostly worked with Python, Typescript, and PHP. Have experience with DevOps & Software Architecture roles. Currently looking for remote work outside of Indonesia
  Location: Indonesia
  Remote: Yes
  Willing to relocate: No
  Technologies: Python, Django, FastAPI, Typescript, NestJs, PHP, Laravel, PostgreSQL, MySQL, Redis, Docker, Kubernetes, Linux, GraphQL, RestAPI, GCP, AWS, React, Vue
  Résumé: https://s.id/resume-abdurrahman
  Email: abdurrahman dot shofy at gmail dot com
Backend engineer with 7+ years of experience. Mostly worked with Python, Typescript, and PHP. Have experience with DevOps & Software Architecture roles. Currently looking for remote work outside of Indonesia

This is a hacky workaround for medium with limited capabilities, but I like it.

The proper way is of course to actually use format/tools/apps with builtin feature for such needs, as addressed in the beginning of the landing page. There is initial cost for adopting it, but if you actually doing it regularly (novelist/journalist/programmer) it would make more sense in the long run.

In the end its about tradeoff. If your medium is limited and you only need it for once in a while, this format is simple & clear. But for more frequent uses I think this format is costly to maintain compared to using specialized tools/apps.

as one of those "newer engineer", the thought of dealing with server racks and bundle of cables inside huge & gloomy server room actually scares me. I really appreciate those guys who actually knew how to setup those HWs, despite maybe clueless about latest shinier things. having the will to actually wrestle with messy to stuff to make the life of other engineer better is actually commandable. kudos to all those guys

I like it. Simple & straightforward. However I'm interested in the usage of AGPL license. Do you think it would hinder adoption as many company fear of adopting AGPL due to its "virality"?

  Location: Indonesia
  Remote: Yes
  Willing to relocate: No
  Technologies: Python, Django, FastAPI, Typescript, NestJs, PHP, Laravel, PostgreSQL, MySQL, Redis, Docker, Kubernetes, Linux, GraphQL, RestAPI, GCP, AWS, React, Vue
  Résumé: https://tinyurl.com/resume-azophy
  Email: abdurrahman dot shofy at gmail dot com
Backend engineer with 7+ years of experience. Mostly worked with Python, Typescript, and PHP. Have experience with DevOps & Software Architecture roles. Currently looking for remote work outside of Indonesia