So you go to this random web thing that some person named fronx, or @fronx or whatever, put up, with the intention of finding out who this person is, what they've worked on, what they're interested in, what they care about, and whether you should care about them.
So in other words, the plan was to basically web-stalk them at the equivalent of an open house day they're hosting. Good. Great. You've found the place. Woohoo. Yay. High five. And all that. Awesome.
Now, here is the information you're looking for, written by the author:
Hey, I'm fronx. If you're wondering if that's my real name: yes, it is.*
I write code for a living, and I especially enjoy building tools for people that help them see things, make decisions, and do their work. I enjoy working on things that matter to the people who use them. When they stop caring, so do I.
What I currently do: I learn things. Like, whatever I want. Because I enjoy doing it and because knowing more things might get me an interesting job. Who knows.
Specifically, I am learning how to write C programs that don't only work, but are also nice and elegant, I am learning about some of the more advanced C++ features such as template metaprogramming, and I am reading about and playing with a few of Haskell's type system extensions, including functional dependencies, GADTs, and type families. It's quite interesting.
Sometimes I write about things I've learned.
The other thing I do is teach. I am teaching a friend programming fundamentals. It's one of the most enjoyable things one can do. It teaches you so much about learning and what's hard and what's easy for different people, and how to think your own and someone else's thoughts at the same time. And sometimes you find out that you've been conflating distinct concepts without ever really noticing. (You should totally get yourself a student and try it.)
Before that, I worked at a Berlin company called Infopark doing web projects for large companies. That was fun for some time. I learned how to work with external dependencies, how to communicate with non-technical people, and how to deliver on time, or find compromises, or inform people early enough that it's not going to happen, for certain reasons. The only thing I wasn't satisfied with was the short-term nature of projects. I have since learned that it's quite interesting to watch your decisions play out over time and have expected as well as unexpected effects.
Before that, I did my Bachelor of Engineering. My favorite subject was signal processing; because it was easy for me to visualize what was going on, and see through what seemed like complex math to a lot of others.
Drums. This paragraph is dedicated to drums. Drums are nice. Like, an actual drum set, ideally. In combination with 2 or 3 others who know what they're doing on their respective instruments, ideally.
Photos. Photos is the other thing. Taking photos and posting them somewhere on the internet has become such an ephemeral activity, but that doesn't make it less enjoyable.
*for most intents and purposes [⬆]