Michael TharringtonLast Friday, @david_j_eddy dropped a fun discussion topic here on DEV:
Lots of folks piled on the comments, shortening their jobs to just the essentials. In case you missed it, here are a handful of descriptions that I found particularly on point...
For those that code with an eye on requirements.
For those that refactor old code.
Honestly 90 % of my job is refactoring legacy code to the point in which it is usable & wondering if my client will pay me for it.
... in other words:
"fixing the prev. persons leftovers"
Haha! Well, at least there's work to be done! 😅
For those that manage and code.
Knowing and telling everyone what everyone else is doing.
Okay, I do a lot of translating between coder-speak and human too, and help everyone with everything, both coding-related and other stuff. Keeps everyone happy if they only have to concentrate on their own job. And happy means efficient.
Making things work, be it code, managing people, new hires, hardware issues and so on. There's no dull day from that point of view, there's always a 'fire' to extinguish somewhere.
For those that avoid meetings.
Avoiding meetings.
For those that fiddle.
Fiddling...
I’m always fiddling with something. Code, design, copy, whatever. I’m a fiddler.
For the many sad folks that double as their org's IT Department.
"How do I print?"
uuuhhhggggg, not again!?
I get called about the copier pretty frequently too, though mostly by the same person -- and usually when convenience is low.
I know that feel bro 👊
Sorry peeps! 😔
For those lucky enough to write mostly just code.
Luckily: Writing
Mostly code.
Well, looks like there's quite a bit of overlap in our jobs... just know, you're not alone.
So, I pose a new slant on this same question: What's the other 10% of your job? What are some of the oddball things you do throughout the day? And how does that 10% stack up against the 90% part... more fun, less fun? Well, hopefully it's more fun than helping somebody print something! 😄
p.s. @vaidehijoshi is the bomb. (this is a test)
Looking at the requirements of a project, then looking at the code, then... (╯°□°）╯︵ ┻━┻
In all seriousness though its taking requirements and implementing them. Sometimes its in very old bad code, some ok code, and sometimes some really good code. The hard part is understanding the big picture when there are thousands of tables, separate systems that need to talk to each other and with almost none of it documented.