Contact us

Flash Drives, Multi-Layer RDP, and Manager Approvals: A Day in a Bureaucratic Dev Team

by Arif Ikhsanudin, Backend Developer

You sit down to fix a small bug. It should take 10 minutes.
Six hours later, you’re still waiting—for access, for approval, for something to happen.

The 10-Minute Task That Takes All Day

Let’s walk through a “simple” staging test:

  • Copy files to a flash drive—oh, wait, you can’t transfer directly to RDP
  • Upload to OneDrive first, then download on the first layer of RDP
  • Open Chrome on that RDP… wait 20 minutes just to start downloading
  • Second layer RDP has 500MB of storage, shared among 3,000 people

And don’t forget the 100MB Spring Boot build .jar you need to upload to OneDrive.

  • Your personal OneDrive storage is 2GB
  • Deleting the trash folder won’t free space immediately
  • You need to submit an IT ticket, and approval takes 2 weeks

You haven’t written a single line of code yet.

Waiting Is the Real Job

Now comes the best part: access approval.

  • You message your manager
  • He hasn’t opened WhatsApp yet
  • Hours pass
  • Maybe he forgets

Six hours later, you finally get access—or maybe not.

Your job isn’t development anymore. It’s waiting for permission.

Flow? What Flow?

Good development depends on momentum:

  • Write code
  • Test quickly
  • Fix immediately

But in this environment:

  • Every test costs 30–60 minutes just to start
  • Storage limitations force you to plan weeks in advance
  • Every delay breaks your concentration

You stop thinking deeply.
You stop caring about details.

Because the system punishes iteration.

When People Start Breaking the Rules

At some point, developers adapt:

  • Sharing access to avoid waiting
  • Skipping steps just to move forward
  • Avoiding staging altogether

Not because they’re careless—
because they’re desperate to get work done.

The stricter the system, the more people quietly work around it.

This Isn’t Security. It’s Paralysis.

All of this is justified as “security”:

  • No direct access
  • Multiple layers
  • Manual approvals
  • Storage caps
  • IT tickets for clearing already deleted files

But what do you actually get?

  • Slower delivery
  • Lower quality
  • Frustrated engineers

And ironically:

  • More risky behavior

You didn’t build a secure system. You built a slow one.

The Quiet Reality

At the end of the day:

  • Developers look unproductive
  • Deadlines slip
  • Managers ask, “Why is this taking so long?”

But nobody talks about the real issue.

Not the code.
Not the people.

The process.

Because when it takes 30 minutes just to log in, 20 minutes just to download, weeks to clear storage, and hours to get approval—

you’re not building software anymore.

You’re surviving a system that was never designed to let you 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

How to Keep a “Lessons Learned” Notebook

Ever finish a project and realize you forgot all the small mistakes and smart hacks you discovered? A “lessons learned” notebook can turn fleeting experiences into a goldmine of knowledge for the next project.

Read more

What If Frontend Engineers Were Treated Like Backend? Chaos Would Start on Day One

Imagine frontend engineers starting a sprint with no design, no specs—just vibes and pressure. Now add extra responsibilities that have nothing to do with UI. That’s where things break fast.

Read more

Writing Efficient JPA Queries — Fetch Strategies, Projections, and Native Queries

JPA abstracts SQL but does not eliminate the need to think about it. The fetch strategy, the columns selected, and the SQL generated determine whether your queries are fast or slow at scale. Here is how to control each layer.

Read more

Docker Networking Is Confusing Until You Understand This One Thing

Most Docker networking confusion comes from conflating three distinct namespaces: how containers reach each other, how the host reaches containers, and how containers reach the outside world. Once you separate those three, the rules become predictable.

Read more