Narigo

Docker would be on the list for me - for reproducible environments. Probably JUnit as it was my first real testing framework - for being able to use test driven development for hard problems.

With programming, I had so many "aha"-moments, it's hard to remember them. It's not all about software, but more about understanding the concepts and being able to transfer this knowledge. Being able to pass functions or function pointers. Streaming / piping data instead of a fixed data structure. Interpreted vs compiled languages. How everything we do here only happens through a long list of 0s and 1s and how this clever setup makes us even see graphics on the screen. Or hear audio through a screen reader....

Thanks for the insight! I guess it's a hard problem to solve with these conflicts. I'm wondering how it could be automatically resolved if a user has the same thing open multiple times with changes to the same password...

Did you try diffing the conflicting databases through a tool like keepass-diff before switching?

I'm the author of keepass-diff and built it for my own needs. Looking through the comments here about why people switched from Keepass to Bitwarden, it feels like the compare feature is something that should be integrated to UI clients as many people seem to face this problem. I always assumed it was more because of permissions and better ability to work with it as a team...

The sync conflicts happened to me whenever I left keepass databases open and changed it on multiple devices. Usually, those changes were adding new accounts into the databases or changing a password on one while adding something on the other. This regularly happened when working in a team.

I assumed people would switch from Keepass + database synced on a private server to something else when they started working in teams and need better/easier permission models. :)

As you have mentioned it, I have written the tool keepass-diff (<https://github.com/Narigo/keepass-diff/>) to help me for exactly these conflicts and I could quickly resolve the issues with it. It was still useful enough to let me keep using Keepass. Was it not working for you or was it too hard to use because of how it needs to be set up first? Would you have stayed with Keepass + sync if something similar to this was integrated into UI clients?

I had this problem as well, these conflicts may happen when you keep Keepass clients open and add passwords on two different machines.

I have written a CLI tool in Rust called keepass-diff that may help you with this: https://github.com/Narigo/keepass-diff

I suspect Hugo: https://autoiterative.com/blog/index.xml

I like the sandboxing effect of using Docker. Having node_modules (or any kind of dependencies) not being able to access all files on the host is a big relief - especially since there were attacks on popular dependencies already, stealing wallets or similar.

It's nice to see that I'm not the only one with that intention :)

I have contacted just a few people (every two/three months) and sent them longer texts with specific examples of why something they did or said had a positive impact on me. The channel does not matter to me, it depends on what kind of contact possibilities I have to that person. It's usually a really long compliment, which I let one or two persons, who know the one I'm writing to, proof-read. I want to make sure it conveys the genuine "thank you" and does not make me look like a stalker or trying to flirt.

Since I only got a ~33% response rate, I am unsure whether I should continue doing that - 66% of the people I've contacted probably see me as a weirdo...

According to BayStartUp (they support startups in Germany), they advise you to do both top-down and bottom-up: This way you can validate the results from the extrapolation.