Or how I learned to RTFM
It's actually fairly simple. In your SSH config file, you add this:
Host * ServerAliveInterval 240
* after the host can be whatever host you want it to apply to, and
* simply means to apply this to all hosts. So you could also apply it this way:
Host example.com ServerAliveInterval 240
Also, if you aren't sure where your SSH config . . .
Or how I learned to not repeat myself
So, we looked at JPEG image encoding, which is a very popular image codec. Especially since our image is going to be blurred heavily on the client, and thus band-limiting our image data, JPEG should compress this image quite efficiently for our purposes. Unfortunately, the standard JPEG header is hundreds of bytes in size. In fact, the JPEG . . .
Or how I learned to evaluate better
Given what I know of this person’s performance, and if it were my money, I would award this person the highest possible compensation increase and bonus.
Given what I know of this person’s performance, I would always want him or her on my team.
This person is at risk for low performance.
This person is ready for promotion today.
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 . . .