I’ll start
After college I started freelancing, doing mainly “creative-technology” gigs, turns out you mainly work on advertisements, and that wasn’t something I wanted to do. I enjoyed a lot projects focused more on live data and interfaces so I shifted more and more to frontend and data-vis work. After few years I opened a small studio - flow-control.io - where I work on professional projects to this day.
I also got in contact with inkandswitch.com where I’m doing part-time research on various end-user programming related topics.
I also work on personal projects (szymonkaliski.com/personal) make music (szymonkaliski.com/music), sometimes interactive art pieces, teach (both workshops, and currently few classes at local university), give talks, etc.
So, to get to the “tools for thinking” space, my personal interest grew out of a few things:
- the need to organise - at first I had at most few projects and some things to do, but over time my work changed to more research/thinking-about-stuff oriented, so a list of checkboxes to check wasn’t really working for me
- data-vis and interface-design work where I mainly work on information-dense interfaces, I can start to see common patterns repeating, but don’t have well structured thoughts on those yet
I also believe that the tools-for-thinking space is very closely related to problems with the way software works today, and the topic of end-user “programming”.
I currently explore this space through personal local-first software, some parts of it are on github to check out:
- https://github.com/szymonkaliski/muninn
- https://github.com/szymonkaliski/archivist
- https://github.com/szymonkaliski/timav
But I think that the ideas behind them might be bit more interesting than the implementations. Working on a blog post about that.