Thinking about #BSDCan abstracts and falling into analysis paralysis, I've no idea what an abstract looks like for this con. How many words? Do you want the talk outline? The topic and that's it?
I dunno - AP is setting in - I want to give a good idea without accidentally writing the entire talk?
=> More informations about this toot | More toots from silverwizard@convenient.email
@silverwizard they can be short! People imagine them like a journal abstract but for our purposes it's probably better to think more about what would help you choose which room to join if you had them taped on the wall to read. Who's it for? What's the background story or prior work? What are the 3-4 biggest points you're trying to hit during your presentation, and what goal do you hope to achieve? Things like that. You don't need more that two paragraphs. Many proposals are fine with just one.
=> More informations about this toot | More toots from pamela@bsd.network
@pamela Maybe @silverwizard should just try to describe the talk here and then take it as an abstract! 😁
=> More informations about this toot | More toots from hypolite@friendica.mrpetovan.com
@hypolite @pamela Ok so the talk abstract is basically
My goal with computer is to be as stupidly boring as possible, let's talk about how BSD enables that, and what I am currently doing.
The problem is that... that... I don't know. Giving more context is way too much, but it's also not much there.
=> More informations about this toot | More toots from silverwizard@convenient.email
@silverwizard @hypolite pick some categories you'd focus on, maybe, and see what personal experiences match up? Often a talk given by an individual works nicely as a set of stories, but we don't always have those.
=> More informations about this toot | More toots from pamela@bsd.network
@pamela @hypolite I'll try to cobble something together than isn't sprawling
=> More informations about this toot | More toots from silverwizard@convenient.email
text/geminiThis content has been proxied by September (3851b).