NearlyFreeSpeech.Net is always my goto.
205 karma · joined May 22, 2010
also I'm paying my mum rent after I bought property wtf?
These results can only be interpreted in the context on normal brain structure and function, and thus would have direct implications for the illicit/neurocognitive use of MPH. Since the underlying anatomy and biochemistry of ADHD has not been definitively characterized, our findings may or may not be generalizable to the vast majority of humans who are properly diagnosed with ADHD and are prescribed methylphenidate. Nevertheless, this work supports studies [51], [57], [58], [59] that demonstrate that drugs shown to increase the levels of dopamine in the synaptic cleft can contribute to degenerative changes in the basal ganglia.
If I'm doing something collaboratively, I'll either use a DVCS or meet with people in person. Or hack something together via Google Docs. (OK, I'm starting to see how this could be useful).
That said, I use Draft on a daily basis and it's awesome.
In my own life the 'solution' I have found is to use FreeBSD; I get a stable, well-maintained core with a sharp distinction between core, userland and third-party (the ports system).
I have found the ports system to be a lightweight, agile alternative to GNU/Linux package managers:
When you install FreeBSD you are left with a kernel, standard UNIX command-line utilities and everything you need to hammer the system into a finely-honed tool.
Right now, I'm using it exclusively on my servers because I'm willing to accept the trade-offs of Ubuntu (beta 12.04 on my dev box, XUbuntu 11.10 on my netbook) on the desktop; a little instability and fully-automated updates is OK in exchange for not having to fiddle with graphics drivers, sound, Flash, etc.
Then, make tags the exception -- since they are likely being used for releases.
http://github.com/may/yabe (Scheme. Barely started.)
I am assuming that this is because Nginx is faster at basic HTTP serving than Varnish. However, I am further assuming that if you have dynamic content served from a cache will always be faster than from the webserver; even if your webserver is super-fast you still have to wait for the page to be generated by your CMS, webapp, etc.
I ask because I am working on some blog software (http://github.com/may/yabe) and one feature I'd like to incorporate is super-fast page loads -- implemented via cache.
As the site will be .. "half-dynamic" -- new posts are added every day or so -- I would like to re-generate the HTML on every request, but cache the results for a few hours. I was planning to rely on Varnish, Squid, etc. to keep the load off my webserver.
Thoughts?
What I'm doing right now is a 5-6 hours/day job for the bills and working on my projects the rest of the day. Balances out pretty well -- I get physically tired from work and get some social interaction/out of the house/out of my own head. And the rest of my time -- and all of my headspace -- is free to write and code.
But, to get back to you, it sounds to me like you really would rather be working on your projects.
Here's what I'd suggest -- you don't want to leave your boss in the lurch, and you still need some money -- so why not just talk to your boss about working reduced hours, say half-time, so you can help them and have more time for your startups?