At work. Stress. How To Tell A Job From A Career. We work, we live: the two snuggle together tighter than the pixels you're viewing as you read this post--and that fact has opened up the Great Work/Life Balance Debate, with calls for integration, fit, and a feeling that the whole thing might be a big myth. Over at HBR, personality profiling expert Tomas Chamorro-Premuzic has another take: that we should have work-life "fusion," allowing for the workaholic hours he says bring success--with an argument that turns on one key claim: you need to have a career, not just a job.
Finding the right match "Work is just like a relationship," Chamorro-Premuzic writes. "Spending one week on a job you hate is as dreadful as spending a week with a person you don't like. " While it seems a touch unnecessary that work is like a relationship, as we most certainly do have a relationship with the work we do, his point (mostly) sticks: "When you find the right job, or the right person, no amount of time is enough.
" Knowing the (psychological) difference. Why young employees quit their jobs. Tuesday, September 18, 2012 The biggest reason young, talented workers leave for new jobs? They’re not learning enough, writes Diane Stafford of the Kansas City Star: “Hirers often complain that their young workers jump ship quickly. A study published this summer in the Harvard Business Review confirmed that young top performers—the workers that organizations would most like to stick around—are leaving in droves. Researchers found that high achievers, 30 years old on average with great school and work credentials, are leaving their employers after an average of 28 months. Furthermore, three-quarters of them admit to sending out resumes, contacting search firms and interviewing for jobs at least once a year during their first employment. Multiple studies find that today’s younger workers have absolutely no intention of sticking around if they don’t feel like they’re learning, growing and being valued in a job.
Work / life balance. Productivity. Freelancing. Why We (Still) Believe in Working Remotely ? Blog ? Stack Exchange. It’s 2013, almost three years after we first raised money and started growing beyond the first four employees. At the time, Jeff wrote a great blog post about working remotely, basically laying out our plan for how we were going to make it work. Now we’re a few years in and it’s time to update it with, well, what actually happened.
First, where are we now? Stack Exchange now employs 75 people, roughly evenly split between sales (and sales ops and marketing) and product (development, ops, design, community management). The product side is where our remote working happens: we have 16 full-time remote and 18 in-office developers, sysadmins, designers, and community managers. . #1: It lets you hire good people who can’t move. . #1a: You don’t lose people to silly things like their significant other going to medical school. . #2: When done right, it makes people extremely productive. . #3: It makes you focus on more than butts in chairs. . #1: Remote working isn’t for everyone. . #1: Google Hangouts. A (Short) Rant About Working Remotely. I get emails on a weekly basis from recruiters looking for developers. The first question I respond with is, "Are you open to remote workers?
", to which the answer, 99% of the time, is "No". The reasoning is inevitably something along the lines of "They're an early stage/small company, so they want to have everyone in the office", as if being a young or small start-up necessarily means that you have to have everyone together, as if there's no possible way to build a company otherwise. I get the reasons why face time is important. This is why even companies that are advocates of remote work, like GitHub and 37signals, have company-wide meetups at least once a year. Even an arrangement where a dev can come in once a week, or when needed during crunch time for a project or a special planning meeting, seems reasonable. But I don't see a reason why, in 2013, given the tools we have, a developer has to be on-site at a desk every day, as the normal operating procedure.
Traveling, Writing and Programming. In a nutshell, my year so far has consisted of: Traveling for 10 months around the world through 17 countries covering Africa, South East Asia, Australasia and North, Central and South America. The trip was centered around surfing and photographyPresenting in Hong Kong, Japan, the US and LondonWriting a book for O'Reilly as I went, titled JavaScript Web ApplicationsWriting another book on CoffeeScript, soon to be published by O'Reilly.Doing a ton of open source libraries, such as Spine, Spine.Mobile, GFX, and Juggernaut.Building a startup prototypePresenting at FOWAAnd finally, landing a job at Twitter So, let me start a year ago, in September 2010.
I had just left a startup I'd co-founded, and whilst the experience was useful, I was feeling bit burnt out from the incredibly long working hours involved. I was back in England and needed to make some decisions. Choices in life: Do a bachelors at Columbia in NYC Downside - v expensive, not much to learn practically, boring?
Culture.