Working on a class that I'd like to use in a library (not for work) and think I'd appreciate external opinions!

If not, where else could I post code for critique? Thanks

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 2 years ago (1 child)

I'm sure there's plenty of people willing to πŸ’© all over your code.

  • source
  • hideshow 2 child comments
  • [–] 5 points 2 years ago (2 children)

    i'm not so sure. Shitting over code takes actual effort and skill. Wish more people took the time.

    Have never had the experience. Feel free to prove your point

    https://github.com/msftcangoblowm

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 2 years ago (1 child)

    I'm not going to dare to lecture the author of pytest-logging-strict. Thank you for your service. 🫑

  • source
  • parent
  • hideshow 2 child comments
  • Thank you for your kindness. This is the first time ever anyone thanked me for creating and publishing FOSS

    For Python packages you wrote, if has hardcoded logging configuration, let me know. Would be a unique way i can contribute.

    Just point me at the package(s)

  • source
  • parent
  • [–] 3 points 2 years ago (1 child)

    A+ for humor usage. Shitting on code is time consuming, so you're not going to get rekt by me...

  • source
  • parent
  • hideshow 2 child comments
  • This thread is about gists. Totally missed the point by posting my entire profile. Quickly regretted it

    So embarrassing. Opps

    The embarrassment was motivation enough to look up how to make a gist.

    create a branch (switch to the branch)

    remove the code that would be in the gist

    commit the branch

    revert the commit

    git push

    share the revert commit

    Although remember how still have never tried to create and share a gist

  • source
  • parent