About 1 hour after my day starts, but before any meetings have happened. If I log on, I really can't just get to being productive at all, but the period right after I really get started is when I can get most of my work done until there is a possible break, which kicks me out of it.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Passionate full stack web developer, course author for Educative, book author for Packt, he/him.
Find my work and get to know me on my Linktree: https://linktr.ee/thormeier
This. And in the middle of the night. Sometimes you just need to be up at 2am, listening to some amazing tunes, hacking the living hell out of that project. Funks up your sleep cycle, but yeah.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
If you get to 2am best bet is to just keep going and go to bed at 6pm the next day - if you work like a Uni student,
then you might as well sleep like a Uni student! 💪🤣
Define productive... Later in the day I would say it is easier for me to get in the deep focus, but the quality of my work gets less. So important to check my work the next morning. Great combo
HTML, CSS, Bootstrap, XML, ajax, react js, WordPress, Magento, Shopify, Photoshop, Camtasia, SEO & learning new skills every moment 👨🏼💻 | I believe in learning and sharing with others 🛴
Morning 9 AM - 11 AM and evening 5 PM - 6 PM. I've been monitoring my most productivity hours for the past three months as I'm building a new app that helps improve focus and productivity
#ActuallyAutistic web dev. Does front of the front-end. Loves perf and minimalism. Prefers HTML, CSS, Web Standards over JS, UX over DX. Hates div disease.
Do you want to have a comment that is way too long for a question so short? Here, have one.
You tell me "make this better" and then remove all limitations on hours and time of day on when to do it, with only expectation being that there will be delivery and that changes are communicated. No feature requests, just "better".
I'd likely be working during late afternoons, and occasionally at nights. I'd probably work less hours than I do now.
Most likely nothing immediately obvious happens. Code changes here and there. However over the long term:
Conversion and user happiness metrics improve
Team members complete their tasks quicker
Team spends less time on bugs
What has happened? Users are happy. Team is happy. There have only been some code changes!
Code is a language. People read it. You take the time to make it clear, remove things that don't make sense, consider what helps a developer get things done, and when there is less friction it is easier to understand each part of the underlying system the code reflects.
UI is a language. People experience it. You take the time to make it clear, remove things that don't make sense, consider what helps a user get things done, and when there is less friction it is easier to understand each part of the underlying system the UI reflects.
I also think productivity is a lie. It is a metric of accomplishing things. I rather replace it with a state of least friction, because that is what it really is. To be able to do things well you need time, well-being, and support. Accumulated skill and knowledge helps, but those are gained by the other three. If you are a curious person you will eventually become an expert in anything given enough time, well-being, and support.
Eventually "productivity" means that you don't do certain things, because you don't need to do them. Say, you can simply fix a problem immediately hitting the right thing. Or better yet, you create things so that some problems never arise. This is totally invisible "productivity". But you can't measure it, because it is something that never happens.
If you want an ultra productive team you want to have a lot of problems that never happen. Put other way, team has to make sure that they choose the right problems to have. Also, over time it makes sense there are people who work to make sure possible problems may not arise, even if this means they're not providing the short term feature accomplishment productivity.
TL:DR; I'm most productive when I change things indirectly resulting to people wasting less time cumulatively thus making everyone else "more productive".
If I manage to get a workout session in the morning I’ve realized that I can focus on problem solving a lot more than from a day just going straight to the computer coding and problem solving.
Waking up the whole body seems to help out since I’m fully awake.
When having a half asleep mind and body I can’t really focus and I can tell
Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
Oldest comments (47)
About 1 hour after my day starts, but before any meetings have happened. If I log on, I really can't just get to being productive at all, but the period right after I really get started is when I can get most of my work done until there is a possible break, which kicks me out of it.
Mornings and evenings, I really seem to suffer from “the afternoon slump” more and more. Maybe it is time I started to take an afternoon nap? 🤣
This. And in the middle of the night. Sometimes you just need to be up at 2am, listening to some amazing tunes, hacking the living hell out of that project. Funks up your sleep cycle, but yeah.
If you get to 2am best bet is to just keep going and go to bed at 6pm the next day - if you work like a Uni student,
then you might as well sleep like a Uni student! 💪🤣
Same!
I got migraines a few weeks ago so I sleep 1-2 hours earlier.
Define productive... Later in the day I would say it is easier for me to get in the deep focus, but the quality of my work gets less. So important to check my work the next morning. Great combo
Typically 9am - noon. Right after coffee and before the rest of the team on the west coast wakes up!
Early morning, after yoga asana my productivity level reach 100%
Morning 9 AM - 11 AM and evening 5 PM - 6 PM. I've been monitoring my most productivity hours for the past three months as I'm building a new app that helps improve focus and productivity
During the night when the kids are sleeping and the only noise that can disturb me is my fan when i click on "Build" 😂
Do you want to have a comment that is way too long for a question so short? Here, have one.
You tell me "make this better" and then remove all limitations on hours and time of day on when to do it, with only expectation being that there will be delivery and that changes are communicated. No feature requests, just "better".
I'd likely be working during late afternoons, and occasionally at nights. I'd probably work less hours than I do now.
Most likely nothing immediately obvious happens. Code changes here and there. However over the long term:
What has happened? Users are happy. Team is happy. There have only been some code changes!
Code is a language. People read it. You take the time to make it clear, remove things that don't make sense, consider what helps a developer get things done, and when there is less friction it is easier to understand each part of the underlying system the code reflects.
UI is a language. People experience it. You take the time to make it clear, remove things that don't make sense, consider what helps a user get things done, and when there is less friction it is easier to understand each part of the underlying system the UI reflects.
I also think productivity is a lie. It is a metric of accomplishing things. I rather replace it with a state of least friction, because that is what it really is. To be able to do things well you need time, well-being, and support. Accumulated skill and knowledge helps, but those are gained by the other three. If you are a curious person you will eventually become an expert in anything given enough time, well-being, and support.
Eventually "productivity" means that you don't do certain things, because you don't need to do them. Say, you can simply fix a problem immediately hitting the right thing. Or better yet, you create things so that some problems never arise. This is totally invisible "productivity". But you can't measure it, because it is something that never happens.
If you want an ultra productive team you want to have a lot of problems that never happen. Put other way, team has to make sure that they choose the right problems to have. Also, over time it makes sense there are people who work to make sure possible problems may not arise, even if this means they're not providing the short term feature accomplishment productivity.
TL:DR; I'm most productive when I change things indirectly resulting to people wasting less time cumulatively thus making everyone else "more productive".
If I manage to get a workout session in the morning I’ve realized that I can focus on problem solving a lot more than from a day just going straight to the computer coding and problem solving.
Waking up the whole body seems to help out since I’m fully awake.
When having a half asleep mind and body I can’t really focus and I can tell
Oh gosh, 6am-9am. My energy tanks after noon.
When I am not reading blogposts that don't add anything to my skillset or knowledge.
When I am in home 🏠
That is when I am alone and just by myself. Also the reason why most of us are hyper productive during morning and nights.
Evenings I'm better at problem solving - which I tend to do stuff that help in work stuff when motived, ie performance issues.
Either 6am or 3pm
Night, probably :)