# burnout Published articles for burnout. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why focused coding time may be limited to a few hours per day DevFeed: [Why focused coding time may be limited to a few hours per day]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-01-29T16:02:51Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [coding](), [meetings](), [Computer science]() Tags: [burnout](), [coding](), [context](), [cycle-time](), [developer](), [meetings](), [strategies](), [techniques]() ### AI overview This commentary argues that developers may have only three to four hours of high-focus coding capacity per day. It discusses cognitive limits, interruptions, meetings, flow, and deep-work strategies, while recommending practices such as time-blocking, batching communication, async defaults, and no-meeting days. ### Source excerpt Most of us have felt it: after a few solid hours of coding, your brain starts shutting down. ## Year in Review: 2024 DevFeed: [Year in Review: 2024]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2025-03-27T00:00:00Z Content type: article Language: en Sources: [Tania Rascia]() Topics: [coding](), [CSS](), [React](), [Web Development](), [Web platform]() Tags: [bluesky](), [burnout](), [career](), [coding](), [css](), [hooks](), [keyboard](), [meta](), [pagination](), [projects](), [react](), [redesign](), [review](), [side-projects](), [sorting](), [table](), [variables](), [year-in-review]() ### AI overview A 2024 year-in-review from a principal engineer who continues to work primarily with React and CSS. The author reflects on balancing a full-time engineering role with coding, writing, side projects, and maintaining a personal website, while highlighting several articles and a blog redesign completed during the year. ### Source excerpt I'm trying to win the award for "Latest Year in Review". 🏆 I don't know if anyone can challenge me at this point, as it's almost thirdway... ## The Benefits and Costs of Building a Personal Brand DevFeed: [The Benefits and Costs of Building a Personal Brand]() Original publisher: [Read original article]() Author: Raphaël Hoogvliets Published: 2025-01-15T11:50:14Z Content type: opinion Language: en Sources: [Raphaël Hoogvliets]() Topics: [Website](), [Code](), [genai]() Tags: [blog](), [burnout](), [career](), [code](), [linkedin](), [mental-health](), [networking](), [personal](), [social-media]() ### AI overview The article argues that building a personal brand can help tech professionals with networking, learning, confidence, and career opportunities, but it also requires substantial time, may have an uncertain return, and can harm mental health through social-media use. The author concludes that it is valuable for some people but not suitable or necessary for everyone. ### Source excerpt Maybe you shouldn't be building a personal brand ## Value-Stream-Oriented Kanban DevFeed: [Value-Stream-Oriented Kanban]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-04-20T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Kanban](), [Agile](), [Software as a service]() Tags: [agile](), [burnout](), [business-developer-productivity-engineering-leadership-kanban-product-management-engineering-ex](), [business-value](), [cpu](), [cycle-time](), [flow](), [kanban](), [metrics](), [parallel](), [saas]() ### AI overview The article argues that Kanban should be oriented around customer-focused value streams rather than individual subtasks. It contends that measuring task-level flow can create an illusion of productivity while multiple initiatives delay meaningful delivery, and recommends prioritizing fast business value over maximizing utilization. ### Source excerpt Value-Stream-Oriented Kanban Many teams, especially in the startup environment, move away from Scrum and use a leaner Kanban-based approach. This is a good thing. I don't think Scrum is a suitable framework for modern, fast, agile companies. - Especially not in the SaaS field (the reasoning behind this statement will become another article, eventually). ## Year in Review: 2023 DevFeed: [Year in Review: 2023]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2024-01-20T00:00:00Z Content type: opinion Language: en Sources: [Tania Rascia]() Topics: [coding](), [Web](), [React](), [Redux](), [GraphQL]() Tags: [burnout](), [career](), [coding](), [graphql](), [life](), [review](), [websockets](), [year-in-review]() ### AI overview A personal review of 2023 and the author's ten years as a developer, covering career history, burnout from writing for DigitalOcean, recent software-related posts, and plans to write more about personal interests. ### Source excerpt It's 2024, y'all. We're 20 days into the year, so I'm running out of time to write that end of year post I always do. I haven't quite known... ## On the Edge of Burnout... Again DevFeed: [On the Edge of Burnout... Again]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:32.669000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [inclusive design](), [Job]() Tags: [accessibility](), [burnout](), [inclusive-design](), [work]() ### AI overview A personal account of recovering from burnout while working as the first accessibility specialist at Oura. The author describes how role miscommunication, unclear expectations, and a brain injury contributed to burnout, and how conversations, time off, and a clearer understanding of the role helped restore their energy and motivation. ### Source excerpt I've been super tired during the spring. Again. I could write a blog post about how disappointed I am that I've let myself into this situation - again. But this blog post is not about it. It's about how I got further away from that edge and started finding myself - and the spark - again. So, to give some context: About eight months ago, I wrote a blog post about my first month as an accessibility specialist at Oura. At that point, I was still in the honeymoon phase, and the realities of being the first-ever accessibility specialist in the company weren't apparent. You see, being the first in any role, especially in a role whose goal is purely to change existing things, is not easy. If there are any miscommunications about the position, it makes it even harder. And if you don't know what's expected of you, well, that's certainly a risk for burnout. I should have known better - hey, I've been here before, and I know I'm more at risk because of my brain injury than someone else without the same history. I realized I'd lost my spark. Not just for the work but also for anything outside the job. I used to love sharing what I've learned, but writing and submitting proposals for conferences didn't feel good. I thought, "What's the point? Nothing's going to change anyway". Now that I'm in a better position, I'm a bit sad because I missed some conference applying deadlines I had been waiting for for a long time. For example, I didn't submit a proposal to Inclusive Design 24 - I just didn't have the energy. I'm better now I'm better now. But it took some time, conversations, and challenging moments before I could be honest about the situation. And again, I could use the word "again." I've been here before. I tried to raise the problems throughout the spring. I think it was a short sickness leave that made the people at the company understand that this is pretty serious. After that, we had multiple conversations about my role. I understood some miscommunications about my positi ## Year in Review: 2021 DevFeed: [Year in Review: 2021]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2022-01-01T00:00:00Z Content type: opinion Language: en Sources: [Tania Rascia]() Topics: [coding](), [Code](), [Job](), [Jackson](), [Netflix](), [sessions]() Tags: [burnout](), [coding](), [developer](), [jackson](), [life](), [netflix](), [year-in-review]() ### AI overview A personal review of 2021 reflecting on time spent away from home, maintaining balance among development work, side projects, and creative pursuits, and recovering from past burnout. The author also discusses cultural discoveries including Bo Burnham's Inside and The Beatles: Get Back documentary. ### Source excerpt Wow, here we are, the sixth installment in the New Year series of posts. This year feels almost like a lost weekend. Aside from a few small... ## Adopting Continuous Delivery: More a culture change than automation of processes DevFeed: [Adopting Continuous Delivery: More a culture change than automation of processes]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-12-04T12:07:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Continuous Delivery (CD)](), [Automation](), [Software]() Tags: [automation](), [burnout](), [continuous-delivery](), [continuous-deployment-software-development-developer-productivity-engineering-excellence-organiz](), [faster](), [ownership]() ### AI overview The article argues that adopting continuous delivery requires a culture and process change, not merely automating manual deployment activities. It recommends understanding existing delivery processes, responsibilities, risks, and safety mechanisms before simplifying or automating them. ### Source excerpt Adopting Continuous Delivery: More a culture change than automation of processes Continuous delivery, the process of automatically delivering changes of a system without human interaction, is one of the most beneficial practices that software teams can adopt. In Accelerate, the authors Nicole Forsgren, Jez Humble and Gene Kim, discovered a strong link between using continuous delivery and organisational performance: Teams that continuously deliver their changes have a stronger sense of ownership, get faster feedback and need to rework their code less. Furthermore, deployments are less stressful and the risk of burnout is reduced.