Skip to content
View mjvmiller's full-sized avatar

Block or report mjvmiller

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
mjvmiller/README.md

Hi, I'm Michael πŸ‘‹

I’m a full-stack software engineer building applications across a variety of fields, ranging across:

  • Physics-based predictions of color appearance under different lighting conditions
  • Supply chain data monitoring with an automated pipeline for importing vendor data
  • A parsing library for a proprietary seismic data standard
  • A low-maintenance, NLP-driven second brain system with intelligent reminders
  • Custom scheduling software which helped me orchestrate logistics for the Berkeley Model United Nations conference

I have taken ownership over the design, architecture, implementation, and deployment for all of the projects I have worked on. In doing so, I've greatly enjoyed getting to learn so much about such a wide array of subjects. I am particularly keen on spending more time learning about server infrastructure and networking, and I'm hoping I'll soon have a chance to dive deeper into database internals and operating systems as I build more experience working with systems languages.

I love solving difficult problems, taking on new challenges, and learning as much as I can about the world around me. This field has given me so many opportunities to pursue each of these things, and I am beyond excited to see what the future brings.

My guiding principles as an engineer:

  • Never compromise on security or user privacy.
    • Minimize the surface area for an attack by sandboxing independent services and minimizing access scopes to the barest essentials.
    • Avoid adding external dependencies for functionality that's realistically feasible to self-roll the portion you need.
  • Optimize for YOUR constraints, not Google's (unless you're Google).
    • A 10-node K8s cluster offers no tangible benefit over a single EC2 instance for a service used by 10 people at peak times.
    • Less moving parts -> less room for error -> less time wasted on maintenance
  • Always consider how your architectural decisions will affect the user's experience.
    • Good performance metrics don't necessarily translate to happy users.
    • Sometimes, it is worth it to choose the less-elegant engineering solution if it improves user QoL.

What I am doing now πŸ§‘β€πŸ’»:

  • πŸ“‘ I’m currently diving deeper into network protocols and database schema design.
  • 🧬 Working on-contract for a biotech startup and a colorant manufacturer.
  • 🌏 Contact me on LinkedIn

Pinned Loading

  1. snake-game snake-game Public

    Implementation of the classic Nokia mobile game Snake.

    Java

  2. CCAO-Housing CCAO-Housing Public

    In this project I perform exploratory data analysis on CCAO Housing dataset with the goal of generating a linear regression model for housing prices.

    Jupyter Notebook