Ali Akhtari

Ali Akhtari · Systems builder

I build software systems from the problem outward.

I work across software, automation, product questions, and operations. The goal is not a polished demo. It is a useful system that can be understood, deployed, maintained, and improved.

Explore the system Start a conversation
Ali Akhtari's system map An interactive constellation linking to systems, work, principles, current focus, and contact. Systems Build Automate Open source Learn Now Connect

Follow a line. The structure is the starting point.

The map has another side.

The other side · AI-assisted

The map, speaking.

Ask about the work, the approach, or what has his attention now. The voice is narrow by design: it answers from approved public material and points back to real pages.

  1. Page

    The public map is awake. Ask a useful question and I will point to what I know.

Complete the quiet verification before asking. Each response is generated when you submit.

This is a scoped AI interaction. Submitted questions are sent to OpenAI for a response. It is not Ali, and it does not have access to private information.

01 Systems

Start with the system, not the stack.

Before choosing tools, I want to understand the user, the constraints, the data, the failure modes, and the feedback loop. Those decisions shape whether software remains useful after launch.

Read the working approach

02 Selected work

Open-source work with a real interface.

SpotifyScraper is a maintained Python library, not a placeholder project. Its code, package, documentation, and public history show how I approach external systems and developer-facing tools.

2026 · active · open source

SpotifyScraper

A Python library for extracting Spotify metadata without official API authentication.

PythonOpen sourceAutomation
Read the project details
257 Stars
28 Forks
303 Commits

03 Principles

A practical way of working.

01

Define the real problem

Start with the user, the constraint, the data, and the failure mode. A framework is useful only after the system is understood.

02

Carry the work end to end

Useful software crosses boundaries. I care about the path from the first question through architecture, implementation, deployment, and maintenance.

03

Automate with judgment

Automation should remove repeated work without hiding important decisions. The output still needs verification, ownership, and a clear failure path.

04

Maintain what ships

A project is more than its first release. Documentation, feedback, operational details, and the next iteration are part of the product.

04 Public loop

Build, document, answer, improve.

Public code and technical answers make the work inspectable. Feedback exposes assumptions and improves the next version.

257 GitHub stars
1,312 SO reputation
392k People reached
32 Answers shared

05 Now

What I am improving now.

  • 01Designing software around the problem, its constraints, and its failure modes before choosing a stack.
  • 02Using autonomous tooling to remove repeated work while keeping review, testing, and accountability inside the loop.
  • 03Improving the connection between building, operating, documenting, and maintaining open-source projects.
Open the current page

A good place to begin

Have a software problem worth understanding properly?

Start a conversation