The Power of Introverts: A Manifesto for Quiet Brilliance. Do you enjoy having time to yourself, but always feel a little guilty about it?
Then Susan Cain’s “Quiet : The Power of Introverts” is for you. It’s part book, part manifesto. We live in a nation that values its extroverts – the outgoing, the lovers of crowds – but not the quiet types who change the world. She recently answered questions from Mind Matters editor Gareth Cook. Cook: This may be a stupid question, but how do you define an introvert? Cain: Not a stupid question at all! It’s also important to understand that introversion is different from shyness.
Cook: You argue that our culture has an extroversion bias. Cain: In our society, the ideal self is bold, gregarious, and comfortable in the spotlight. In my book, I travel the country – from a Tony Robbins seminar to Harvard Business School to Rick Warren’s powerful Saddleback Church – shining a light on the bias against introversion. Cook: How does this cultural inclination affect introverts? Cain: Yes.
Getting Things Done® GTD Podcasts. Our GTD podcasts are here to support you at every stage of your GTD practice.
You will hear interviews with people from all walks of life about their journey with GTD, from beginners to those who have been at it for years. The podcasts include personal and professional stories, as well as practical tips about GTD systems for desktop and mobile, using apps and paper. Start listening now and you'll be well on your way to stress-free productivity. You can subscribe or listen to our free podcast stream through iTunes, Stitcher, Libsyn, Spotify, Google Play Music, or Soundcloud. Or click on the podcast title below to listen now through our website. iTunes Stitcher Libsyn Google Play Music Spotify Soundcloud Listen now Episode #22 – GTD and Balancing Family Life September 28, 2016 How do you balance a daunting project list representing multiple roles and outcomes? Episode #21 – Optimizing Your GTD System. Less stress, more productivity: why working fewer hours is better for you and your employer · Code Without Rules.
Update: This post got to #1 on Hacker News and the /r/programming subreddit, and had over 40,000 views.
Given that level of interest in the subject I've decided to write The Programmer's Guide to a Sane Workweek. There's always too much work to be done on software projects, too many features to implement, too many bugs to fix. Some days you're just not going through the backlog fast enough, you're not producing enough code, and it's taking too long to fix a seemingly-impossible bug. And to make things worse you're wasting time in pointless meetings instead of getting work done. Once it gets bad enough you can find yourself always scrambling, working overtime just to keep up. The real solution is not working even harder or even longer, but rather the complete opposite: working fewer hours.
Some caveats first: The more experienced you are the better this will work. Fewer hours, more productivity Why does working longer hours not improve the situation? 1. 2. 3. Skills Maps - Redgate Software. At Redgate, career development doesn’t mean rising through a hierarchy of job titles.
Instead, we encourage people to be T-shaped (or even more!) , that is, to take on a broad range of skills alongside expertise in a particular role. The skills maps are our way of communicating the breadth of skills and specialisms available, and highlighting those we find valuable. The skills maps have some common themes. Each role has a set of core skills, shown in the inner circle, which collectively represent the fundamentals of that role.
Leadership: Providing direction, and growing peopleProject: Interest in team processes, methodologies and evangelising best practiceSpecialist: Deep knowledge in one or more particular areasProduct: Domain expertise, user research and commercial nous Our skills maps are freely available to download in pdf format, simply click on the desired map below: Test Engineer Software Engineer Project Manager Technical Author UX researcher Interaction Designer Visual Designer. Advice for building a career in open source. Back in 1998 when I discovered Linux and open source, I never would have believed that I would make a career out of this.
Back in those days I didn't have a clue about what I wanted to do, but I knew I wanted it to involve technology in some way. Since those dim distant days filled with teenage inexperience and ... well, hair ... I have learned so many things about what works and what doesn't in building a career in open source. So here are some broader principles I have learned that may be handy for those of you starting out on your journey. Irrespective of whether you want to be a programmer, community leader, documentation writer, entrepreneur, or something else, I think these principles will help in setting you up for success and differentiating you from the pack. You don't have to have all the answers The open source industry is filled with smart, accomplished people.
They key is not sitting down with a whiteboard and charting an elaborate path forward for your open source career.