Or how I learned to love Keynote
Before I started using this method, I always struggled with ways to highlight parts of code I wanted to talk about when giving presentations. This method, I've found, is at once the easiest method to employ, and provides context to the viewer. They can easily follow along, and where the code is in relation to other code you are talking . . .
Or how I turned tweets in a blog post.
- Practice your talk before speaking. Several times. Record yourself. Watch it. At a conference, people paid $$$ for this.
- Assume wifi is unavailable for your talk. Don't depend on it to run demos.
- Assume you'll get few or no questions. Given a 45 minute slot? Aim for 40 minutes.
- If you insist on live coding, make sure you've written . . .
Or what we don't keep track of
Simply put: we don't sell your data, we don't mine your data, we don't look at your data and we don't share your data.
We do not share your data with any third party. The only third party involved with storing your data is Parse, who we use as our backend hosting provider.
We do not . . .
Or one way I learned to find them
All too often on Hacker News, I come across a comment like this:
wouldn't most of them be able to build something like this for internal use in a single day
Yes. Of course, it might only take a day to build, but it will be maintained forever. And that means dealing with potential bugs. That means testing. That means deploying. It means . . .
Or my presentation from MidwestPHP 14 on PHP and RabbitMQ
You've optimized your database queries, you're using memcache and APC, and you've even upgraded your servers. But now your processes are taking too long to run. A script running in cron every minute just isn't going to cut it. Where do you turn next? This talk introduces you to RabbitMQ specifically, and queues in general. . . .
Or how to do something in an agile fashion
What to do:
- Find out where you are
- Take a small step towards your goal
- Adjust your understanding based on what you learned
How to do it:
When faced with two of more alternatives that deliver roughly the same value, take the path that makes future change easier.
From Agile Is Dead (Long Live Agile) by Dave Thomas.
Or how I do support
So, you purchased TwoDo from the AppStore and you need support? Support right now is a fairly simple affair. Just email me at firstname.lastname@example.org! That's pretty much it. Be sure to include "TwoDo Support" in subject line. I'm sure if I get a lot of support requests, I'll just actually fix the problems. And if I get a lot . . .