I BUILD THE GAPBETWEEN“IMAGINE IF…”AND“OPEN THE LINK.”
Ideas can stay ideas forever. I like making them clickable.
from thought → architecture → build → ship
I build digital products, explore emerging technology, teach people how to create with it, and occasionally argue with my backend until it apologizes.
Based abroad. Building globally.
THIS TERMINAL IS REAL. GO AHEAD, BREAK SOMETHING.↘Yes, it actually works. Type a command or steal one of the try: examples below.
arteja@stacks — live
arteja@stacks:~$ whoami
Full Stack Developer
Software Engineer
AI Analyst
Technical Educator
Builder of suspiciously ambitious ideas.
arteja@stacks:~$ git status
On branch: building-something
Ideas ahead of origin by: 47
nothing to commit.
everything to build.
try:
CHAPTER 01 — HIGH SCHOOL
HIGH SCHOOL
COVID changed the world. I started building mine.
During high school and the COVID era, I started developing websites. While so much of life was suddenly moving online, I got fascinated by something most people weren't asking: who was actually building all of this?
I didn't want to only use the internet. I wanted to understand what was happening behind the screen — how ideas became interfaces, how a button actually did something, how a blank file could turn into something another person could use.
So I started learning. Then I started building.
Somewhere between the curiosity and a ridiculous number of browser tabs, technology stopped feeling like something I consumed and started feeling like something I could create.
Curiosity opened the first tab. I still haven't closed it.
03 // GET TO KNOW ME
OKAY, BUT WHO IS ARTEJA?
The professional stuff is everywhere else. This part is just fun — poke around.
THIS / THAT
vs
vs
vs
vs
vs
vs
MY BRAIN HAS TABS OPEN
LINE THEM UP IF YOU CAN.
It's 2am. This is definitely a good idea. I will regret nothing.
CURRENTLY
Buildingsomething new
Learningalways
TeachingFull Stack Development
ExploringAI
Locationabroad
Availabilityopen
Bugsabsolutely
MY TECH PERSONALITY
Definitely not scientific. Do not cite in a performance review.
CURIOSITY100%
BUILD IT MYSELF100%
ASK "WHY?"100%
SLEEP31%
COMMUNITY100%
OPEN TABSERROR
BUILD A VERSION OF ARTEJA
Role
Environment
Problem
Coffee
Pick three, then compile. It's playful frontend logic — no AI required.
04 // ABOUT ARTEJA
THE CODE IS ONLY PART OF THE STORY.
Beyond the stack, there's a human — and a reason all of this exists.
SUBJECT // ARTEJA GRIERROLE // FULL STACK
STATUS // BUILDING
I learned how to rebuild long before I learned how to code.
I was born blind and deaf and lived with those limitations through the earliest years of my childhood.
When my world began opening up around the age of six, learning wasn't simply about catching up. In many ways, it meant learning how to experience things that other children had already been building familiarity with for years — sound, sight, language, patterns, memory, communication, and how the different pieces of the world connected.
My brain and my way of learning had to adapt. Things that might have developed naturally for someone else often became things I had to approach deliberately, differently, and repeatedly until they became mine.
THE BRAIN CAN ADAPT.PEOPLE CAN REBUILD.“IMPOSSIBLE” CAN MOVE.
I grew up understanding that long before I had the language for it. What it meant in practice: I had to relearn, rebuild, create new ways of processing information, and adapt how I understood the world.
That experience followed me into everything. When I encounter something I don't understand, my instinct is to investigate it. When a system breaks, I want to know why. When someone says something cannot be done, my brain immediately starts asking: “According to who?”
That curiosity eventually found technology. And technology felt strangely familiar. Code is complicated until you understand the pattern. Systems are intimidating until you understand how the pieces communicate. A problem feels impossible until you break it into smaller problems.
Maybe that's part of why engineering made sense — I'd already spent a lifetime learning how to do exactly that.
IMPOSSIBLE HAS ALWAYS SOUNDED TEMPORARY TO ME.
I don't always know how yet. “Yet” is the important part.
Tap a marker — see how it connects.
I learned very early that “difficult” and “impossible” are not synonyms.
My background as a former emergency first responder in law enforcement shaped the way I think about responsibility, safety, information, and what happens when technology meets real people in real situations.
Over the years, my technical and investigative skills have taken me far beyond building websites.
I've used technology to help locate missing children. I've helped reconnect families.
I've worked with communities to better understand:
Digital SafetyCybersecurity AwarenessAI SecurityResponsible TechnologyOnline SafetyDigital Literacy
Those experiences are part of why I don't see technology as something separate from people.
To me, the most interesting question is never simply: “Can we build it?” It's also: “Who does it help once we do?”
I've spent my life adapting, rebuilding, learning, teaching, investigating, connecting, and refusing to accept that the current limitation has to be the final answer.
THAT'S PROBABLY WHY I BECAME AN ENGINEER.
Debugging started long before JavaScript.
05 // THE STACK
Not a wall of logos. A map of how it connects.
Tap a technology to light up what it talks to, what I use it for, and where it shows up. No fake skill percentages — just how comfortable I actually am.
frontend
Next.js
My default for real products — App Router, server components, routing, the whole spine.
Comfort
Home turf. This site runs on it.
Where it shows up
Linked to project data as verified case studies are added.
Talks to
06 // CREDENTIALS
I like receipts.
Certifications, structured learning, and proof that I don't only collect browser tabs.
I work closely with AI because I believe technology should keep evolving. Not just what it can do — how it should be implemented, analyzed, governed, secured, and used.
Don't be shy. Click the buttons below.
I promise nothing will explode. Probably.
Start with the task, not the model.
What does the work actually need, what's the risk, and what is the data really saying? The model is one input — the analysis is the job.
Small, self-contained things I try to understand a capability.
EXPERIMENTS PENDING
AI WORKFLOWS
Human-in-the-loop pipelines where the model is one component.
EXPERIMENTS PENDING
AI ANALYSIS
What a task really needs, what the risk is, what the data says.
EXPERIMENTS PENDING
GOVERNANCE
How AI should be implemented, reviewed, and kept accountable.
EXPERIMENTS PENDING
SECURITY
Where AI systems break, leak, or get manipulated — and how to prevent it.
EXPERIMENTS PENDING
AUTOMATIONS
The boring, repeatable work AI can carry — responsibly.
EXPERIMENTS PENDING
PROTOTYPES
Rougher builds testing whether an idea is worth finishing.
EXPERIMENTS PENDING
THOUGHTS
Notes on where this is all going, and how to build for it.
EXPERIMENTS PENDING
DON'T FEAR THE EVOLUTION. LEARN HOW TO BUILD WITH IT.
09 // TEACH
Then I started teaching other people.
Knowledge should travel. I teach Full Stack Development to beginners, children learning technology, career changers, people breaking into tech, and anyone breaking into tech. Tap a key — learn something.
LESSON 01 / 09 — The skeleton.
HTML
HTML is the structure of the web. Use semantic elements — <nav>, <main>, <button> — so people, browsers, and assistive tech all understand the page. Divs can't do that for you.
Technology becomes more powerful when more people understand how to create with it.
10 // THE MISSION
Build people, too.
I care about what technology can do for people who haven't always had access to the rooms where technology gets built. So I try to open those rooms.
Teaching
Full-stack development for people who were never handed the map.
Mentorship
Walking alongside people breaking into tech, not just pointing.
Community platforms
Technology built with a community, not just for it.
Nonprofit work
Tools for organizations doing the work that matters.
International organizations
Technology that crosses borders as easily as I do.
Access
Opening the rooms where technology actually gets built.
Technology becomes more powerful when more people can build with it.
11 // THE NETWORK
The internet connected computers. I like connecting people.
Some of the best things in technology happen when the right people find each other. Tap a node — see what that connection actually means to me.
↑ Pick a node to see what that connection means to me.
12 // GLOBAL
My office moves. My standards don't.
Based abroad. Building globally.
GLOBAL PERSPECTIVE
REMOTE COLLABORATION
CROSS-BORDER TECHNOLOGY
DISTRIBUTED TEAMS
INTERNATIONAL ORGANIZATIONS
BUILDING FROM ANYWHERE
13 // OPPORTUNITIES
So… what should we build?
Pick the door that matches the moment.
You have a team.
HIRE ME
I have approximately 47 ideas.
For employment, engineering teams, AI roles, and technology leadership.
Remote software engineering
Full-stack product work
AI analysis & governance
Technical leadership
You have an idea.
BUILD WITH ME
Let's make it exist.
For startups, founders, organizations, products, consulting, and large projects.
Product from concept to foundation
Community & organizational platforms
AI-enabled workflows
Cross-border technology
You want to understand it.
LEARN WITH ME
Technology is significantly less scary once somebody explains it properly.
For training, teaching, workshops, developer education, and technical onboarding.
Ask me about Arteja. I'm a local mock with a fixed set of honest answers for now — the real assistant connects later. Try a prompt below, or type your own.