hiepph

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".

But still, we should strive for writing the best "clean code" that we set out to write. So "clean code" here is subjective and bound to the individual. Normally, business and absurd deadlines force us to lessen that principle—that's what I call "ugly code".

For me, the "Inbox rules" hasn't been working as I expected—some emails doen't end up in the folder that I want. The experience of editing rules feels awkward.

And I cannot "bridge" Thunderbird to Tutanota to apply my filters.

Recent price change was the last straw to make me another end-to-end encrypted alternative.

Recently I switched to Proton Mail with advanced Sieve filter [1] and feel much happier.

[1] https://proton.me/support/sieve-advanced-custom-filters

Observability! Grafana, Prometheus, Loki, OpenTelemetry, you name it.

I'm digging deeper into the architecture of those open source tools—how they work under-the-hood—and not only at the superficial surface (deploying the stack and tune some parameters).

I'm also trying to find some free time to contribute to some open source projects. It's not hassling but I just want to give back to the community—who gave me the career and many awesome tools already.

Getting into contributing is not easy, I have to admit. It's like you're having a second job and no one has the dedicated resources to help you understand the internal architecture. All you can do is submitting the bugs, questions, pull requests and hope for the best.

Factorio is fun but the way I play it was unhealthy—several hours of Factorio after 7 hours of sitting in front of a computer. I had to give it up to find a healthier lifestyle—e.g. running, hiking, or taking a walk in nature.

I do want to come back to Factorio since it's an awesome game, but currently I cannot find the good timing for it.

Ansible makes mutable changes to the OS, task by task.

Nix is immutable. A new change is made entirely new, and only after the build is successful, all packages are "symlinked" to the current system.

Fedora Silverblue is based on ostree [1]. It works similarly like git, but on your root tree. But it requires you to reboot the whole system for the changes to take effect. Since Nix is just symlinked packages, you don't need to reboot the system.

More detailed explanation here [2].

[1] https://github.com/ostreedev/ostree

[2] https://dataswamp.org/~solene/2023-07-12-intro-to-immutable-...

If only they had configuration files...

Some more features that I like:

+ Bottom posting can be set as default.

+ Selected text are automatically quoted when hitting reply.

+ Many add-ons and utilities are available: DKIM verifier, Mail Hop viewer, Mail Agent viewer, etc.

I tried to find an alternative but I couldn't either.

I met this problems twice, when registering and resetting my password. Reloading the page (resending the request) solved the problems.

The enterprise versions of their products are ridiculously expensive. They're always trying their best to charge you with mistakes (e.g. number of connecting clients). The pricing on the landing page is just a fraction of the real price. That's a big turn-off for me. It's true that I don't want to have the hassle of setting up a production-ready Vault, but seriously, if Hashicorp keeps charging like that I'd would really consider a different solution.

I also had a hard time choosing between Python and Ruby for my goto scripting language. But given Python community is more active outside of webdev, I also chose to stick to be more professional on Python.

For the case of Javascript, (I think) it followed "Worse is better" principle. It's been trying to be as practical as possible. And it's everywhere even though it was not really great (until new standards and Typescript come). So a new joiner would pick Javascript so he/she can have a wide choice of possibility later.

Same things are happening with Python. And if I have to be honest, if I come from a different profession and want to change my career, I would pick either Python or Javascript for my first step.

I would say it has a "better" scripting languages syntax.

For example, compare this in zsh:

``` case $input in "foo") echo "Input is foo" ;; "bar") echo "Input is bar" ;; ) echo "Input does not match any case" ;; esac ```

with this in Fish shell:

``` switch $input case "foo" echo "Input is foo" case "bar" echo "Input is bar" case "" echo "Input does not match any case" end ```

And it was a really small example. Fish can do much more with "simpler" and not arcane syntax.

Fish also has `string` to work with string much much easier [0].

You miss `oh-my-zsh`? Fish has `oh-my-zsh` [1].

You miss integration with `fzf`? Fish also has it.

One caveat is Fish is not POSIX-compatible. But I don't find it a compelling reason to not using it.

Personally, I use Fish as my main shell. I do use zsh/Bash in my company though since they're more ubiquitous.

[0] https://fishshell.com/docs/current/cmds/string.html

[1] https://github.com/oh-my-fish/oh-my-fish

I heard in a Podcast that they are inspired by game development workflow (e.g. Unity) where multiple teams can work together in a unified way. This reduces "niche" power like CLI commands that only some of sysadmins can wield.

Personally, as an infrastructure engineer, I still prefer CLI and everything as (text) code. But I'm open to change if this "second wave" could take off.

This. I personally can switch but how do I communicate with my other colleagues? It's hard to convey people to move into a whole new stack without significant effort.

Emacs was called "obsolete", "hard to use", "bizarre", and other things.

Well, Emacs isn't designed for a common user, but for a power user. From my experience, first time using Emacs was really frustrated.

In contrary, VSCode, Atom, Sublime Text etc. were usable right from the start. But these IDEs didn't stick for me. Easy come, easy go, I guess.

Emacs and Vim, although took a lot of effort to configure them into usable text editors/IDEs, stick with me 'til these days and I'm continuing to use them in the future. The power of configurations are astounding and I can shape them into whatever I want.

I learned this lesson: focus on mastering the language and understanding the fundamentals of networking instead of chasing new shiny web frameworks.

Web frameworks come and go, but the language and network protocols are here to stay.