It's STILL ONLY FRIDAY!
It's the weekend of hope.

I will.
-- Finish my tasks and reach my goals this weekend.
-- NOT be distracted by ANYTHING.
-- Check in with my progress here.
-- Make sure than I am on track.

Tasklist

1. Mcombinations
2. Equivalence coding
3. Ratio decision.
4. Extraction.
5. Function port.
6. Covariable recognition
7. Variable selection (D)
8. a) conventional
9. b) bootstrap
10. Variable selection (W)
11. a) conventional
12. b) bootstrap
13. Model evaluation (D)
14. Model evaluation (W)
15. Send to A/M/Z

---

1. SNP Scoring
2. Run through algorithm
3. Send to R

The latest pulseaudio debian repositories are at this:

I hope they fix the low-volume-through-front-speakers issue I have been having with the older versions...

NOTE: This was a bad decision. Stick to the repository version.

If you don't have much time to stand around stirring the onions and want to caramelize onions perfectly with the least amount of work...

3 minutes prep:
1. Peel and chop red onions lengthwise. Turn the chopping board and chop the lengthwise chopped onions into three.

2. Toss in olive oil, salt and spices

40 minutes cooking time (unattended).
3. Spread on a stainless-steel cookie sheet in an even uniform layer. Roast at 375 deg F for 40 minutes.

Perfectly caramelized onions ready to go into whatever you are cooking... or maybe even as a fun dinner with a little lime juice and chopped apples.

---
PS: The method doesn't work so well without
a) salt (because then, the onions become very dry and may burn/char instead of caramelizing).

b) stainless-steel cookie sheets. The non-stick varieties are just awfully non-uniform when it comes to heat conductance. I have always had partially charred results with those.

A while back, I wrote about how I was under-utilizing (e:strip). (e:tinypliny,54394). I am constantly making notes all over the internet and it becomes so crazy to keep track of everything. So I have decided never to log out of here and make all those notes here (except work) - which is still at citeulike.

I can't transfer all work here because then (e:strip) would also have to be my reference manager and store my million pdfs... Yeah, not very practical.

The thing is the search function of (e:strip) sometimes does not play well with my blogs. I don't know what to do about that. My one big request/feature-suggestion for (e:strip) would be to make search results somehow more accessible and context-sensitive along with the ability to use more search-modifiers... maybe.

And while we are on the subject of search, one more suggestion would be to turn up blog-numbers, or cite-able referral links along with the blog titles and excerpts in the search results. For example

Using (E:strip) To Its Potential...
06/01/11 @ 11:20 (e:tinypliny,54394)
excerpt with keyword visible here

Cross-referencing would become so much easier. Currently, I hover my mouse over every post to find out the number and then string it to the name of the (e:peep) who wrote it. Makes for a longer workflow.

(or how Google is everyone's mother(tm) (e:Paul), 2011)

I think (e:mrdeadlier) did this once but there is now a site for finding out what Google thinks of you.

Let's see: Who is tinypliny?

tinypliny is the network based installer
tinypliny is the minimalistic one that does not even
tinypliny is the
tinypliny is an unknown quantity at this point
tinypliny is offline
tinypliny is that a sweater with the shorts?

Who are you according to Google? Find out at this

---

PS: Who or what is Binky?