• 0 Posts
  • 33 Comments
Joined 3 months ago
cake
Cake day: August 21st, 2024

help-circle










  • brave also used it to scam people by taking tips for creators who weren’t on the platform. if the creator never signed up, they kept that money.

    and they had an adblocker that replaced ads with their own, making the browser money instead of the site.

    they have actively contributed to making the web worse. saying “at least they’re doing something” is like praising the hard work and entrepreneurial spirit of a mugger.





  • this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you’re interested in. it reads a bit wooden. i get that would happen after you’ve been told to correct your style though.

    to be clear, the original article doesn’t need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that’s not really a part of it (unless it’s funny)



  • your writing overall is good! it’s just a matter of information priority.

    here’s a tip, dunno how applicable it is but i use it when writing technical documentation:

    for each step, explain to yourself why you’re doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.


  • this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying “edit the file”? why symlink systemd stuff to your own home directory?

    the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.