#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.
You start off your day fresh. You have a clear goal on what you want to do.
You start doing stuff. But you encounter a nasty bug that prevents you from validating what you're doing, so you must resolve this bug first.
The nature of the bug forces you to resort to jumping from commit to commit trying to find the issue.
Your email starts shouting. Somebody had the idea to ask people share their calendars which has the side effect of sending email about it to everyone.
You have a meeting.
You have a second meeting.
After these you find the commit that breaks everything. You look at it in GitHub and it seems like a harmless one line change by Dependabot.
In reality it is a merge commit that contains a full version's worth of changes to hundreds of files.
You go for lunch.
You return back and are a bit tired, because food. You start trying to pinpoint the issue using bisect.
You have another 1½ hour meeting.
You are dead from all the meetings, the mail constantly throwing more stuff about the calendar, and the fact you now end up with mysterious blank white pages in every bisect commit you try, not helping to figure out the original commit causing the bug you try to locate.
Oh, sorry, this was my day today. Lines of code written: 0. Bugs solved: 0. Goals achieved: none.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You start off your day fresh. You have a clear goal on what you want to do.
You start doing stuff. But you encounter a nasty bug that prevents you from validating what you're doing, so you must resolve this bug first.
The nature of the bug forces you to resort to jumping from commit to commit trying to find the issue.
Your email starts shouting. Somebody had the idea to ask people share their calendars which has the side effect of sending email about it to everyone.
You have a meeting.
You have a second meeting.
After these you find the commit that breaks everything. You look at it in GitHub and it seems like a harmless one line change by Dependabot.
In reality it is a merge commit that contains a full version's worth of changes to hundreds of files.
You go for lunch.
You return back and are a bit tired, because food. You start trying to pinpoint the issue using bisect.
You have another 1½ hour meeting.
You are dead from all the meetings, the mail constantly throwing more stuff about the calendar, and the fact you now end up with mysterious blank white pages in every bisect commit you try, not helping to figure out the original commit causing the bug you try to locate.
Oh, sorry, this was my day today. Lines of code written: 0. Bugs solved: 0. Goals achieved: none.