From Frontend to Full-Stack

Introduction

Joining Goodwings changed the way I think about development.

Up to that point, most of my experience revolved around building websites, both frontend and full-stack. Over time, though, I became more interested in larger application-oriented systems, how services communicate, how data flows through a platform, and what actually happens behind the UI users interact with every day.

This role gave me the opportunity to explore that side properly.

Moving Beyond Websites

I started working more closely with backend technologies, primarily Laravel and PHP, building and maintaining application logic, APIs, and internal services.

The focus shifted from mostly website-based projects to larger applications with more complex data flow, integrations, and business logic.

I worked with relational databases like MariaDB, handled API integrations, and spent more time thinking about architecture, performance, and data consistency.

The challenges became less about individual pages and more about how entire systems communicate and behave under real-world conditions.

Learning to Think in Systems

Working on larger applications pushed me toward a more system-level way of thinking.

Building features was no longer just about creating interfaces. It involved designing endpoints, structuring data, handling edge cases, validating requests, and making sure different parts of the application communicated reliably with each other.

I also became more aware of things users never directly see, performance bottlenecks, background jobs, security concerns, logging, and how small backend decisions can affect the entire product.

That shift helped me move beyond thinking in pages and components and start thinking more about applications as connected systems.

Working With Docker & Environments

Alongside backend development, I also started working with Docker.

Containerized environments made development more consistent across the team and introduced a more structured way of managing dependencies, services, and local setups.

It also gave me a much better understanding of how applications actually run outside of a local machine, something you do not always think deeply about while building mostly client websites.

That naturally pulled me closer to infrastructure and deployment-related topics.

Exploring DevOps & Security

As I became more comfortable working on the backend side, I also started exploring DevOps-related concepts.

I worked more with environment configuration, deployment workflows, application security, and general infrastructure awareness. While I’m still growing in that area, it helped me better understand the full lifecycle of an application, from development all the way to production.

It also made me appreciate how much work happens behind the scenes to keep systems stable, secure, and maintainable.

Connecting Both Sides

My previous experience building websites remained valuable throughout the transition.

Understanding frontend development helped me design APIs and backend solutions with the user experience in mind. At the same time, working more deeply with backend systems gave me a much clearer understanding of how modern applications are structured behind the scenes.

Being able to understand both sides of development changed the way I approach problem-solving and collaboration within a team.

Conclusion

My time at Goodwings significantly expanded the way I think about software development.

It pushed me beyond traditional website development and into understanding larger full-stack applications, how systems communicate, how infrastructure supports them, and what it takes to build reliable software in real-world environments.