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
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
14 Comments
m_f@discuss.online · 22 pts · 1y
IMO this is a good fit. There's no rule against it, and I'm a fan of not splitting up communities until really necessary. Maybe once there's so many people posting code for review that it becomes annoying to find other posts, then it'd be worth creating a new code review community or something.
Ategon@programming.dev · 13 pts · 1y
Theres technically a code review community at !code_review@programming.dev although ive seen some people also post code reviews in the language/engine communities
eager_eagle@lemmy.world · 11 pts · 1y
gist.github.com
pastebin.com
Ategon@programming.dev · 22 pts · 1y
we also host an instance of opengist at https://blocks.programming.dev as an alternative to those if wanted
0101100101@programming.dev · 1 pts · 1y
Awesome! Maybe this should be added to the topic of each language-specific channel?
Artyom@lemm.ee · 8 pts · 1y
Maybe when Lemmy gets bigger, I'd like to have a Python community for news and a learnpython community for code help like we had on reddit. However, this community isn't huge, so go ahead and post it here.
Balthazar@lemmy.world · 7 pts · 1y
I'm sure there's plenty of people willing to 💩 all over your code.
logging_strict@programming.dev · 5 pts · 1y
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
Balthazar@lemmy.world · 4 pts · 1y
I'm not going to dare to lecture the author of pytest-logging-strict. Thank you for your service. 🫡
logging_strict@programming.dev · 3 pts · 1y
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)
Braindead@programming.dev · 3 pts · 1y
A+ for humor usage. Shitting on code is time consuming, so you're not going to get rekt by me...
logging_strict@programming.dev · 2 pts · 1y
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
solrize@lemmy.world · 1 pts · 1y
Better to use a paste bin and ask specific questions rather than just please choose l critique this code.
muntedcrocodile@lemm.ee · 1 pts · 1y
I dont see why not.