progfolio

I'm particularly interested in hearing about use cases I might not have considered.

Humanity.

lol

I usually go left to right, top to bottom.

Be specific. You don't really give any examples for why or how one would influence the other. If you've got both bouncing around in your skull, of course they do. It's a question of how and to what degree.

It's also interesting that you've framed it as "enjoying music" (consumption) and "coding" (production). Would "enjoying software" make one a better musician or composer?

They both seem to dance on the fine line of structure and freedom.

This could apply to almost anything.

100% no. Don't bother replying. I can't be convinced otherwise.

100% yes. Don't bother replying. I can't be convinced otherwise.

blimpy blimpy blimpy, blimpy blimp'y limpy b. blimpy blimpy blimpy limpy b blimp'y blimpy blimpy blimpy blimpy blimpy (limpy b blimp'y blimpy blimpy) blimpy blimpy limpy b blimpy blimpy blimpy blimpy limpy b blimpy blimpy blimpy limpy b limpy b?

Agreed

limpy b

blimpy?

--force-blimpy

bloated

"blimpy"

limpy b :(

Can anyone articulate why there is a group of people who seem to really like this video?

blimpy

Please see https://github.com/progfolio/blimpy#usage

limpy b limpy b limpy b

blimpy-mode forgave my student loan debt

:blimpy!

blimpy.

blimpy?

A lot of people don't know how.

Currently working on a speedrun split timer written in elisp:

https://github.com/progfolio/speedo

I've also written a real-time game pad input visualizer (heavily inspired by Chris Wellon's work here:

https://nullprogram.com/blog/2016/11/05/)

I did this for a couple of reasons. I couldn't find a decent split timer that was:

- available on Linux

- not Electron/browser based (These worked well enough, but at the cost of high CPU usage, which caused hiccups when recording gameplay)

I was easily able to set up the timer so that I can feed inputs to anti-micro, which are forwarded to Emacs. This allows me to control everything from the game pad. I also have a feature that allows me to record a mistake during a run. I have commands which can then pull out mistakes for a given range across multiple runs to analyze where I need to practice most.

Still a work in progress, but it's been fun to work on.