Does anyone else have trouble trying to work out what computational *thing* they want to try and self-learn next? I'm finding I'm being quite hard on myself lately for having 'not learned enough' (which I also know is a tendency I need to challenge), but I also struggle to identify what thing to really try and learn/master next and to stick with it.

I wonder if I should accept that 'mastery of *nix systems' is an 'ongoing thing' rather than a 'study time' thing, but have other floating>

> interests that I struggle to nail down and prioritise a self-taught learning approach with. These include:

* better mastery of git
* SQL databases
* some more back-end Web tech language(s)
* object-oriented python
* more data-science oriented python

Struggling, and being hard on self, for not being able to nail something down and commit to it.

Worth noting that pretty much all of this is hobby stuff and not rly to do with my dayjob.

Playing with some mind-mapping processes to see if that leads to some clarity.

Getting ideas down in a 'mess' like this does seem to help.

(I use labyrinth software - which is quite basic but useful:

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.