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?
pamela
in reply to silverwizard • • •like this
Hypolite Petovan and silverwizard like this.
Hypolite Petovan
in reply to pamela • • •silverwizard likes this.
pamela
in reply to Hypolite Petovan • • •like this
silverwizard and Hypolite Petovan like this.
silverwizard
in reply to Hypolite Petovan • •@Hypolite Petovan @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.
Hypolite Petovan
in reply to silverwizard • • •silverwizard
in reply to Hypolite Petovan • •Hypolite Petovan
in reply to silverwizard • • •silverwizard
in reply to Hypolite Petovan • •pamela
in reply to silverwizard • • •like this
silverwizard and Hypolite Petovan like this.
silverwizard
in reply to pamela • •Hypolite Petovan likes this.
Hypolite Petovan
in reply to silverwizard • • •@silverwizard A good abstract is like good slides, they give the direction of the talk but not the details.
You aren’t trying to get clicks so you should state bluntly the context of the talk and its conclusion, this lets people gage if they are interested in the “in-between” part.
silverwizard likes this.