[ad_1] At this point in my career, I’ve been working remotely more than I have ever been in an office. I don’t ever want to have to return into an office unless it’s absolutely necessary. Part of working like this, though, is maintaining a sense of self-discipline for the backlog of tasks required for work and doing so in such a way that makes it easy for me to focus on what I’m working on, what’s next, and what’s in the backlog. (If you’re a developer and you’re reading this, then you’re probably thinking kanban and you’re not wrong – but what I’m getting at is slightly different). Before getting too much into the rest of the article, I do want to share that the majority of work I do right now is captured in Asana and organized by quarter. We have very little email and very little thrashing between emails, DMs, and other behavior commonly associated with the hyperactive hive mind. [The] hyperactive hive mind as a workflow centered on ongoing conversation fueled by unstructured and unscheduled messages delivered through digital communication tools, like email and instant messenger. Ezra Klein Interviews Cal Newport But that doesn’t mean I don’t want to take a little further to not only help my day-to-day (especially during periods of increased business) but also to help give visibility to other people with whom I work so they know where a given task stands in my queue. And don’t think this is me elevating my day-to-day any more important than yours. On the contrary. I’m sharing this to help give insight on what I’ve found that works so it may help you, too. Don’t Use Elaborate Task Management Systems I’ve used a variety of productivity apps and tools over the years, like Things (it was the first app I ever bought for the very first iPad!) and Trello (long before Atlassian bought them from Glitch, fka Fog Creek). I’ve also given a fair shake at a number of apps with which we’ve been inundated with the last decade and a half. But I’ve found it’s often the simplest approaches that can be just as effective, if not more so. In particular, I’ve settled on two lightweight methods that I find most useful for keeping track of my tasks, projects, and various todos – a simple text file and a Google Doc. A Basic Text File The first method I use is maintaining a plain text file on my desktop that I can quickly open and jot down notes, thoughts, links, quotes, and anything else related to the work I need to get done. What it’s like to type into a basic text editor. I usually have it open in an area of the screen or one of my virtual desktops so I can quickly capture the idea and the move back into what I was doing. The goal here to is get the information somewhere I can remember it later but to avoid the expensive cognitive load of context switching. This low-friction system allows me to capture ideas the moment they come to me, without having to fuss with a complex task management app. Ultimately, think of it like a digital scratch pad – I’ll dump in links to or quotes from Slack messages, email excerpts, random musings, and anything else that I want to reference or follow up on later. Then, during the last block of time in my workday, I can review the file, triage the items, and transform them into actual tasks, projects, more detailed notes, and so on. The Kanban Google Doc (For Lack of a Better Term) The second approach I rely on is keeping a living Google Doc that serves as a kanban board of sorts for my work. I divide the document into three clear sections: “In Progress,” “Up Next,” and “Backlog.” Under each of these headers, I list out my various tasks, projects, and responsibilities, along with any relevant details, links, or context. This simple, visual layout gives me a birds-eye view of everything I’ve got going on. There’s a difference in a bird’s eye view and eye-view of birds. It helps me stay focused on what I’m actively working on while also keeping an eye on what’s coming up next. And crucially, if I need to share let others see what I have going on, I can simply send them the link to the Google Doc to provide that transparency. Sometimes, this affords them the opportunity to find someone else to help or it helps set reasonable expectations on when the requested work will be completed. When Simplicity Matters I find these two methods valuable because they are so lightweight and low-friction. I don’t have to wrestle with complex task management software or try to shoehorn my workflow into a particular system. There are no software updates, system downtimes, or anything like that. In situations like this, I’m convinced simplicity wins almost every time. Instead, I can quickly jot things down, organize my thoughts, stay focused, and keep moving forward on whatever it is on which I’m currently working. We have too many notifications, alerts, red circles, and digital distractions that attempt to push themselves on to us. I’d rather silence all of those and then pull the work I need when I’m ready. Sometimes the simplest approaches are the most effective. By sticking to these two lightweight task tracking techniques, I’m able to maintain focus, reduce cognitive overhead, and ensure I’m making steady progress on the things that matter most. [ad_2] Source link
Continue readingTag Archives: Dont
Don’t Over-Architect Your Blog Posts
[ad_1] At some point, I lost the motivation to write about anything that would include too much code because of the amount of time it would take to: put a functioning solution together, architect it in such a way that’d fit with best practices (at least for OOP), explain the various features about OOP that the reader may not know, then explain the problem. This is too complex. I’m not saying that articles shouldn’t be written that explain the concepts of object-oriented programming or shouldn’t talk about certain rationale for why something was done. But I am saying that not every article on programming has to be written in a way that includes code that’s in a namespace with several other classes, has subscribers, services, and that uses dependency injection and includes a GitHub repository just to demonstrate a single concept or solution. Case in point. Maybe I’m writing this for my own benefit, but maybe there’s also something to be said for those of us who enjoy blogging about what it is that we’re doing and are growing more concerned with showing how to solve a problem with the bare set of code to make it happen all the while leaving the architecting – or judgment from other readers on our abilities – to our day-to-day responsibilities. To that end, don’t over architect your blog posts. Say what you need to say, demonstrate what you need in the code, and leave the rest for another post or another author. [ad_2] Source link
Continue readingYou Don’t Have To Want What Everyone Else Wants
[ad_1] I launched a WordPress-based business sometime around 2013. Starting a business is a goal for a lot of people, but it was never something I intentionally set out to do. I was in university at the time and blogging about books — just doing something I loved. But then I had an idea for a WordPress plugin that would make book bloggers’ lives easier. Although I did decide to sell it instead of releasing it for free, making a lot of money was never my goal. I thought maybe I’d make $500 overall if I was lucky. But three months in I’d already made nearly $1500 and those numbers would only continue to climb. By the time I graduated university, this little business of mine was already fully paying my bills. I went straight from graduation to running a full time business. Over the next few years, I sold pre-made plugins, built custom plugins, launched custom websites for authors and bloggers, dipped into the managed WordPress hosting space, and created WordPress e-courses. Objectively, business was great. But by 2016, I was waking up every morning and thinking, “What the hell am I doing?” The more my business grew, the more I was afraid it was about to crash and burn. The more I diversified, the less confident I felt about what I was doing. Above everything, I was tired. Turns out, I’m not a businesswoman I was tired of selling, of marketing, of advertising, of promoting. I was tired of asking myself “will this sell?” before I started a new project. I missed creating just for the sheer fun and joy of it, which was how my very first plugin even came to be. I just wanted to build cool things and quietly release them into the wild. I love to create but I don’t love to sell. Perhaps I could have hired people to help me with the aspects of my business I didn’t enjoy, but although business was going well for a one person show, I didn’t feel like it was going well enough to hire more people and confidently feel like I could pay their salary every month. And the thought of having that responsibility just brought me even more anxiety. I felt stuck and, honestly, ashamed of how I felt about my business. Was I being ungrateful? I had this incredible thing going for me — I was paying all my bills, working flexible hours (and from home!), and calling all the shots. This is what other people aspire to have, and I had it! I was embarrassed to admit that maybe I didn’t like it anymore. I didn’t want to be in charge. I didn’t want to have the entire success or failure of a business resting on my shoulders. I remember looking through job listings trying to imagine myself doing something else — anything else. But another problem I had was that running my own business straight out of school had spoiled me. I didn’t want to be in charge, but I also still wanted to work from home. I still wanted flexible hours. I didn’t want to sacrifice my 3pm gym session. I still wanted a certain degree of freedom in what I did each day. I wanted all the benefits of running my own business, without any of the downsides I had come to dread. A well timed opportunity In late 2016, sheer luck and good timing brought me to Sandhills Development. I was offered a job at a company that could amazingly check every box on my dream list. I could work from home, set my own hours, have a weird schedule, still make the gym at 3pm, and most importantly: my job would just be one thing. I could focus on building really cool stuff, and nothing else. I wouldn’t have to think about marketing or sales or profit. It’s been over four years since then and I’m now the lead developer for Easy Digital Downloads — the plugin I originally used to sell my first product. So I think things are going pretty well! My old business does still exist, but in a very low key way. I still work on and maintain the products out of love and passion for them, but with zero pressure to actually make sales or be successful. The biggest difference is the boundaries I’ve been able to create in my life. When running my own business, I didn’t work all day long, but I did tend to think about work all the time. Growth was always on my mind because making that happen was purely up to me. I was putting so much pressure on myself to do well, that I couldn’t stop thinking about it. But now, work goes away as soon as I decide I’m done for the day. I don’t think about it after hours. There’s comfort in the fact that although I care about the company, it’s not my company, and the success — or failure — of the company isn’t purely up to me; if something does go wrong when I’m gone, there’s someone else capable of handling it. What works for someone else may not work for you Some people would consider it a downgrade to go from business owner to employee, but it was absolutely the right move for me. Running your own business is often glamorized, but not everyone is cut out to wear all the hats that a one-person business requires, and not everyone has the drive to grow a business into something larger. And that’s okay. At the time, it was immensely hard for me to admit that out loud because I thought it would make me a failure. There is no “one size fits all” dream job and I learned that being the owner of a company is not mine. If what you’re doing now isn’t working then there’s absolutely no shame in bowing out, even if you’re currently living
Continue reading