Hello, Im Darrell Walker

Professional Self-Assessment:

Completing the SNHU Computer Science program and building this ePortfolio pushed me to turn classroom skills into working software. Across the capstone I designed, built, and refined StockVault, an Android inventory app that runs fully offline on SQLite. Turning an early CRUD list into a smooth product-inline edits, typo-tolerant search, and per-item alerts-helped me showcase strengths I’ll bring to a team: clear problem framing, iterative improvement, and shipping reliable code.

Strengths, goals, and values.

I value simple designs that solve real problems and are easy to maintain. My goals are to grow as a full-stack/Backend engineer and to keep security and usability as non-negotiables. Outside class, I prototype hardware + software using a Raspberry Pi, which keeps me curious and hands-on.

How I work with others.

1.) Collaborating in teams: In course projects I split work into small, testable tasks, used Git branching, and wrote clear notes so my peers could review quickly.
2.) Communicating with Customers: I summarize trade-offs in plain language (performance vs. complexity, on-device vs. cloud) and show short demos with POC so decisions are based on behavior, not theory.

Core CS skills I apply.

1.) Data structures & algorithms: In StockVault I used an in-memory list with a custom restock comparator (quantity–threshold → age → name) and a lightweight edit-distance search with debounce for smooth typing. These choices kept operations O(n) and responsive on mobile.
2.) Software engineering & databases: I designed a minimal SQLite schema (items, item_prefs), wrapped writes in transactions, added indexes, and separated UI from data with a repository layer. I plan to migrate to Room + DataStore for type-safe DAOs and easier migrations.
3.) Security: I practice least-privilege permissions (Android 13 notifications), input validation, and local-first storage. A production build would add credential hashing/biometric, a privacy policy, along with SQL Hashing.

How the artifacts fit together.

1.) Software Design & Engineering: shows UI/UX improvements and code structure (inline editing, repo layer, notification channel).
2.) Algorithms & Data Structures: explains the ranking/search choices that make the app feel fast.
3.) Database: documents the schema, integrity rules, and migration approach that make data reliable.

Together, these artifacts demonstrate the full path from problem to product: requirements → design → algorithms → data layer → user experience → release-readiness. They also reflect how I work-start simple, measure, refine, and leave the codebase cleaner than I found it. I’m ready to contribute those habits and skills on a professional team.