Full-time web dev; JS lover since 2002; CSS fanatic. #CSSIsAwesome
I try to stay up with new web platform features. Web feature you don't understand? Tell me! I'll write an article!
He/him
When I'm working on an interesting, complex problem, but making progress at a steady pace.
It's a balance that's easy to upset in either direction: if the problem is too simple, especially if it's a lot of repetitive, rote work, sure you'll make quick progress, but it can get boring; but if a problem is overly complex, like a caused by subtle, weird race conditions that are hard to reproduce, or if the library you're using has some unexpected behavior and you have to dig through someone else's poorly organized deep class hierarchy to find the bug (this is definitely a hypothetical and not my actual life right now 🙄), it can feel like trudging through deep mud, making frustratingly slow progress.
Both of these are normal parts of software development, but they aren't the parts I love the most. I'm happiest when I'm presented a really interesting, non-trivial challenge, especially one where I have to do some research and learn a new technique, but where I have at least an idea where to go and I consistently make some significant progress daily, check off a subtask each afternoon before I leave.
When I'm working on an interesting, complex problem, but making progress at a steady pace. It's a balance that's easy to upset in either direction: if the problem is too simple, especially if it's a lot of repetitive, rote work, sure you'll make quick progress, but it can get boring;
Wow, you really nailed this!
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.
When I'm working on an interesting, complex problem, but making progress at a steady pace.
It's a balance that's easy to upset in either direction: if the problem is too simple, especially if it's a lot of repetitive, rote work, sure you'll make quick progress, but it can get boring; but if a problem is overly complex, like a caused by subtle, weird race conditions that are hard to reproduce, or if the library you're using has some unexpected behavior and you have to dig through someone else's poorly organized deep class hierarchy to find the bug (this is definitely a hypothetical and not my actual life right now 🙄), it can feel like trudging through deep mud, making frustratingly slow progress.
Both of these are normal parts of software development, but they aren't the parts I love the most. I'm happiest when I'm presented a really interesting, non-trivial challenge, especially one where I have to do some research and learn a new technique, but where I have at least an idea where to go and I consistently make some significant progress daily, check off a subtask each afternoon before I leave.
Wow, you really nailed this!