Professional Engineering

Higher Education.

Internal application delivery, Java and SQL development, frontend modernization, testing, documentation, and production support.

Organization
Community College of Baltimore County
Role
Associate Web Developer
Period
Jan 2020 – May 2021
Platform
Internal Academic & Administrative Systems
A laptop and books in a university study space representing higher-education technology

Context

My higher-education experience involved internal academic and administrative applications supported by Java backends, SQL data workflows, Angular interfaces, application servers, tests, documentation, and production support.

As an earlier professional role, it established practical foundations in maintaining existing systems, modernizing interfaces incrementally, and supporting software used by a real organization.

Engineering Scope

  • Backend development
  • Data and reporting
  • Frontend development
  • Modernization
  • Testing
  • Production support

Selected Outcomes

  • Contributed backend, database, and frontend capabilities for internal systems
  • Supported modernization across AngularJS and Angular application code
  • Added and maintained automated tests and technical documentation
Systems & Responsibilities

Internal application development

Contributed backend, database, and frontend functionality for academic and administrative systems.

Internal software still requires dependable behavior, maintainability, and clear support practices for organizational users.

Frontend modernization

Worked across AngularJS and Angular interfaces with state-management patterns.

Incremental modernization improves maintainability without assuming every established workflow can be replaced at once.

Support and documentation

Participated in testing, documentation, deployment, and production support.

Understanding how users and operators experience the system is an important part of learning to build maintainable software.
Engineering Challenges

Established application environments

Challenge: Internal applications combined existing Java application servers, SQL workflows, and evolving frontend technologies.

Approach: Contributed within Spring MVC, JDBC, AngularJS, Angular, and established deployment environments.

Consideration: Incremental change lowers disruption but requires engineers to understand both existing constraints and newer implementation patterns.

Data-backed reporting workflows

Challenge: Administrative applications relied on accurate SQL-backed data behavior and reporting.

Approach: Worked across Java backend logic, JDBC, and SQL as part of application delivery.

Consideration: Correctness and query behavior matter as much as interface presentation when software supports institutional processes.

Production support

Challenge: Issues in internal applications needed diagnosis across frontend, backend, database, and deployment layers.

Approach: Supported testing, documentation, troubleshooting, and application-server environments.

Consideration: Supportability improves when code, deployment knowledge, and documentation evolve together.
Technology by Responsibility

Backend

Java · Spring MVC · JDBC

Data

SQL · Redis

Frontend

Angular · AngularJS · NgRx · JavaScript · AJAX · JSON

Testing

JUnit · Jasmine · Postman

Runtime and build

JBoss · WildFly · Tomcat · Maven

Collaboration

Git · GitHub · SVN · Agile delivery

Improvements, Decisions & Outcomes

Improvements

  • Incremental modernization of frontend application behavior
  • Maintainable backend and database changes for internal workflows
  • Greater confidence through backend and frontend testing
  • Clearer documentation and production-support knowledge
  • Continued delivery within established application environments

Decisions & trade-offs

Modernize incrementally

Allows established internal workflows to continue while newer frontend patterns are introduced.

Teams must temporarily understand and support multiple generations of technology.
Keep data access explicit

JDBC and SQL provide direct control and visibility for internal data workflows.

Direct data access requires careful query design, mapping, validation, and maintenance.
Treat support as engineering feedback

Production issues reveal where implementation, deployment, and documentation need improvement.

Support work competes with feature delivery and requires disciplined knowledge sharing.

What I learned

  • Existing systems deserve careful understanding before modernization.
  • SQL correctness and access patterns directly affect application reliability.
  • Production support builds stronger mental models than isolated feature development.
  • Documentation is part of maintainability, not an afterthought.
  • Progression comes from learning how frontend, backend, data, and runtime concerns connect.