hiepph

Proton Mail, Proton VPN, and Proton Pass are the only products I’m using right now. Lumo and other suites feel subpar and inferior. I don’t know why they don’t collect feedback from users like us and put effort into what matters.

This is true. My main use of AIs now, aside from grinding it to code at work, is to clean up my Obsidian notes (which I normally have no time for) and to brainstorm ideas. I can rest and focus on my work, whilst grinding the agents to run 24x7, and let them report to me what they've cleaned up or researched. It has saved me so much time, since now I only have to review what they've done and pick the direction (and the "taste") I want to go. It releases me from the boring work, and creates me the capacity to read books and explore ideas that I've always wanted to have.

I’m actually impressed by the handwritten blog - really cool concept.

Was it exported by writing on remarkable? How did he include link into the text that he wrote?

Sadly, I have the same experience. It's one of the minus points of using Thunderbird, alongside the lack of the feature for shipping my configurations (e.g. filters) across machines.

He also captured so true the process and meaning behind training to get stronger.

Respect.

True, now it's blocking some VPN IPs, which is annoying.

Agree. Writing communication is essential, and might have more influence than speaking communication, in a remote working environment. The whole OSS movement has been built on this.

> Is there anybody who can share their experiences with issues and workarounds in this area?

Just use your Bash/zsh to run Bash/zsh scripts: `bash script.sh`.

> turned off by it not being POSIX-compliant.

I was like this when I first started using Fish. I spent some time to learn some different syntax to get away from the POSIX-compliance. Overall, I think the saner syntax of Fish is worth the effort. Now I use the terminal much happier.

Besides, 90% of the time I don't need to follow POSIX-compliant. Many scripts or extensions nowadays support Fish.

For enterprise use, I still stick to Bash/zsh. They're the standard.

From my experience, programming and technology communities are already really strong on Lemmy. I'm confident to say that if you care about these topics, moving from Reddit to Lemmy is a good option.

For another categories, they're still small and having struggles gaining traction to have enough users and posts to be lively. But I think it's just a matter of time if Lemmy continues polishing its features and community discoveries.

I used to love Tuta for the tempting price (1eur/month). But now due to the increasing price, poor UX, no bridge to Thunderbird, broken filter rules, I switched to another provider.

I think the only option to make sure it will run in the 10 years is to package the linking libraries and all the dependencies. Container (e.g. Docker) or Nix can solve this, provided that these technology still live in the next 10 years.

> You can configure about anything (which may be a good thing) but all of this "configuration" looks and feels like Apollo 11 Command Module.

I wish I could configure KDE "declaratively" with a configuration file, like what I do with i3.

> The way most people talk about software engineering, you'd think they were some kind of open-source warrior building entire applications from scratch when really they're on the Cancel Prime Membership Button Obfuscation Enablement team at Amazon.

True, if one apply most of the lessons in the article (e.g. "Nobody gives a f** about your clean code") to a well-established open source project, the maintainers will grind you to death.

> I would encourage anybody interested in a professional career (in anything) to zoom out and keep in mind that almost every profession is ultimately about providing service.

> You will primarily work with (and for) other human beings, inside your organization and outside.

I used to be an engineer who always new technology and push a fancy solution to an invisible problem—just for the sake of it. Now I listen more to people on my team, carefully consider pros and cons before adopting a solution. That's the biggest lesson I've learned.

> This is why I go out of my way to praise good work loudly and publicly when I see it.

This sounds true. Some people do the boring job of cleaning code and keeping the system reliable never got a praise. But some people, who never care about the quality of the system, fight the incidents and are called "hero".