Feedly [0] (web app and on IOS) has been amazing since Google Reader died. On IOS it makes flipping through items and saving them for later a smooth and relatively fast experience.

[0] https://feedly.com

Yes, plus it can be used as a RSS “engine” for iOS reader apps such as Reeder, which is my favorite way of consuming my feeds.

Related post from yesterday: We found North Korean engineers in our application pile [0]

[0] https://news.ycombinator.com/item?id=41353079

Have you tried Blackhole? It’s a loopback device for macOS.

https://github.com/ExistentialAudio/BlackHole

Nice! How is this different from Vampr? [0] they use (or at least, used) the same tagline: ‘Tinder, but for musicians to collaborate’

[0] https://vampr.me/

It might be relevant, because labor isn't just about working in a silo. A significant part of work might be done in a team setting, where communication, feedback loops, constant interaction, collaboration, code reviews, team spirit, and more are important.

I'm not suggesting should offer your free time to help cultivate this, but in my experience it does help with building a good work relationship with your colleagues - either outside of work or even at lunch - which then improves the outcome of the labor.

I use the IOS app BirdNET for this - also using the same dataset from Cornell Lab of Ornithology. Highly recommended.

From the Q&A [0]:

>> Can I work with the digital nomad visa?

>> No. Travelers visiting under the visa cannot be hired or involved in any profit-making activity during their stay.

Isn’t the point of a digital nomad that you are able to work from anywhere?

[0] https://www.digitalnomadskorea.com/post/everything-you-need-...

Fun fact: One of the most most popular Gouda cheeses sold in The Netherlands is actually made in New Zealand.

What type of issues did you run into?

We've been running Zalando Postgres Operator for all our prod and dev clusters (around 100 in total) and couldn't be happier.

My impression is that when it works it works well but when it doesn't it doesn't help you that much. We have had two main issues:

- Can't set up two separate clusters in the same kubernetes instance because some cluster specific configuration is inexplicably set globally in the operator.

- Documentation and error messages are cryptic. Have to do a lot of trial and error to compensate for that. Maybe the issue here is a lack of experience with the stack used. Like Spilo and Patroni.

The suggestion would be something to do after the pay is already negotiated. You’d want to leave as much room to grow as possible - both money wise as well as your title.