OK. I did it, finally.
-
OK. I did it, finally. Travel is booked. If you're at #PyConUS2026 I will be seeing you there.
-
OK. I did it, finally. Travel is booked. If you're at #PyConUS2026 I will be seeing you there.
(and yes, I booked in the conference room block, as should you, if you're going)
-
(and yes, I booked in the conference room block, as should you, if you're going)
I gotta be honest, I'm a bit annoyed at the amount of AI nonsense going on at both the conference and within the community right now. It was more emotionally difficult to book this year than it has been in years prior. I am expecting more tense social interactions that require a far higher degree of self-regulation this time than I am used to at an event where I usually feel like I am Among My People.
-
I gotta be honest, I'm a bit annoyed at the amount of AI nonsense going on at both the conference and within the community right now. It was more emotionally difficult to book this year than it has been in years prior. I am expecting more tense social interactions that require a far higher degree of self-regulation this time than I am used to at an event where I usually feel like I am Among My People.
But, this *is* a community that is open to arguments about ethics and sustainability, which is rare enough in tech already, and I think it's important to be in the room to represent a constituency which has already peaced out to some degree, so I felt it would almost be an abdication of responsibility to not go for that reason.
-
But, this *is* a community that is open to arguments about ethics and sustainability, which is rare enough in tech already, and I think it's important to be in the room to represent a constituency which has already peaced out to some degree, so I felt it would almost be an abdication of responsibility to not go for that reason.
I gotta finish this curséd blog post first though. 3500 words and I'm almost done with the introduction. Starting to wonder if I'm actually just writing a book and I should be looking at a markdown -> epub pipeline instead
-
I gotta finish this curséd blog post first though. 3500 words and I'm almost done with the introduction. Starting to wonder if I'm actually just writing a book and I should be looking at a markdown -> epub pipeline instead
@glyph I can highly recommend Pandoc for doing lightweight Markdown → ePub. Doesn't do everything you might want out of a professional e-book, but it gets you pretty far.
-
I gotta be honest, I'm a bit annoyed at the amount of AI nonsense going on at both the conference and within the community right now. It was more emotionally difficult to book this year than it has been in years prior. I am expecting more tense social interactions that require a far higher degree of self-regulation this time than I am used to at an event where I usually feel like I am Among My People.
@glyph I'm not going this year (for various reasons) but I groaned at the announcement of the "AI" specific talk track.. Like FFS
-
@glyph I can highly recommend Pandoc for doing lightweight Markdown → ePub. Doesn't do everything you might want out of a professional e-book, but it gets you pretty far.
-
@glyph I can highly recommend Pandoc for doing lightweight Markdown → ePub. Doesn't do everything you might want out of a professional e-book, but it gets you pretty far.
@xgranade sigh. apparently pelican's frontmatter specification is some weird thing nobody else has adopted (rfc2822-style) so this is going to be annoying
-
@xgranade sigh. apparently pelican's frontmatter specification is some weird thing nobody else has adopted (rfc2822-style) so this is going to be annoying
@glyph Ah, yeah, frontmatter is annoyingly even less standardized than Markdown itself. I went down a rabbit hole the other day trying to even find specifications for what markers should be used for different kinds of front matter and just gave up.
-
@glyph Ah, yeah, frontmatter is annoyingly even less standardized than Markdown itself. I went down a rabbit hole the other day trying to even find specifications for what markers should be used for different kinds of front matter and just gave up.
@xgranade okay apparently it's not _totally_ custom, it's this one https://fletcher.github.io/MultiMarkdown-5/metadata.html but it looks like the general consensus is that "yaml frontmatter" won over "multimarkdown" so fml I guess
-
@xgranade okay apparently it's not _totally_ custom, it's this one https://fletcher.github.io/MultiMarkdown-5/metadata.html but it looks like the general consensus is that "yaml frontmatter" won over "multimarkdown" so fml I guess
@glyph The great thing about Markdown is that there's so many to choose from.
-
@glyph The great thing about Markdown is that there's so many to choose from.
@glyph (Yes, that's intentionally incorrect grammar for the sake of humor.)
-
@glyph (Yes, that's intentionally incorrect grammar for the sake of humor.)
@xgranade Markdowns General
-
I gotta finish this curséd blog post first though. 3500 words and I'm almost done with the introduction. Starting to wonder if I'm actually just writing a book and I should be looking at a markdown -> epub pipeline instead
@glyph non serious suggestion: do a Typst -> epub pipeline instead because that'll cause you to also write an additional short blog post about the process of producing epub from Typst as a side effect which means it's almost free! Aside from the huge time investment.
-
I gotta be honest, I'm a bit annoyed at the amount of AI nonsense going on at both the conference and within the community right now. It was more emotionally difficult to book this year than it has been in years prior. I am expecting more tense social interactions that require a far higher degree of self-regulation this time than I am used to at an event where I usually feel like I am Among My People.
@glyph Me, about PyCon AU's proposal review process this year: "We don't know the proportions, but we expect the audience to range from "all in" LLM enthusiasts to adamant "never LLMs" hardliners. Crafting a program that encourages everyone on that spectrum to *talk* to each other rather than yelling over or at each other is going to be a challenging task."
I can only assume the PyCon US program committee faced the same challenge.
-
I gotta be honest, I'm a bit annoyed at the amount of AI nonsense going on at both the conference and within the community right now. It was more emotionally difficult to book this year than it has been in years prior. I am expecting more tense social interactions that require a far higher degree of self-regulation this time than I am used to at an event where I usually feel like I am Among My People.
@glyph I was at a Blacksmithing event and had to discuss a surprising amount of AI. It was a spectator though.
-
@glyph Me, about PyCon AU's proposal review process this year: "We don't know the proportions, but we expect the audience to range from "all in" LLM enthusiasts to adamant "never LLMs" hardliners. Crafting a program that encourages everyone on that spectrum to *talk* to each other rather than yelling over or at each other is going to be a challenging task."
I can only assume the PyCon US program committee faced the same challenge.
@ancoghlan I'm wondering what "all in" folks are looking to get that they don't get from their vendor.
-
I gotta finish this curséd blog post first though. 3500 words and I'm almost done with the introduction. Starting to wonder if I'm actually just writing a book and I should be looking at a markdown -> epub pipeline instead
I am going to need some volutnteer copy-editors / advance readers for this monstrosity. if you're a booster this is going to be a hard read because it's relentlessly negative. but if you're a critic it's going to be a hard read because there's a lot of harm-reduction safety-tips language assuming that the reader doesn't agree with me and that they will continue to use AI (or at the very least are not able to escape mandates to use AI). so does anyone feel like doing some self-abuse next week
-
I am going to need some volutnteer copy-editors / advance readers for this monstrosity. if you're a booster this is going to be a hard read because it's relentlessly negative. but if you're a critic it's going to be a hard read because there's a lot of harm-reduction safety-tips language assuming that the reader doesn't agree with me and that they will continue to use AI (or at the very least are not able to escape mandates to use AI). so does anyone feel like doing some self-abuse next week
