this post was submitted on 22 Jan 2024
7 points (100.0% liked)
CSCareerQuestions
950 readers
1 users here now
A community to ask questions about the tech industry!
Rules/Guidelines
- Follow the programming.dev site rules
- Please only post questions here, not articles to avoid the discussion being about the article instead of the question
Related Communities
- !programming@programming.dev - a general programming community
- !no_stupid_questions@programming.dev - general question community
- !ask_experienced_devs@programming.dev - for questions targeted towards experienced developers
Credits
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
About 4 ~ 12 a day, though roughly about 50 ~ 60 hours a week.
A 4 hour day would be if I have some problem that I know has a good implementation, but I just can't figure out how to do it. Then it's better to just stop and do something unrelated.
Though then once the problem is solved and all the puzzle pieces fall together - and I can just work on implementing it, and refactoring it into a good solution - I can continue working on it without caring about the time.
But I don't have a lot of days where at the end of the day I'm like "Yess, I'm finally done working, now I can start doing something fun!" - The working itself is already fun, so that creates a different "Working vs Not Working/Having Fun" dynamic