Contact us

The Machine Behind My Backend Systems

by Arif Ikhsanudin, Backend Developer

When you hire a backend consultant, you're not just hiring code. You're hiring performance, reliability, and execution speed. That’s why the machine I use to build systems matters.

1. Macbook Pro

This is my daily driver.

If I’m working from a café, traveling, or just moving around the house — this is the machine with me.

I’ve used different laptops before, but I always come back to the MacBook Pro. The battery life is predictable. The build quality is solid. It doesn’t randomly slow down when I have 20 things open.

My current configuration:

  • M6 Pro chip with 18-core CPU and 20-core GPU
  • 64GB RAM
  • 1TB SSD

2. Custom-Built PC

At home, I use a custom desktop when I need more raw power.

This machine stays on my desk and is built specifically for heavy workloads — long test runs, large datasets, or when I just want maximum performance without thinking about resource limits.

Specs:

  • AMD Ryzen 9 7950 X3D processor with 16 cores and 32 threads
  • 128GB RAM of DDR5 Kingston Fury Beast
  • 4TB NVMe Samsung 990 Pro
  • 8TB HDD WD Blue
  • Radeon RX 7900 GRE
  • 32-inch 4K monitor

It’s fast. Very fast.

Sometimes I run full environments locally just because I can. No waiting for cloud instances. No worrying about memory. Everything is instant.

Why Two Machines?

The MacBook Pro gives me flexibility.

The desktop gives me power.

One travels with me. One stays grounded at home.

That’s my setup in 2026.

It might change next year — but for now, this is the machine behind the work.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Say Hej

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Git Hooks: Automate the Checks Your Team Keeps Forgetting

Git hooks run scripts at specific points in the Git workflow — before a commit, before a push, after a merge. They are the lightweight automation layer that enforces standards locally before code ever reaches CI.

Read more

Who Is Responsible for Auth in a Microservices Architecture

Auth responsibility in microservices is frequently undefined, duplicated across teams, or delegated to the wrong layer. The ambiguity is not an org problem — it is an architecture problem with a clear solution.

Read more

How I Handle Disagreements With Other Engineers Professionally

Technical disagreements are normal and often productive. Handled poorly, they damage relationships and produce worse decisions. Here's the approach I've developed over years of getting it wrong first.

Read more

Why “Simple Features” Are Often Not Simple

“It’s just a small feature” is one of the most expensive sentences in software. What looks simple on the surface often hides layers of complexity underneath.

Read more