DEV Community: Angga Jiyan

Shock After Joining a New Company as a Developer

Angga Jiyan — Sat, 16 May 2026 13:10:45 +0000

A while ago, I joined a new IT company.

Technically, it wasn’t too difficult to adapt. It was still backend, frontend, databases, APIs — things I was already familiar with.

But there was one thing that genuinely surprised me:
the coding culture was completely different from the company I worked at before.

At my previous company, coding standards were taken very seriously.
Folder structures were clean.
Naming conventions were consistent.
Old comments were removed.
Even small details during code review mattered.

I got used to working in an environment where “clean code” was a big deal.

Then I joined the new company.

And suddenly I started seeing:

old commented-out code everywhere,
functions that were hundreds of lines long,
mixed business logic,
inconsistent naming,
and pieces of legacy code that looked like they had survived for years untouched.

Honestly, at first, it stressed me out a little.

My immediate reaction was:

“Why doesn’t anyone clean this up?”

But after spending more time there, I slowly realized something important:

Real-world software development is much messier than the clean coding principles we often see online.

Every Company Has Its Own Way of Surviving

At my previous company, workloads were more manageable.
There was time for refactoring, architecture discussions, and improving code quality.

At the new company, things moved much faster.

Most of the time, the priorities were:

shipping features quickly,
fixing urgent bugs,
responding to client requests,
and keeping the system running.

That doesn’t mean the developers there were bad.

In fact, many of them were highly capable.

But their priorities were different.

And honestly, that makes sense.

Because in the real world, developers are not just writing code in isolation. There are deadlines, business pressure, clients, unexpected changes, and production issues happening all the time.

Sometimes idealism has to meet reality.

I Realized I Was Carrying Technical Ego Too

When I first joined, I felt like many things were “wrong.”

I wanted to:

reorganize folders,
remove old comments,
split large functions,
enforce consistent naming,
and refactor a lot of things immediately.

But then I realized something:

Joining a new team and instantly saying:

“Your codebase is messy”

isn’t a great way to build trust.

Every codebase has its own history.

Some strange-looking code exists because:

someone was rushing to meet a deadline,
a hotfix was needed,
client requirements suddenly changed,
or multiple developers made compromises over time.

Sometimes we only see the final result without understanding the story behind it.

Clean Code Matters — But It’s Not Always the Top Priority

This was probably the biggest lesson for me.

I used to think:

good code = perfectly clean code.

Now I see it differently.

Sometimes “good code” simply means:

the team can still understand it,
bugs can still be fixed,
and the business can continue operating without major problems.

Is it ideal? Maybe not.
Is it realistic? Very often, yes.

So I Started Adapting Slowly

Now, instead of trying to “fix everything,” I take a smaller approach.

Whenever I touch a file, I try to:

clean up a little,
remove truly unnecessary comments,
improve naming where it helps,
or simplify logic if it becomes too difficult to read.

Small improvements over time.

Because changing engineering culture doesn’t happen overnight.

And honestly, I’ve started realizing that being a professional developer is not only about writing beautiful architecture.

It’s also about:

working with different kinds of teams,
understanding business realities,
and knowing when to be idealistic and when to be pragmatic.
Final Thoughts

If you recently joined a new company and felt shocked by the codebase or coding culture, you’re not alone.

I’ve been there too.

Sometimes we come in expecting:

“Every company follows best practices.”

But reality is different.

Every company has different pressures, priorities, and trade-offs.

And maybe one of the hardest parts of being a software developer isn’t learning a new framework.

Maybe it’s learning that not every codebase will match your ideal version of software engineering.

Compliance Document Management Is Still More Painful Than It Should Be

Angga Jiyan — Sat, 16 May 2026 12:26:28 +0000

Organizations today handle massive amounts of compliance-related documents.

Things like:

certifications
background checks
ID verification
signed consent forms
contractor requirements
licenses
onboarding documents

The problem is that most teams still manage these using:

spreadsheets
email attachments
shared drives
WhatsApp groups
manually chasing people for updates

As organizations grow, that process quickly becomes difficult to manage.

Missing one expired certification or unsigned document can create operational and compliance risks.

That’s where platforms like DocuLocker come in.

What Is DocuLocker?

DocuLocker is a compliance document management platform designed to help organizations automate document collection, tracking, and compliance monitoring.

It is commonly used by:

non-profit organizations
sports clubs
schools
healthcare organizations
franchise networks
professional associations

The platform focuses on helping organizations manage compliance requirements for:

volunteers
contractors
staff members
participants
operational teams

Instead of manually tracking compliance through spreadsheets and emails, administrators can manage everything from a centralized dashboard.

Why Compliance Document Management Matters

One of the biggest operational problems in organizations is not collecting documents.

It’s maintaining compliance over time.

People join.

People leave.

Certifications expire.

Background checks need renewal.

Policies change.

Without a proper system, administrators spend a huge amount of time manually following up.

This is especially difficult in industries where compliance requirements constantly evolve.

Features That Make DocuLocker Useful

Automated Compliance Checklists

Organizations can create compliance workflows and assign required documents to individuals or groups.

For example:

onboarding requirements
volunteer verification
annual certification renewals
contractor compliance

This creates a more structured process instead of relying on manual reminders.

Automated Reminder Notifications

One of the most useful features is automated follow-up.

The system can notify users when:

documents are missing
certifications are expiring
signatures are incomplete

This reduces the need for administrators to manually contact every member.

Real-Time Compliance Dashboards

DocuLocker provides visibility into compliance progress across teams and organizational structures.

Administrators can quickly see:

who is compliant
which documents are missing
checklist completion progress
compliance status across departments

This becomes especially valuable for larger organizations.

Secure Document Collection

The platform supports multiple compliance-related document types, including:

certifications
licenses
background checks
ID cards
signed declarations
consent forms

It also includes digital signature support to simplify approval workflows.

Bulk User Management

For organizations with many members, CSV import and group management tools help reduce administrative work.

Instead of adding users one by one, administrators can manage compliance at scale.

Security and Compliance Features

Security is a major concern in document management systems.

DocuLocker includes several security-focused features such as:

AES-256 encryption
two-factor authentication (2FA)
GDPR-focused compliance handling
audit trail logging

The audit trail records:

document submissions
updates
notifications
compliance history

This helps organizations maintain accountability and regulatory visibility.

Why Compliance Platforms Are Growing Fast

More organizations are moving away from manual compliance management.

The reason is simple:

Manual processes do not scale well.

As compliance requirements become more complex, organizations need systems that can:

automate document tracking
reduce administrative overhead
improve visibility
maintain security standards
simplify audits

Compliance document management software is becoming less of a “nice-to-have” and more of an operational necessity.

Managing compliance manually is difficult, especially for organizations handling large numbers of people and documents.

Platforms like DocuLocker help centralize:

compliance tracking
document collection
certification monitoring
approval workflows
compliance visibility

As organizations continue to digitize operations, tools focused on compliance automation will likely become increasingly important.

If you want to learn more about the platform:
https://www.doculocker.com/