@GergelyOrosz I asked for pricing on a tool through on-site chat. Took 2 declined let’s jump on a call, 2 people and 3 days to get a quote 🙈 (to be fair long duration was mostly due to 9h time zone difference)
@mfussenegger Full ack. There are so many ways for useful contributions to OSS. Unfortunately culture and tooling sway this too much to code contributions
@mfussenegger That’s basically usability testing https://t.co/XT8IK8lElk 😊
I can tell from personal experience how helpful this is. We used it on a SaaS product but this can be mapped directly to software tooling / libraries / etc
@chaudum @mfussenegger @matryer My two cents:
* for common patterns match the usual style used in your code base
* if there is no usual style decide on one style and favor this / refactor to it (as it’s nitpicky let the people decide who care)
Probably worst scenario is if you mix variants
@mfussenegger @chaudum Wondering why Mittagspitze is not showing up 🤔
Maybe due to slightly different spellings and some peaks with added names for differentiation 🤷🏼♂️
https://t.co/1s8pLYo1Fg
@mfussenegger I assume it’s difficult to cover every aspect in detail and still keep a video in a YouTube-compatible length 😅
Don’t have links on these topic. If I do I also typically struggle with verifying contents and judging trustworthiness 😞
@mfussenegger Have you seen the kurzgesagt video on this topic? https://t.co/IWuABDzPBU
You find all sources in the description. Feels to me quite extensive and balanced
@kaeff I also like the additional indicator of what past me/us thought this test will do and where it ends up. Continue if test name and test match. If there is a mismatch take another look at code and test
@GergelyOrosz Writing out my reply helps me get it out of my system and restore some peace of mind.
If I actually send this reply or not was a decision I left to future me 😅