mgmeyers

I've been reading a little bit of it every day. The quality of the writing is top notch, so I can actually ready it just for fun. I'm still on the first volume, and plan to be for a while. I definitely get lost on the mathier parts of it, but for the most part I can follow along, and I'd consider myself on the advanced side of intermediate.

I got rid of chronic pain I had for 4 years in 4 weeks by reading "The Divided Mind" by John Sarno. I'd highly recommend it.

And, as other's have pointed out, a wandering mind is part of meditation. The beneficial part of meditation comes from that act of noticing your wandering mind and bringing it back to focus.

Also, you can go through the UC Berkeley SICP course for free: http://www-inst.eecs.berkeley.edu/~cs61a/fa13/

I'm going through it now, on my own, and it's an awesome course.

My first gig was at a start-up. They could only afford to pay someone for ~10 hours a week, which fit perfectly with my school schedule. When I left school, they offered me more hours, but I was adamant about working no more than 25 hours, and by that time they had seen how productive I was at just 10 hours a week. There were definitely some rough spots when they had tight deadlines, but for the most part, they scheduled things so they worked with my schedule.

My current gig I got through a personal connection. They were in desperate need of a senior level front-end dev, and I was just upfront with them from the start that I would only be interested in working 25 hours a week. It helps that they have a team of devs to rely on when I'm not there.

My advice: if you want to be part-time, either be an expert in your field, or find an early stage startup that can't afford a full-timer. This sounds kind of shitty, but it's hard to convince people who are ingrained in the 40 hour work week. Also, telling people you're a student helps. I've found that people look down upon me when I tell them I have no desire to work 40 hours, but if I tell them I'm a student, they're all for it.

Sounds like you're senior to me. If you can quantify how you're the "go-to" guy, then you're in a position to ask for a raise.

To explain my stance vaguely, if you can make critical decisions about abstract concepts, then I'd consider you senior. For instance, I recently saw that some of my coworkers were using an HTML tag in a way that was technically correct, but in a situation where a different tag is more suitable based on the context of the page. This is something I've learned through my studies and experiences as a front-end dev, and as such, contributes in a small way to my "senior-ness".

This.

If I was working somewhere I was 100% passionate about, I would have no problem working 1/3 of my life. But, it's rare to find a position that completely matches one's values and professional desires.

I've worked 25 hours a week for the past ~6 years as a web developer, and I can't imagine a better work schedule. I've noticed that I'm just as productive on average, if not more so, than my 40-hour-per-week coworkers.

I do find it difficult to progress in my career, however. I've been trying desperately to transition into a full-stack, part-time position, but I feel pretty stuck as a senior level front-end dev. In my experience, this is because I need some weight to throw around when I request working only part-time.

Does any one know of any good self study resources (or online courses) on this subject?

From the article: "Barbano, who specializes in filtration methods for separation and recovery of protein, has his sights set on the tiny amount of protein in acid whey. He believes it might be usable as an infant formula ingredient. But first Barbano has to figure out how to extract the protein in a cost-effective way, and his research is just getting underway."

Agreed.

I was convinced it was going to end up being a commercial for some new car.

I like it. It will no doubt be refined as more people learn. It will be interesting to see how it holds up.

On a side note, I think a majority of the arguments I've read against it aren't very good ones. I see most of them boiling down to, "it's different, I don't want to have to learn a new language". This is what I said when I was learning standard music notation. I can see the issue of its anglo-centricness, but even that is a minor detail. One doesn't need to understand the words "above" or "below" to be able to associate the symbols with the notes.

I don't think a fair critique can come out of a quick glance at the hummingbird website. I'd be more interested to hear what people say after a few months of working with it.