USES
What I use
The things within arm's reach while I work. Not just a list: each item says why I picked it, and that is where the useful part is.
Rows marked “placeholder” have not been filled in yet. Left empty rather than made up.
Hardware
What sits on the desk. This whole section is still a placeholder: the hardware is yours to fill in.
Computer Chassis
The ASUS Hyperion GR701 case felt like it had been designed specifically for my needs, both in terms of appearance and functionality.
Monitor
This 27-inch monitor is from the Monster Aryond series. A larger screen means a larger workspace.
Keyboard
This keyboard from the TUF Gaming K1 series offers excellent sound quality and is also quite reasonable in terms of features.
Mouse
The Pusat One Shot Pro Wireless Mouse is quite good in terms of battery life and features.
Headphones
The Hawk HS420 model offers a pleasant experience with its sound quality and comfortable fabric ear pads.
Phone
With the iPhone 16 Pro Max, I stay closer to the latest technology while also creating my content.
Development
The programs open while I write code, and the languages I touch most.
Windows 11
My day-to-day operating system; this site was built on it from start to finish.
Visual Studio Code
This is the IDE I prefer the most when coding.
Terminal
I generally work with PowerShell, but when used correctly, most terminals offer similar functionality.
Git
Everything lives in version control; this site is itself a repository, posts included.
Python
Automation and data-related tasks. I prefer PyCharm when developing projects with Python.
Dart and Flutter
My mobile development toolkit: Being able to build apps for multiple platforms from a single codebase is an excellent experience. I mostly prepare and use my own materials.
Docker
I use Docker to containerize my development environment and the small services I work with. This allows me to run projects more easily and reliably across different environments.
This site
The stack behind the page you are reading. Versions are taken from the packages installed in the repository.
Astro
It converts pages into HTML at build time. No framework code is sent to the browser, and the page can be fully viewed even without JavaScript.
Tailwind CSS
I manage layout and spacing with utility classes, while colors are handled through theme variables. This way, the dark theme can be controlled from a single place.
MDX
I use plain Markdown for articles and MDX when I need to add components between the content. This way, there’s no need to create a separate structure for each article.
TypeScript
The translation layer and component interfaces are strongly typed. A missing text in one language becomes a build error instead of silently making its way onto the page.
Keystatic
The writing panel only runs on the development server and writes directly to files in the repository. It is not included in the production build.
Inter (subsetted)
The default files were loading 133 KB into the browser; now, only the characters actually used by the site are downloaded. Turkish characters are kept in a separate file and loaded only on Turkish pages.
Server
What runs on the published side.
nginx
It serves the static files. Since the site is hosted under a subdirectory rather than the root of the domain, the redirect and caching rules are managed here. If the domain changes in the future, only this configuration will need to be updated.
PocketBase
A single-file backend with the database, authentication, and file uploads all in one place. For a small project, it doesn’t make sense to set up a separate stack. It also makes it easier to change the architecture if the project grows later.
PM2
It keeps the processes on the server running: it restarts crashed services and automatically starts them when the machine reboots.