cdaven

> Reading rates were found to be fastest at 95 cpl.

They only tested 35, 55, 75, and 95 characters per line (cpl)! Which means that if they had tested 120 cpl, THAT could have been "fastest".

I actually built a micro break reminder in AutoHotkey yesterday; every 30 minutes a (top-most) message box shows up, telling me to move and look out a window. The message box auto-closes after 30 seconds.

Extremely simple! https://gist.github.com/cdaven/360f0509f823d309e1b9de67bd826...

I read _Go It Alone!_ in 2009, and was blown away. Try it? https://www.goodreads.com/book/show/19029346-go-it-alone

Ironically, we get a whole lot of free time when we invite the kids' friends over. They disappear somewhere and play for hours and hours.

Because SSL certificates are a hassle to use on the client side, and possibly cumbersome to generate. I used client certificates in a few projects, and while the idea sounds perfect, it's hard to implement, and at least I don't understand it thoroughly.

A username and a password is so much simpler.

Yes, if you mean a token that identifies a session that is saved on the server somehow. But not a JWT, which is only saved on the client and verified on the server.

I just stumbled on a note from the abandoned project [History.js](https://github.com/browserstate/history.js/):

> Despite History.js being one of the most popular JavaScript libraries there is, and has been used by even multi-million-user companies in its time - the reality of economy and company practices seems to be that companies prefer to fork their own internal versions and fix locally with their own devs rather than fund open-source maintainers what they would pay their own devs to make things better for everyone, including themselves, which would be cheaper - but no, that would require too many tiers of company approval that don't understand the need.

> As such, if you are an open-source developer, I'd recommend just working on open-source projects that are paid for by your own consulting work or your own company (e.g. every successful open-source project). As otherwise, when they become popular, you better hope they are easily maintainable and testable, otherwise the cost of maintenance is higher than the free time of the maintainers.

Yes. Learning new languages and libraries is helpful to a point, but learning all new languages and libraries is a distraction.

What's the point of developing stuff in the first place? To make the world a better place, to learn things, to grow. Will that be accomplished so much better by switching from Perl to ASP to Ruby on Rails to Node.js to Go?

Look, there will always be a new tool|library|framework|language|paradigm that is cooler and better. If you pick the coolest language available today, you will be "so 2014" in a few years.

We need to be more pragmatic and use the tools that make our mission easier. Sometimes that mandates a complete rewrite in a new language|framework, but that is rare.

What the article calls "revolutionizing" is really not that big a deal. Maybe it makes things a bit easier, faster, prettier -- but it won't make or break your company.

No good reason, no. Feel free to start your local franchise, and let me know how it goes. :-)

Sure, but the site is in Swedish: http://rakna.net

I have a quite simple web site with some calculators for taxes and stuff, that I originally built in 2007. The Google AdSense and affiliate income has grown from about $1000 per year to almost $1000 per month.

It is "passive" in the sense that I respond to the occasional e-mail (once a month), update the data once a year, and add another calculator when I feel like it.

A few years back, I was in the same position with another (online casual gaming) website, that I sold for 2.5x the yearly revenue. Looking back, I should probably have kept that site as well.

Pro tip: quality content beats SEO in the long run. Be the tortoise.

I had no trouble either. Do hackers hate Adobe?

I once spent a couple of hours writing a bash script that edited my /etc/hosts file (e.g. resolve facebook.com to 127.0.0.1), and then ran that using crontab to allow some breaks during the day.

It was fun, but then I had to go back to work. ;-)

I had some merge problems with SVN too (like a 6 hour merge session twice a year), but that may be due to my limited SVN knowledge and poor branch setup.

As an aside, I changed jobs to another place using SVN, and when they started moving to Git I changed jobs again. Still using SVN! :-)

"Another" could imply that Darcs is new, but it's not. According to Wikipedia, the first release was in 2003.

We tried using Darcs at work in 2006, but the early exponential merge issues made it impossible to use. (One time, we let Darcs try to merge "some changes" over the weekend, but it never completed.) Unfortunately we chose Subversion instead.