The only regret after buying M! MBA is that year later Apple released MacBookPro version :( besides that - for my needs (web development, novel writing, running small business) it's fantastic.
In all approaches to therapy, regardless of the psychological flow behind them, it's the patient who heals himself (or herself). Therapist role is not exactly to be a blank screen, more like responsive socratic human mirror. It's up to experience, knowledge and gut feeling of the therapist to know when be quiet, when ask questions and what may have better chances to help given patient.
In general, inner monologue is fantastic tool for self-reflection. Yet, if one is struggling with living, it's a good approach to seek help of other human being, rather than relying solely on oneself.
I understand (to some degree) if someone is willing to enforce things you shouldn't say. Although right to free speech is/should be universal, but it doesn't mean free of consequences of what has been spoken. But I strongly oppose situation and any attempts to enforce what I should say. No. No pasarán. Ni wuja. Claiming power over what one should or ought to be saying is claiming power over what one should or is allowed to think. "1984" of Orwell's says hi.
Perl is not a bad language. Neither is PHP. I'm using both. And to be honest - it's all about collaboration. Writing something for myself? Perl. Writing anything which will involve anyone else? PHP.
1. Prepare agenda - write in points what topics are going to be at the meeting.
2. Set time frame - meeting longer than hour is counterproductive.
3. Invite proper people - include those who are actually needed (don't invite anyone "just in case").
4. Moderate!!! - have someone who will moderate meeting, will be in charge of presenting queued topics (asking questions and asking for answers) and will cut extending off-topics.
5. Write summary - sum up everything was said during meeting and send to everyone who was participating.
Progress not perfection. Which in this context should be read as willingness to getting know new solutions, new technologies and new applications; You delve into things, get some of the ideas, think about them, implement parts of them, fidget with them. BUT! Do not let them overwhelm You. It's virtually impossible for a person who isn't genius engineer to be fluent in all known technologies, languages, libraries and rest of the stuff. You focus on setting in your head memory anchors to different solutions, different approaches, and when the time is done You will end up with bigger knowledge and skill set. You don't need to remember all the details, You just need to remember where to find them.
Second thing - constantly improve communication. Be as humble as You possibly can, because people have their own struggles we are not aware of, and those affect the way they write and speak. That's why You need to remind your self everyday - "is this what I understood really the thing the person has said?". And ask for their understanding of given information. It's basically 70 to 80% work of good SE.
Finally, take care of your physical and mental health. You cannot be productive 24/7. Your body and mind need breaks and maintenance. Treat yourself in this aspect as any other high-grade, professional, top-quality tool. Your mind, your body are your tools - take care of them, so they can perform for life.
Oh! And be nice to yourself. Harsh treating You will most likely get from others. If You don't be kind to yourself, who will be?