iOS Engineering Leader · Educator · Founder

Engineering is not what I do.It's how I think.

I believe software engineering is much more than writing code.

It's about solving problems, designing systems, making thoughtful decisions, and continuously learning.

For more than thirteen years, I've been building iOS applications, leading engineering teams, mentoring developers, and helping transform ideas into products used by millions of people.

Today, my mission has expanded.

I'm helping engineers learn how to combine strong engineering principles with modern AI workflows through what I call the AI-Powered iOS Engineering Framework.

Explore the Framework View My Projects

Portrait

My Story

Where Curiosity Became a Career

Long before I wrote my first line of Swift, I was fascinated by technology.

As a child, I spent hours experimenting with Macromedia Dreamweaver, trying to build websites simply because I enjoyed creating things.

I wasn't thinking about becoming a software engineer.

I simply loved understanding how technology worked.

That curiosity never disappeared.

It eventually led me to earn a Bachelor's degree in Computer Science, where I built the theoretical foundation that continues to shape the way I think about software today.

Looking back, I realize that I was never attracted to programming because of code itself.

I was attracted to the process of solving problems, building systems, and creating something that didn't exist before.

That mindset has stayed with me throughout my career.

Curiosity introduced me to technology. Engineering gave that curiosity direction. Artificial Intelligence is simply the next tool in that journey.

Why Engineering?

Engineering Is About Solving Problems, Not Writing Code.

People often ask me why I became a software engineer.

The answer has never been "because I like coding."

Coding is only a tool.

What truly fascinates me is solving problems.

I've always enjoyed taking something complex, breaking it into smaller pieces, understanding how it works, and building a better solution.

That mindset started long before my professional career.

Years later, I realized that software engineering perfectly combines creativity, logic, communication, and continuous learning.

That's why engineering has never felt like a job.

It's the way I naturally approach problems.

Even today, after more than thirteen years of building software, the excitement remains exactly the same.

The technologies evolve.

The engineering mindset doesn't.

I don't love programming because I love writing code.

I love programming because I love building solutions.

Why Apple?

The Apple Ecosystem Changed Everything.

During my university years, smartphones were rapidly changing the world.

Applications were becoming more than simple utilities.

They were becoming products that millions of people used every day.

Among all platforms, Apple's ecosystem immediately stood out to me.

I admired the attention to detail.

The consistency.

The focus on user experience.

The quality standards.

When I first opened Xcode, something simply clicked.

Building iOS applications felt natural.

I enjoyed every part of the process — from designing interfaces to optimizing performance and polishing small user interactions.

Over the years, that decision proved to be one of the best decisions of my career.

Apple continuously raises the standard for software craftsmanship.

That philosophy has deeply influenced the way I build software today.

Not just visually. But architecturally. Professionally. And personally.

Great products aren't built by accident.
They're built through thousands of thoughtful engineering decisions.

Why iOS?

I Didn't Choose iOS Because It Was Popular.I Chose It Because It Felt Right.

Many people choose a platform based on market trends.

I chose iOS because I genuinely enjoyed building for it.

I loved how Apple combined hardware and software into a single ecosystem.

I loved the developer experience.

I loved the emphasis on performance.

I loved the attention to small details that most users never consciously notice.

As my career progressed, I had the opportunity to work on products used by millions of people — from global consumer applications to banking platforms and startup products.

Every project reinforced the same belief:

Great mobile applications are built by engineers who care deeply about quality.

Not developers chasing the fastest solution.

Why Artificial Intelligence?

AI Doesn't Replace Engineers.It Amplifies Them.

Many people ask whether AI will replace software engineers.

I believe that question misses the point.

Artificial Intelligence is a tool.

Just like compilers.

Just like Git.

Just like cloud computing.

Every major technological shift has rewarded the people who learned how to use the new tools effectively.

AI is no different.

The engineers who learn how to collaborate with AI will become dramatically more productive.

Not because AI thinks for them.

But because it removes repetitive work and allows them to spend more time solving meaningful engineering problems.

The future belongs to engineers who combine technical depth with intelligent AI workflows.

That is exactly why I created the AI-Powered iOS Engineering Framework.

It isn't about replacing engineering.

It's about strengthening it.

The Tractor Principle

The Tractor Didn't Replace Farmers.It Empowered Them.

I often compare Artificial Intelligence to the invention of the tractor.

When tractors first appeared, some farmers embraced them immediately.

Others believed they could continue working exactly as before.

The tractor didn't replace farmers.

It simply allowed one farmer to accomplish far more than was previously possible.

Those who adopted the new tool became significantly more productive.

Those who ignored it gradually fell behind.

Artificial Intelligence represents the same shift for software engineering.

AI will not replace great engineers.

But engineers who know how to use AI effectively will outperform those who refuse to adapt.

The competitive advantage is no longer just writing code.

It is knowing how to think, design systems, communicate with AI, and make better engineering decisions.

That is the future I want to help developers prepare for.

The Principle

Engineering is the driver.

AI is the accelerator.

Never the other way around.

Why Teaching?

Teaching Is How I Multiply My Impact.

Throughout my career, I discovered something unexpected.

Building software was rewarding.

Helping someone else become capable of building software was even more rewarding.

Every time I explained a difficult concept, reviewed someone's architecture, or helped a junior engineer solve a problem, I realized I enjoyed teaching just as much as engineering.

Teaching allows me to scale knowledge.

One well-designed lesson can change hundreds of careers.

One great engineer can build products that impact millions of users.

That's why I don't see education as a side project.

It's part of my responsibility as an engineer.

Today I've mentored more than one hundred developers through workshops, mentoring sessions, and professional training.

Many of them started with little experience.

Some later became confident iOS engineers working on real production applications.

Watching that transformation is one of the most meaningful parts of my work.

Teaching Philosophy

I don't teach syntax.

I teach thinking.

Anyone can watch a tutorial and copy code.

Very few people learn how to make engineering decisions.

Real software engineering isn't about remembering APIs.

It's about understanding trade-offs, communication, architecture, debugging, collaboration, product thinking, and the ability to keep learning.

Those are the skills that survive every new framework, every new language, and every new AI tool.

That is exactly what I try to teach.

Every lesson should help students

Think independently.
Understand why.
Ask better questions.
Build production-quality software.
Develop engineering judgment.
Use AI responsibly.
Never depend entirely on AI-generated code.

Engineering Philosophy

Engineering Before Everything.

Technology changes.

Engineering principles don't.

Throughout my career, I've worked with different programming languages, frameworks, architectures, and products.

Every few years, the industry introduces another revolutionary technology.

One thing has always remained constant: Good engineering.

That's why my philosophy is built on principles rather than technologies.

Engineering First.

Technology should support engineering. Engineering should never depend on technology. The best engineers don't define themselves by the tools they use. They define themselves by the problems they solve.

AI Accelerated.

Artificial Intelligence should increase human capability. Not replace human thinking. The best engineers will use AI to automate repetitive work while spending more time on architecture, communication, debugging, design, and product decisions.

Systems Beat Shortcuts.

There are no shortcuts to becoming a great engineer. There are only better systems. Consistency beats intensity. Daily learning beats occasional motivation. Repeatable workflows beat random inspiration.

Learn Forever.

The software industry changes every year. Curiosity is no longer optional. It is one of the most valuable engineering skills. Every project teaches something. Every mistake teaches something. Great engineers never stop being students.

Core Values

The Principles That Guide My Decisions.

Build Real Things

I value practical experience over theoretical perfection. The best lessons come from production. Not slides. Not toy projects. Not simplified tutorials.

Stay Honest

I never want to promise unrealistic results. Engineering takes time. Growth takes time. Mastery takes time. My responsibility is to make the journey more efficient. Not to pretend it is easy.

Think Long-Term

Most people optimize for today. I optimize for the next decade. The decisions I make today should still make sense years from now. That applies to products, teaching, writing, leadership, and personal growth.

Share Knowledge

Knowledge grows when it is shared. Teaching isn't giving away an advantage. It is creating more people capable of building great things. The software community becomes stronger when engineers help one another.

What I Choose Not to Pursue

I don't teach shortcuts.
I don't create clickbait.
I don't chase every AI trend.
I don't believe AI replaces software engineers.
I don't optimize for algorithms instead of people.
I don't create content just to go viral.
I don't build products I wouldn't personally use.
I don't compromise engineering quality for speed.

My Journey

From Curiosity to Engineering Leadership.

Early 2000s

The Beginning

Discovered technology through curiosity. Spent countless hours experimenting with computers, software, and websites. Built simple websites using Macromedia Dreamweaver. At the time, I wasn't thinking about a career. I simply enjoyed creating things.

University

Building the Foundation

Studied Computer Science to build a strong engineering foundation. University helped me understand algorithms, data structures, software engineering principles, and systems thinking. More importantly, it taught me how to learn.

University Years

Discovering iOS

As smartphones started transforming the world, I became fascinated by mobile applications. Apple's ecosystem immediately stood out. The combination of hardware, software, developer experience, and attention to detail convinced me that iOS was where I wanted to build my career.

First Professional Years

Becoming an Engineer

Started building production iOS applications. Learned the realities of software engineering: working with teams, deadlines, product decisions, bugs, architecture, communication. This period shaped my engineering mindset far more than any university course.

Growing Responsibilities

Growing Into Leadership

As my experience grew, my responsibilities changed. I wasn't only writing code anymore. I was mentoring engineers, reviewing architecture, making technical decisions, building engineering culture, hiring developers, and leading teams. I discovered that leadership is simply another form of engineering.

Enterprise Era

Enterprise Experience

Contributed to products used by millions of people: McDonald's Mobile App, ABB Mobile, Birbank Business, Rabitabank. Each project presented completely different engineering challenges. Different industries, architectures, business requirements, and teams. Those experiences taught me how to adapt without compromising engineering quality.

Entrepreneurship

Building My Own Product

Eventually, I wanted to build something of my own. That led to Borderless eSIM. Unlike previous projects, there was no existing internal knowledge. Everything had to be learned from scratch. That experience reminded me of one of my strongest beliefs: Engineers don't wait for answers. They find them.

Career Highlights

Thirteen Years. Four Disciplines.

13+

Years Building iOS Apps

Building production iOS applications across enterprise companies, fintech organizations, and startup products.

Leadership

Engineering Leadership

Leading engineering teams, building engineering culture, mentoring developers, and making architectural decisions.

100+

Developers Mentored

Teaching more than one hundred developers through workshops, mentoring sessions, and structured learning programs.

Products

Product Development

Enterprise applications, startup products, personal products, and digital education — each category teaching different lessons.

Beyond Engineering

Curiosity Beyond Code.

People often assume software engineering is only about technology. For me, it has always been about curiosity.

Outside of Engineering

Reading books.
Learning new technologies.
Exploring AI.
Studying successful companies.
Understanding product strategy.
Thinking about better ways to teach.

Books

Atomic Habits
Shoe Dog
Rich Dad Poor Dad
Detective novels

Favorite Tools

Xcode
Claude
Visual Studio Code
Notion
GitHub

I believe the best engineers are interested in much more than code. They understand people, products, business, and communication. Because software is ultimately built for humans.

Mission & Vision

Personal Mission

Help engineers build better software by combining timeless engineering principles with modern AI workflows.

Everything I create should make developers more capable, more thoughtful, and more confident.

Not just more productive.

Future Vision

I don't want to become known simply as another iOS developer.

I want to become one of the people helping define what modern AI-powered software engineering looks like.

I believe software development is entering one of the biggest transformations in its history.

Developers need more than tutorials.

They need frameworks. They need systems. They need engineering thinking.

That is the work I want to dedicate my career to.

What I Want To Be Remembered For

Not for the number of apps I built.

Not for job titles.

Not for social media followers.

I want people to remember me as someone who helped engineers think differently.

Someone who made AI practical instead of intimidating.

Someone who shared knowledge honestly.

Someone who cared deeply about quality.

Someone who built trust before building products.

My journey started with curiosity. It grew through engineering. Today it continues through Artificial Intelligence. Tomorrow it will continue wherever technology creates new opportunities to build, teach, and learn. The tools will evolve. The mindset won't.

Let's Connect

Let's Build the Future of iOS Engineering Together.

Whether you're an engineer looking to improve your workflow, a company seeking technical leadership, a conference organizer, a podcast host, or someone passionate about the future of software engineering — I'd love to connect.

Explore the AI-Powered iOS Engineering Framework Connect on LinkedIn