Beyond the basics such as an enforced code of conduct and covered travel and lodging, there are a few things that I really appreciate as a speaker:
Speaker dinner / lunch / hangout time. Getting a chance to talk to other speakers in a non-public situation is great for conquering my imposter syndrome. Even if they're super famous, we're still sharing food and I can get a chance to connect as peers.
Recommended lodging. I've already got to write a speech - do I really have to track down the best hotel too? Having the majority of the conf stay at the same venue can lead to powerful chance meetings between attendees.
Video of speech. This is such a great artifact for a speaker to have. This can be a powerful tool for finding the next speaking opportunity.
ColorHighlighter is a pretty nifty package for Sublime Text which can display the color of CSS colors values right in the text editor. Here are a few usage and configuration tips if you want to use it yourself.
There are two different settings for how to display the colors:
ha_style: The style at any time.
style: The style when that text has focus (line 7 in the image above).
Here's an example of the ColorHighlighter.sublime-settings file which results in the image above:
Let us take a little time to compare and contrast printed products with their online counterparts - such as a printed newspaper and the same newspaper's website.
The printed version is tangible and tactile. Once printed, it can't be revised by the creator, though the user can make notes on the paper. Since it's a tangle product, the user must find a way to dispose of the used product; which may be repurposed as combustion or packing material. Each newspaper will probably only be used by one or two users.
The online version is interactive: searchable and sharable. It is easily updated. The website is much more likely to be seen by users outside of the physical area of the newspaper. Many users will use the same "version" of the paper, which can generate comments and discussions.
These are completely different products, even though they share the same content.
Creaming is one of those weird terms you see in baking recipes. It does have a specific meaning though, and doing it correctly can really improve your baked goods.
Creaming means mixing the butter (or the main fat of the recipe) and sugar (white or brown) until "light and fluffy". This process puts a bunch of tiny bubbles into the proto-cookies, which help with leavening. You should see the volume of the mixture increase by about a third, and has lightened in color, due to all that air. You shouldn't be able to see any sugar granules, but you should be able to feel them if you rub the creamed mixture between thumb and forefinger. Creaming will take somewhere around 3 minutes with a mixer (I like to use a paddle with a scraper or edge beater in my stand mixer), and just about forever if you're mixing by hand.
Not to be a downer, but that "free" trip you got by having your conference talk accepted is pretty far from free. TANSTAAFL, and all that. Here some additional "costs" you may have to consider. (Organizers: think about the huge commitment your speakers are making when they agree to speak. Try to make things as easy for them as possible.)
Time off. Some companies are happy to consider conference-attending as work days. But if your company isn't, or if you're self-employed or a student, or have already done a lot of speaking this year and your company can't really cover any more, then you'll be using your PTO or otherwise covering these days yourself.
Travel costs. Even if the conf offers reimbursement for travel costs, most do so within a few days of the actual conference. If that's the case, you're going to have to float the money until the paperwork and funding goes through. And unfortunately it's not uncommon to have to "remind" the organizers to process the reimbursements. This can be reduced by having the conf book (and pay up front) for as much as possible, but not all confs offer this and this isn't an option if you're traveling with a SO and want to sit together on the plane.
Travel hassles. Travel can suck, particularly if you're going via airplane. Your odds of encountering that suck increase with every layover and international border.
Eating. If you're traveling, you'll probably be eating out. There is almost never a per-diem covered by community conferences, so be sure you've budgeted for your food. Also consider any tourism costs if you'll be combining the conf with a few actual vacation days.
Talk preparation time. How much do you value your time? Somewhere between minimum wage and your hourly rate? If you have a talk accepted, your new hobby is preparing that talk. Writing and researching and coding demos and practicing in front of people. Some magicians can write a 25 minute talk in 3 days. I sure can't. My talk preparation is like water in a pothole - it expands to fill all available time and space.
Partner time. If have a partner traveling with you, odds are they won't attend the conference with you. But you'll probably plan to spend time with them; perhaps dinner each day and a few days touring after the conference. Be sure to work this all out ahead of time so that all expectations are met.
Have you been thinking about contributing to open source projects, but didn't know where to start? Here are a few ways to get started. find projects which are actively welcoming new contributors by highlighting their "starter" issues - bugs which are small in scope or otherwise make a good introduction to the project.
Outreachy: In addition to year round code mentorship for under-represented folks in tech, Outreachy provides paid internship matchmaking - the deadline to apply is October 17th!