I've been thinking about this, but I don't really know. The podcast is a lot of Clojure, which by itself might be an interesting language to learn. Some people report that learning Clojure was different than other languages, eg Uncle Bob, Gene Kim (see "Love Letter to Clojure") or I think even Paul Graham.
Maybe the Effectively Isolated Serie might be interesting (ep 021-027). Oh, and Cooking Up Composition, about composing functions (ep 093-098).
For example, one can start separating pure functions from side-effects, aiming for aggressively minimal side-effecting functions. Applying this approach to calling REST APIs, one would first create a full request (including the http method, body, headers, etc) in a pure function, and only then send that request to the wire. With such a split, one can easily unit-test the request construction (it's a pure fn), and also explore the request.
It was mind-bending to me when I first heard it. The podcast is full of such approaches and it seems that Chris and Nate, the hosts, have quite some battle scars to source from.
Reminds on Rich Hickey ranting about touch screens in cars [1] in Design in Practice:
> We do not have feature X" is never a valid problem statement. If you need proof of this you only need to look at a modern car which has a touch screen where no one said, "I need to slide my finger on some random piece of glass to a precise point to set my blower in my car while I am driving." No one has ever said that, right? But somebody did say, "We need touch screens because young people will never buy our cars." This is what happens when you are not talking about the problem.
I worked shortly for an airline, breathing carosine weekly, and so then switched back to EV charge-points and solar. I am not sure if it makes real impact, but I feel subjectively better and find more satisfaction on every day basis.
I started as a full-time employee, now I work remotely as a freelancer/contractor.
I am pretty glad for the switch. The type of work I do (data engineering, tech leadership) is quite similar to the airline business; but in the clean-tech side.
For finding a job, maybe remote job listing sites might help [1], or then clean-tech related job sites.
Love Obsidian as well, for about 1y now. I have a tech background, but typescript and aws serverless were new to me, so I decided to learn-in-public.
Regarding categorization (and design), I was inspired by Julia's web: https://jvns.ca/
For technical things where I'm a newbie, I'm trying to learn-in-public [1]. I write a TIL usually at the end of the day, it typically goes quickly.
In those cases where the matter is private (maybe 1/4 of all), I attempt to document it in company's knowledge base or at least share it in the company chat.
- Developing empathy towards myself first, that is, being able to observe feelings that arise within me and then being able to accept these feelings as they are. I have found this to be very relieving. A technique that helped me was meditation; training the mind like a muscle to be able to observe & recognize feelings.
- Turning this outwards to others, the works of Marshall Rosenberg on the NonViolent Communiction (NVC) [1] had a profound impact on my perception of feelings of others. I'm trying to follow the essence of the book, rather than copying the phrases outlined there. I'm seeing more and more that NVC can be applied to business as well as personal relationships [2]
Applying these to your example, it might be interesting to explore what do you _feel_ when the other person just wants you to listen. What is it that you _need_ out of the relationship and what is it that the _other_ side needs [3]?
Another usecase is tracking hours with Clockify. I was frustrated opening up the web everytime, so I wrote a script using fzf, httpie and jq. Love it now. [1]
This, exactly. Perhaps counterintuitively, having less time enables me to do more.
Also, I stopped doing optimizations & just try to deliver the basics. I realized a lot of time was eaten by optimizations, while other, more important things, were not even done.
I focus at least one third of my learning time on things that dont change, such as principles behind Hickey’s Simple Made Easy, Hamming’s You & Your Research, Brooks’ Mythical Man Month, functional programming, and technical things like SQL, shell.
New tech is a often a container around those, making it easy to grasp it.
Also, new tech also dont have such community & ecosystem around it as older tech, so I keep it on the radar, but dont use in production immediately. Focusing on boring technology, with a spark of novelty where needed.
This. Less flying, less buying, less meet, less consumerism, more local & seasonal food. No need to go full 100%: it would be enough if critical mass reaches a good-enough level.
Maybe the Effectively Isolated Serie might be interesting (ep 021-027). Oh, and Cooking Up Composition, about composing functions (ep 093-098).