Skip to main content

// ABOUT

Phil Vishnevsky

I write code, break things, and occasionally ship something useful.

locationHartford, CT
focusSWE · AI · Games
statusOpen to opportunities
$ view-work

// EXPERIENCE

The story so far

Started coding in 2019. Haven't really stopped. That's, like, 2,486 days of experience. Or 214,851,050 seconds

~/journey/timeline.log
├─ 2026
Embedded, AI & Game Development
Building AI tools and indie games
[work]
├─ 2023-Present
Full-Stack Engineering
Web apps, containers, and embedded
[work]
├─ 2022-2025
UNC Charlotte
BS, Computer Science
[edu]
2019
First Lines of Code
Self-taught coding journey begins
└─ [milestone]
...more chapters loading
4 logsLOG
~/stats/overview
years_coding0+
[░░░░░░░░░░]
projects0+
[░░░░░░░░░░]
technologies0+
[░░░░░░░░░░]
last updated: nowSTATS
~/resume/resume.pdf
PDF
···

// CURRENTLY

What I'm up to

What I'm building, learning, and reading right now.

~/git/contributions
$ git log --graph --since="90d"
building heatmap...
~/git/activity
$ git log --all --oneline
fetching activity...
~/now
$ cat now.md
// BUILDING
├─indie game with Godot + C#[active]
├─AI-powered dev tools[active]
└─this portfolio (always)[ongoing]
// LEARNING
├─embedded systems & RTOS[deep-dive]
├─game design patterns[exploring]
└─Rust (slowly)[started]
// READING
├─Designing Data-Intensive Applications[current]
└─Game Programming Patterns[reference]
last updated: Mar 2026NOW
~/github/zenatron/zenatron/README.md
$ curl github.com/zenatron/zenatron/README.md
Fetching README...
···

// OFF THE CLOCK

Stuff I like

Apps I use, hobbies I have, opinions I'll probably change.

~/favorites/list.sh
$ ls --filter all
Homelabbing

building servers at home

Game Dev

did not work at blizzard

Networking

connecting computers

Reading

sci-fi, tech, and self-improvement

Hiking

touching grass

Tea Brewing

trying every tea in the world

Weightlifting

building strength and discipline

Travel

exploring the world

37 itemshi :3
~/principles
$ cat principles.md
├─01.ship > perfect
done is better than debating edge cases forever
├─02.read the error
the stack trace is trying to help you. let it.
├─03.own the outcome
blame doesn't fix bugs. accountability does.
├─04.simplify ruthlessly
if you can't explain it simply, you don't understand it well enough
├─05.learn in public
writing things down forces you to actually understand them
├─06.tools are tools
don't marry your stack. use what works, ditch what doesn't.
└─07.help the next person
write code (and docs) for the person who reads it at 2am
7 rules to code byMANIFEST
~/neofetch
$ fastfetch --host=macbook
phil@macbook
────────────
OS: macOS Sequoia
Kernel: arm64 (Apple Silicon)
CPU: Apple M1 Pro (8-core)
GPU: Apple M1 Pro (14-core)
Memory: 16GB unified
Storage: 512GB NVMe
Display: 14.2" Liquid Retina XDR (120Hz)
Shell: zsh + oh-my-zsh
Editor: VS Code · nvim
Terminal: Ghostty
Theme: Atom One Dark
████████████████
$ fastfetch --host=desktop
phil@desktop
────────────
OS: CachyOS (Arch btw)
Kernel: x86_64 Linux
CPU: AMD Ryzen 9 7950X (32-thread)
GPU: NVIDIA RTX 4070 Ti (12GB)
Memory: 64GB DDR5
Storage: 4TB NVMe
Display: 2x 27" 2K QHD (144Hz)
Shell: fish
Editor: VS Code · nvim
Terminal: Alacritty
Theme: Atom One Dark
████████████████
2 machinesFETCH
···
─── EOF ───

Made it this far? I'm impressed.

exit 0 · thanks for scrolling