• 0 Posts
  • 165 Comments
Joined 9 months ago
cake
Cake day: December 25th, 2023

help-circle






  • Hey, I like the initiative of sharing this!

    One major point stood out to me. When reading CVs I try to match the statements with the experiences. I didn’t manage to map them. Example: you improve processes - when and where?

    Either adjust the statement to the stations or vice versa. For every statement you should have a recent backing.

    The second thing is the title part: this will be very hot or miss depending on the reader. Either way I recommend putting explanation and title either in one paragraph or very close together. If this would’ve need on my desk and I’d be in stress I wouldn’t have read beyond it just because it looked like an isolated joke going directly into the serious next block.

    Hope this helps!





  • User perspective:

    If you want something big I’d pitch nixos. As in the core distribution. It’s a documentation nightmare and as a user I had to go over options search and then trying to figure out what they mean more often than I found a comprehensive documentation.

    That would be half writing and half coordinating writers though I suspect.

    Another great project with mixed quality documentation is openhab. It fits the bill of more backend heavy side and the devs are very open in my experience. I see it actually as superior in its core concepts to the way more popular home assistant in every aspect except documentation!

    That said: thanks for putting the effort in! ♥



  • You don’t! You observe the result. When no interaction happens the resulting pattern is described well with wave functions. If interaction happens to determine which slit it is traveling through the double line result is seen and can be described by mechanical functions.

    This “we have math for both results” for interpreted to “has properties of both wave and particle”. Which I guess was one press release away from n"it’s both and depends on if I’m looking!"