Open caichinger opened 4 months ago
@swkWien/organisers see above for this year's Zero Overhead Code Retreat schedule. Hoping to see many of you in course of the coming gatherings!
Thank you for joining! :clap:
You find today's state in above commit.
I would like that next time we think of our template to remind us of our rules of engagement, check-in etc. I will try to do that.
I am not entirely happy with our "let's try interactive programming session", maybe I offer one in the future where I take a more active role in guiding you through the process (!= navigator role), in case you want to join. I am interesting in better understanding the relationships between IP and TDD and how the can complement each other.
Here the links to the two publications I mentioned:
Regarding Brainf*k language that you rejected. It is not nice to code it for sure but it was not created to be like that. It seems to have been created to allow the smallest compiler possible: "Compilers für den Amiga in lediglich 240 Byte zu schreiben. Brian Raiter konnte dies unterbieten, indem er – unter Verwendung von nur 171 Bytes – einen Brainfuck-Compiler für x86 Linux schrieb. Für MS-DOS gibt es einen Brainfuck-Interpreter von Bertram Felgenhauer mit einer Größe von nur 98 Bytes" So I guess the exercise would be to create the compiler not code in the language ;-) Also it seems to be proven Turing complete.
thank you for posting the links.
Citing The Curse of Recursion: Training on Generated Data Makes Models Forget (Model collapse)
very interresting. makes me think how this effect not only applies on llms but humans as well, like confirmation bias :)
Regarding Brainf*k language that you rejected. It is not nice to code it for sure but it was not created to be like that. It seems to have been created to allow the smallest compiler possible: "Compilers für den Amiga in lediglich 240 Byte zu schreiben. Brian Raiter konnte dies unterbieten, indem er – unter Verwendung von nur 171 Bytes – einen Brainfuck-Compiler für x86 Linux schrieb. Für MS-DOS gibt es einen Brainfuck-Interpreter von Bertram Felgenhauer mit einer Größe von nur 98 Bytes" So I guess the exercise would be to create the compiler not code in the language ;-) Also it seems to be proven Turing complete.
Interesting, I did not know that. From the perspective of being a very limited language
Brainfuck requires one to break commands into microscopic steps.
could be interesting to try but I am still vary about the syntax. There is a VS Code extension for Brainfuck though.
thank you for posting the links.
Citing The Curse of Recursion: Training on Generated Data Makes Models Forget (Model collapse)
very interresting. makes me think how this effect not only applies on llms but humans as well, like confirmation bias :)
You are welcome :) I too think that is pretty interesting.
FWIW
[...] this effect [...]
With regards to your comparison, I am not sure though. No being an expert in any of these matters... when we follow this definition of confirmation bias (that's a nice link as well btw):
Confirmation bias occurs when an individual looks for and uses the information to support their own ideas or beliefs. It also means that information not supporting their ideas or beliefs is disregarded.
I would say that an LLM has no beliefs (in particular they may hallucinate) and feeding it with LLM-created content does not imho introduce certain biases but instead feeds a degenerative process that is affecting overall model performance.
However, I too think that if we continuously succumb to our own biases then yes, our model of the world collapses. In that sense I agree with you. :)
thank you for posting the links.
Citing The Curse of Recursion: Training on Generated Data Makes Models Forget (Model collapse)
very interresting. makes me think how this effect not only applies on llms but humans as well, like confirmation bias :)
You are welcome :) I too think that is pretty interesting.
FWIW
[...] this effect [...]
With regards to your comparison, I am not sure though. No being an expert in any of these matters... when we follow this definition of confirmation bias (that's a nice link as well btw):
Confirmation bias occurs when an individual looks for and uses the information to support their own ideas or beliefs. It also means that information not supporting their ideas or beliefs is disregarded.
I would say that an LLM has no beliefs (in particular they may hallucinate) and feeding it with LLM-created content does not imho introduce certain biases but instead feeds a degenerative process that is affecting overall model performance.
However, I too think that if we continuously succumb to our own biases then yes, our model of the world collapses. In that sense I agree with you. :)
how would you define belief?
Hi all, as the Dojo on Saturday 18th is coming up - how and where should I send the reminder?
Hi all, as the Dojo on Saturday 18th is coming up - how and where should I send the reminder?
Thank you for hosting and reminding us! :)
For me it is up to you do the reminding part.
Options include:
[...] how would you define belief?
@gregorriegler let's continue this conversation elsewhere (e.g. at our next meeting).
Hey there, the events were created on Softwerkskammer and Meetup, but not on coderetreat.org and twitter for now. @caichinger @ReaSu @maosmurf @gregorriegler @goerge @codecop cu
Thank you @redseacomputing for announcing via swk (and meetup)! My first tweet is out: https://x.com/swkWien/status/1788980108826398868
EDIT: adding links
Thank you @gregorriegler and @redseacomputing for todays session about approvaltests
in Python using Inline Approvals Workflow.
We started via cyber-dojo, using the Python 3.12, approvaltests-12.0.0
setup, then quickly moved to local PyCharm (and Code With me feature for faster handoff).
One can find today's code at https://github.com/maosmurf/20240518_ant_approval_2
Today I joined the Python Approvals Mob and told them about our CodeRetreat. I explained our problem where we lost the previous results on a failing refactor, and proposed an option that would preserve the previous result. We briefly implemented it. Amazing! https://github.com/approvals/ApprovalTests.Python/releases/tag/v12.2.0
Who can organize a venue for the next session on Friday, 14.06.2024 09:00-14:00?
At WKO there is still one free room but I have few hours left.
WKO EPU 8 is booked on Code Mentor KG, Görge Albrecht on 2024-06-14 09:00-14:00
HTH
WKO EPU 8 is booked on Code Mentor KG, Görge Albrecht on 2024-06-14 09:00-14:00
Thank you for taking care of that.
As you might have noticed I created the event on softwerkskammer.org and sent out an invite (thanks @goerge for the venue!), however, unfortunately I won't be able to attend.
Looking forward to July! I would really like to give interactive programming another try.
As you might have noticed I created the event on softwerkskammer.org and sent out an invite (thanks @goerge for the venue!), however, unfortunately I won't be able to attend.
Thank you for taking care of that (even though you do not have time to join yourself).
Looking forward to July! I would really like to give interactive programming another try.
Happy to facilitate that in the future. :)
I created https://pads.c3w.at/code/#/2/code/edit/IQyRDjgpy-0a2Vj6+BhDKoWR/ in case you want to document something.
See you tomorrow :)
@caichinger So it seems it's only the two of us. Do you still want to make it happen? If not, it's fine for me. In that case, I will cancel the WKO reservation and hopefully get my time budget back.
No worries. At least one "external" participant will join. I"ll be there.
I"ll be there.
Thank you for the nice and productive session! (And not cancelling it:)
I documented and shared some of our observations. Feel free to make amendments.
Is anyone up for meeting in July, or are you all on holiday?
Is anyone up for meeting in July, or are you all on holiday?
I would be in. 12, 19, 20 and 21 would work better for me though.
12th and 19th would work for me, Saturday is not an option. I did not want to start the discussion about moving dates, but now that Claus has started it ;-)
12, 19, 20 and 21 would work better for me though.
Out of these, 19th is least convenient for me.
Shall we move it to Friday, 12th?
Please vote:
:tada: : yes, 12th works for me :eyes: : no, 12th doesn't work, but 13th would be fine :slightly_frowning_face: : neither date works for me
@ReaSu / @goerge are we going for 12th? I could book WKO venue?
@codecop Thank you for booking the venue!
I have created this, in case someone wants to add a topic already: https://pads.c3w.at/code/#/2/code/edit/8vXivcYHWzWLZDqwcf3J1UrW/
Will send out an invite/reminder later today.
EPU Venue for 12th (this Friday) has been booked. It is "EPU 9", ask for meeting with Peter Kofler. It is available 9-14 as usual on Friday, for max 6 people. Unfortunately without windows.
Thank you!
without windows
looking at the weather forecast, I hope there will be air conditioning! :-)
I hope I can join. Cannot promise though.
I hope there is enough space available. I'll join, too cu tomorrow
Code from our first sessions: https://github.com/gregorriegler/coderetreat_2024_07_12_async
Code from our final session: https://github.com/gregorriegler/coderetreat-2024-07-12-incremental
Thank you all for contributing to this collaborative effort! :)
Flip with notes is in the folder https://github.com/swkWien/sessions/tree/main/2024/cr20240712
About
Locations
Appointments
You want to take part and the event is not yet being taken care of? Go ahead and lead the way!
Dates:
Rules: