Skip to content
View hpmine42's full-sized avatar

Highlights

  • Pro

Organizations

@seekra-se

Block or report hpmine42

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.

Content in all repositories owned by your account will be closed.
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
hpmine42/README.md

Hi πŸ‘‹, I'm hpmine42

Typing SVG

Profile Views GitHub Followers Email Status


> whoami

$ whoami
hpmine42

$ cat about.txt
Developer.
I write software, then I read it, then I apologize to it.
Most of my bugs are features that haven't been documented yet.

$ git status
On branch main
nothing to commit, working tree clean
(4 uncommitted crises)

πŸš€ Featured Project

enough. project

enough.
A minimalist private messenger focused on simplicity, privacy and meaningful conversations.
No tracking, no ads, no "we've updated our privacy policy" emails. Revolutionary, I know.

Live Demo Source Code

React TypeScript Supabase


πŸ› οΈ Tech Stack

TypeScript JavaScript React Node.js Supabase PostgreSQL Git

(The bare essentials, plus whatever the current side project demands. Occasionally I ask an AI for help - but I do read the answer.)


πŸ“Š GitHub Stats

GitHub Stats Top Languages

GitHub Streak


πŸ’­ Developer Beliefs (unpopular opinions)

  • There are two hard problems in computer science: cache invalidation, naming things, and off-by-one errors.
  • "It works on my machine" is a valid deployment strategy β€” if you ship the machine. The cloud is just someone else's computer anyway.
  • 0-indexing is correct. Everything else is a rounding error.
  • I'm not afraid of undefined. I'm afraid of undefined that only appears on Fridays at 16:55.
  • My most reliable code reviewer is a rubber duck. Approval rate: 100 %. Comments: 0.
  • Premature optimization is the root of all evil β€” except for that one console.log I left in production. That one is load-bearing.
  • I had a problem, so I used regex. Now I have two problems, and one of them is catastrophic backtracking.
  • Dark mode, because light attracts bugs.
  • If the tests pass on the first try, be suspicious. Something is simply not being tested.
  • Comments are for the next developer. I write them for the version of me that exists 6 months from now, who is technically a different person and definitely hates me.
  • git commit -m "final" is not a message. It's a historical document of optimism.
  • Legacy code is code written by someone who knew exactly what they were doing, six months ago, and that someone was me.

πŸ“ˆ Contribution Analytics

GitHub Contribution Analytics


🐍 Contribution Snake

GitHub Contribution Snake

The only snake I'm not afraid of. It runs on a cron job at 00:00 UTC, which is the most reliable code I own.


πŸ“¬ Contact

Open to collaborations, code reviews, and arguments about semicolons.
Best reached by email β€” response time follows an exponential distribution.

Pinned Loading

  1. hpmine42 hpmine42 Public

  2. enough enough Public

    Minimalist private 1:1 messenger focused on privacy, security, and simplicity. Built with React, TypeScript, Vite, and Supabase, featuring Signal Protocol-based end-to-end encryption, secure recove…

    JavaScript 2