Remote
codingjoe 
@codingjoe@fosstodon.org
mastodon
4.6.6
Professional Open Sourcerer 🧙♂️ @ThePSF@fosstodon.org & @django@fosstodon.org member
71
Followers
69
Following
20
Posts
Joined November 23, 2022
GitHub:
Website:
Posts
Special thanks to @amureki@mastodon.social for better #Sentry support in #Django CronTask.
Thanks @getsentry@fosstodon.org for replying so quickly to our questions.
Replying to
@openwebdocs@front-end.social
I think I have to forward the thanks to @jake@mastodon.theorangeone.net
Replying to
@simon@fedi.simonwillison.net
@simon we live in a crazy timeline. Frist, xz, now this. Makes you wonder how many haven't been discovered. I'd certainly fall for it myself.
Replying to
@codingjoe@fosstodon.org
@sarahboyce@mastodon.social but you seem to navigate this fairly well, at least from my own experience. Should you ever find the secret ingredient, do share 😊
Replying to
@sarahboyce@mastodon.social
@sarahboyce@mastodon.social hm... I guess that makes a lot of sense for large projects. Since I mostly do medium projects, it's less so about priorities but communication. The wild mix of English being my second language, non-native contributors, AI and ADHD is a lot to navigate. I know people universally mean well, but all cultures have different ways to express (or not express) this 😅 Some might see self-doubt as a weakness, while I consider it a strength.
Replying to
@benjaoming@social.data.coop
@benjaoming@social.data.coop hehe. I was more thinking just a simple message on every PR to kindly complete a small checklist. It requires another step (which is harder for a bot) but at least you can't bypass it like a PR template.
Same treatment for everyone tho, except for returning contributors maybe... don't know yet.
Replying to
@benjaoming@social.data.coop
@benjaoming@social.data.coop @davidism@mas.to hm… probably something that I could automate with a workflow (bot) response. It's also harder to take something personally if it doesn't come from a person 🤷♂️
Replying to
@sarahboyce@mastodon.social
@sarahboyce@mastodon.social yes, it's making an already hard job even harder. I have been using GitHub Copilot prompts to get better assisted reviews. However, copilot won't address the elephant in the room by itself.
Besides, how wild is it that you can turn that darn thing off…
Replying to
@benjaoming@social.data.coop
@davidism@mas.to interesting. Doing some open source for uni or your resume is something that I am seeing more too. Especially from India, which at least in part is probably attributed to population size, but in other part because AI has killed software offshoring. I usually respond kindly to those requests when I can see some effort and people are responsive.
Reviewing your own code should be the absolute minimum. But how do you say this without sounding like a Finnish kernel dev?
Replying to
@decibyte@social.data.coop
@decibyte@social.data.coop true, helping other engineers with their growth always is.
Mostly my discussion starts with "what do you want to solve"? More than before I get presented with solutions rather than problems. AI agents have made "contributing" so easy, people often don't take the time to write a ticket first.
Funnily enough, since I have a fine-tuned agent. When a ticket has decent maturity, I will often simply assign it to copilot. However, in those cases I have a direct interaction with an agent.
Q to my fellow #Django maintainers:
How do you deal with AI contributions? I believe I can fairly easily detect slop. However, it's usually dangerously close to code from an inexperienced engineer. How do I make sure not to insinuate and crush young engineers? I want to maintain the wonderful growth culture of the Django community while being mindful about my own capacity.
Replying to
@geerlingguy@mastodon.social
@geerlingguy@mastodon.social and here I thought, you own the tokens you create... Guess only when it suites the narrative
Replying to
@amirreza8002@mastodon.social
@amirreza8002@mastodon.social it became much simpler in the new version. If you're missing something, don't hesitate to share your ideas 😊
Replying to
@codingjoe@fosstodon.org
Btw, I am open for work if someone needs a crafty human #opensource engineer / #ai operator
Replying to
@codingjoe@fosstodon.org
That was a month long grind. But with that out of the way, I can go back to develop #theBox (Signature Edition) 😂
https://github.com/codingjoe/the-box
#Django HealthCheck version 4.0 is out! 🎉 🥳
The list of new checks is huge, but let me know if we missed anything. Thanks to everyone who contributed and tried the release candidates!