It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
"In general, on a working day I (easily) spend 12+ hours working. This has been going on for the past couple months." <- this is the problem. Your brain isn't built to go full bore on problem solving for the bulk of your waking hours. You can do it for a while, but it's like redlining an engine: you go faster temporarily, but it's not free energy. An engine's components degrade and it eventually breaks down; a person burns out, and, not to put too fine a point on it, eventually breaks down.
Attending university and holding down two jobs, part-time or no, is a lot. If you can dispense with one of the three, do it, and replace the time you formerly spent on it with something that isn't programming. Maybe take a short break from development entirely to recharge, go camping or something; it sounds like you might need it. Take stock of your passion projects and evaluate how much time you can spend on them without running yourself ragged, but don't give them up entirely! They are work in their own way so you need to watch your commitments, but it's important to have things you do for yourself.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"In general, on a working day I (easily) spend 12+ hours working. This has been going on for the past couple months." <- this is the problem. Your brain isn't built to go full bore on problem solving for the bulk of your waking hours. You can do it for a while, but it's like redlining an engine: you go faster temporarily, but it's not free energy. An engine's components degrade and it eventually breaks down; a person burns out, and, not to put too fine a point on it, eventually breaks down.
Attending university and holding down two jobs, part-time or no, is a lot. If you can dispense with one of the three, do it, and replace the time you formerly spent on it with something that isn't programming. Maybe take a short break from development entirely to recharge, go camping or something; it sounds like you might need it. Take stock of your passion projects and evaluate how much time you can spend on them without running yourself ragged, but don't give them up entirely! They are work in their own way so you need to watch your commitments, but it's important to have things you do for yourself.