I’m 40…been writing the codes professionally for about 20 years now, and come from the cowboy coding era before things were so specialized.
One of my actual strengths is to understand how design and coding fit together in a unique way, since I have a design background, and years of practical experience.
While I love the agile process to help identify tasks, it only goes so far as you break down the tasks.
If your technical manager just tends to leave big epics not broken down into their actual tasks, it can have a weird effect on tracking velocity and keeping on track.
But then there are tasks that take longer to write up, then just asking.
Right now we’re in the spot where we over-document, and I routinely get tasks that probably take 5 minutes to write up, where it’s seriously like changing a hex color in a sass include or something trivial…
Since I’m the oldest, and only remote employee, it’s kind of hard for me to really have a say in how that process is run, and it’s just easier for me to adapt to whatever they come up with since I’m a little bit more used to thinking on my feet than some of the juniors, but they like to do weird things to cut Fridays short, and I’ve been suggesting “hey why don’t you design people, and you programming people just get together and talk about little tweaks for an hour or so”
Like whenever I’m out there and wrapping up a new feature, I make it a point to pull the designer aside and walk through what I’ve built with them, explain things in a way that they could design it more effectively (never about aesthetic, usually just little details at this point), and allow them to make a few adjustments so they feel like we’re working together on the product.
That’s like the most difficult thing for them to do though, they’d rather have a 7 person team take a happiness survey than actually just talk shop and whiteboard because it’s fun.