Whether it is a specific enough technical expertise, or just part of the craft you do well?
For further actions, you may consider blocking this person and/or reporting abuse
Whether it is a specific enough technical expertise, or just part of the craft you do well?
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (98)
Writing documentation is probably the thing that stands out above some of my other skills.
I would love to read a blog post by you going over better documentation skills as a new developer! It doesn't get talked about enough and there seems to be no clear cut way of how one should go about writing it. โจ
meanwhile, the documentation I write is just ๐คข๐คฎ
Not a hard skill, but I feel like I'm good at over-communicating with my team. It's about consistency.
I think depending on the situation and opportunity at hand, my best skills are: Solving problems from scratch, i.e. greenfield projects.
But then at the other end of the spectrum, I fancy myself a really good debugger.
I'd love to see a post from you about your top considerations for greenfield projects!
I think listening and knowing the right questions to ask (so we can get to a better problem definition) is probably my super power. I would probably add documentation/blogging and simplifying the complex as probably other things I think I am pretty good at.
Abstracting complex things and explaining it the easy way.
Also adapting to change and new technologies I guess.
Creating problems. Sure, I could say that problem solving is my best skill (and it probably is), but the fact is I also create problems by developing tech that then needs to be maintained, fine-tuned, updated, rewritten, replaced, re-thought. There are a few thousand lines of C# and JavaScript processing sales leads for two car-sales companies. I listened, thought, developed but now I'm stuck with a fairly constant regime of maintain, fine-tune, update that I can't get away from. So maybe my best skills as a developer are dogged persistence and faithfulness to the product.
Starts out with "creating problems" and finishes with "dogged persistence". Add "pivoting while marketing self" to your skills list too :P
I feel that though. You create a cool utility or tool and now it's your child.
nice
Whats that old saying, Gotta break a few million itterations to make a program
Not estimating, and ignoring deadlines
Some deadlines go away on thier own and some things cannot be known :) devils advocate here
Critical thinking, lean coding
Debugging
I am in best of my learning skill
Some comments may only be visible to logged-in visitors. Sign in to view all comments.