2

What is your best skill as a developer?

 2 years ago
source link: https://dev.to/ben/what-is-your-best-skill-as-a-developer-ia7
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client
Cover image for What is your best skill as a developer?
Ben Halpern

Posted on Mar 18

What is your best skill as a developer?

Whether it is a specific enough technical expertise, or just part of the craft you do well?

Discussion (74)

pic

Collapse

Expand

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.

Comment button Reply

Collapse

Expand

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.

Comment button Reply

Collapse

Expand

Collapse

Expand

Whats that old saying, Gotta break a few million itterations to make a program

Comment button Reply

Collapse

Expand

My ability to relax and stop working

Comment button Reply

Collapse

Expand

Well, I would often start rocking on the chair relaxing, thinking solutions without putting any pressure or let fear of completing things on time take over. This worked really well in most cases but did disturbed others and few asked what are you so relaxed about? Why are you rocking and spinning on the the chair for?

Comment button Reply

Collapse

Expand

Honestly, get out doors that's the best way to solve problems, I used to do my best work on the way home

Thread

Thread

I will try it, I guess other than laziness there's no excuse to just take a short walk. Some problem requires attending to and some are solved in mind, with that distinction I would say I could definitely use going for a short walk for problem solved using mind alone.

Comment button Reply

Collapse

Expand

Hahahahaha ! The most important thing of all!

Comment button Reply

Collapse

Expand

I used to want to be the very best frontend developer, like a Pokémon trainer. I had to catch them all, but now I just want to chill and enjoy hobbies, play with my son and be a smarter developer not work harder

Comment button Reply

Collapse

Expand

You are the real human, peace

Comment button Reply

Collapse

Expand

Not taking bullshit.

Shit roles down hill in software. I don't let bullshit politics or cocky non-technical management affect me.

It's really the soft skills that matter in the long run. Code is easy, people are difficult.

Comment button Reply

Collapse

Expand

Awesome comment. Couldn't agree more.

Comment button Reply

Collapse

Expand

This should be part of a "Top 7 Comments of the Week" list 🤝

Comment button Reply

Collapse

Expand

Collapse

Expand

Yup, I aggree did experince something similar and I did not take it, not well atleast. LOL. Wanna share a few experinces... don't need to go into details.

Comment button Reply

Collapse

Expand

Writing documentation is probably the thing that stands out above some of my other skills.

Comment button Reply

Collapse

Expand

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. ✨

Comment button Reply

Collapse

Expand

That's something I hadn't considered, but am now considering.

Perhaps there's something to glean from my posts tagged with documentation? takeonrules.com/tags/documentation/

Thread

Thread

omgoodness what a collection! Thank you!

Thread

Thread

Thank you for prompting me.

Comment button Reply

Collapse

Expand

Collapse

Expand

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.

Comment button Reply

Collapse

Expand

Not estimating, and ignoring deadlines

Comment button Reply

Collapse

Expand

Some deadlines go away on thier own and some things cannot be known :) devils advocate here

Comment button Reply

Collapse

Expand

Author

Mar 18

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.

Comment button Reply

Collapse

Expand

I'd love to see a post from you about your top considerations for greenfield projects!

Comment button Reply

Collapse

Expand

Abstracting complex things and explaining it the easy way.
Also adapting to change and new technologies I guess.

Comment button Reply

Collapse

Expand

My best skill would be to break down hard-to-understand technical concepts in a way that makes sense for junior developers & even non-tech folks.

Probably the reason why I could transition from a pure software engineering role to DevRel! 😎

Comment button Reply

Collapse

Expand

Understanding Dinosaurs and combing spaghetti. My life since 2019.

Comment button Reply

Collapse

Expand

Wow. Such nice way of describing it. Love that.

Comment button Reply

Collapse

Expand

Communication.

Understanding that the same word, in the same context, but used by a different person, can mean completely different things.

Understanding that I may not understand the full context of a technical tool or a person's perspective, and knowing what questions to ask to get there (sometimes that very question is, "What are the best questions to ask?").

Understanding that sometimes concepts are not complex, they're just hidden behind a bunch of domain-specific vocabulary. More than that, I make these kinds of concepts more accessible to others.

This is how I got into tech without a CS degree, and this is how I'll stay in it.

Comment button Reply

Collapse

Expand

Resourcefulness, Quick Learning & Catching on to new code base quickly by fearless experimentation, let the git worry about things unrelated.

No harm will come as long as I dont create a exprimentation branch and start creating PR from that to be merged to dev, because then I would be in trouble.

Comment button Reply

Collapse

Expand

Self-learning and self-seeking

This skill helped me a lot with fear. I don't mind getting down and dirty with new codebases because I just know that whatever happens, I'll always be able to find the answers I need even if it takes a bit of time.

Comment button Reply

Collapse

Expand

Being goot at math.
I actually graduated in Mathematics and became a developer by chance. But when it comes to those seldom problems that deal with abstraction, generalization, visualization and figuring out how things work from a bunch of data I feel like I have an edge over my colleagues.
It's not something that's always necessary, but it's good to have in a team, and I think it helped me improving some other developer skills.

Comment button Reply

Collapse

Expand

This is a great articulation of math.

I too have a degree in math, yet I rarely use algebra or calculus for programming. Instead its all about abstractions (and sets).

Comment button Reply

Collapse

Expand

Not a hard skill, but I feel like I'm good at over-communicating with my team. It's about consistency.

Comment button Reply

Collapse

Expand

Intuitive problem solving. Makes it harder to explain how I arrive at a solution, but is otherwise a helpful skill.

Comment button Reply

Collapse

Expand

Critical thinking, lean coding

Comment button Reply

Collapse

Expand

I think adapatability.

I started my professional career doing .NET in financial services, now I'm writing realtime OS code for medical devices, and I've done a bunch of stuff in between. I'll pick up whatever and run with it.

Comment button Reply

Collapse

Expand

I'm kinda passable at creating solutions, but once I have them, I'm really good at making up a corresponding problem.

Jokes aside, I'd say I'm kind of okay-ish at building abstractions with heavy metaprogramming.

Comment button Reply

Collapse

Expand

Analogizing technical topics. Besides creating a common ground for everyone in the room, it's occasionally fun and colorful to talk about how Kirk delivers mail to Carol's army of clones (aka Kafka and consumer groups).

Comment button Reply

Collapse

Expand

By far, it's my dedication to writing. I've found that the more I write, the more I learn. And from that corpus of knowledge, novel connections emerge. I think I "see" more things now than I did before I wrote with such devotion.

Comment button Reply

Collapse

Expand

I'm RPA developer, using Python were standart language. I build automation and inovation for a enterprise where I work, using various librarys/frameworks in Python: Sellenium, Pandas, Mathplotlib, Tabula, etc. I make improvements in the company's internal processes, makes the boss much richer hahahaha :')

Comment button Reply

Collapse

Expand

Skill? Creativity. Whether working on an original program. (And, we all know that coding a new program is often a thing of art. : )
Or troubleshooting and updating an existing program that's out there by another coder.
It comes down to creativity. Ability to think out of the box. Be flexible. This leads me back to keeping a creative mindset to be successful.

Comment button Reply

Collapse

Expand

the ability of Zooming In and Out, meaning:

  • reduce the scope and focus on details when it comes to implement tiny simple effective methods with single responsibility (and all other solid principles) and be able to unit test and debug "surgically".
  • move away from those lines of code and get an eagle eye view, understand the big picture, the context where your piece of code works.

and while zooming in and out, be creative and bold and challenge the status quo, pointing out flaws and suggesting solutions or improvements

too often we put ourselves in a cage and implement crazy complicated solutions only because we did not ask the developer close to us (working on same feature but different subtask) to change the return value of the method they are implementing...

Comment button Reply

Collapse

Expand

Debugging, fixing, and optimizing existing code.

I am far, far better at finding and fixing the bug, optimizing a nonperformant application or piece of one, or tackling a pile of tangled code spaghetti and turning it into a saucy code tapestry than I am at building even the simplest of applications in the greenfield and from scratch.

Comment button Reply

Collapse

Expand

Communication and analysis - don't jump into coding right away, understand the problem first, ask questions!

Comment button Reply

Collapse

Expand

Beautifying and organizing code and documentation are my favorite sub-task in developing!

Comment button Reply

Collapse

Expand

Collapse

Expand

Sub- tasking.. I always try to focus on how to reduce a task to about a unit time...

Comment button Reply

Collapse

Expand

Responsive website design

Comment button Reply

Collapse

Expand

Being calm in high pressure situations ✌️

Althrought I'm not as good as I think

Comment button Reply

Collapse

Expand

I ask questions, a lot of questions

Comment button Reply

Collapse

Expand

Sharing whatever cool thing I learn with the team

Comment button Reply

Collapse

Expand

Collapse

Expand

My love for learning! In development there is always something new to keep am eye on or to better yourself somehow!

Comment button Reply

Collapse

Expand

Learning fast as soft skill and Typescript

Comment button Reply

Collapse

Expand

debug and find the problems about a bug

Comment button Reply

Collapse

Expand

Process automation and leveraging existing tools in a way they weren’t necessary designed to in order to gain an edge.

Comment button Reply

Collapse

Expand

not sure that's really a skill but I'm perfectly honest when I don't know smth or when the solution is unclear at some point.

Comment button Reply

Collapse

Expand

I am in best of my learning skill

Comment button Reply

Collapse

Expand

Pretend to be a non-technical user and see the product from his point of view

Comment button Reply

Collapse

Expand

To make my way rather than to find one when attempting to solve a problem

Comment button Reply

Collapse

Expand

Thinking and write thought as fluent as code.

Comment button Reply

Collapse

Expand

A better question is "What do other people on your team think your best skill is?"

Comment button Reply

Collapse

Expand

Listening and then asking questions to find out what clients / people actually want.

Comment button Reply

Collapse

Expand

Or just place code that spies them and tell you what client wants.

Comment button Reply

Collapse

Expand

Guess having learnt how to learn.
Uh, no, it's having learnt how to say "no"

Comment button Reply

Collapse

Expand

Solve problems, I dont know how explain, but I have creative ideas to solve problems haha (sometimes a kludge '-' )

Comment button Reply

Collapse

Expand

I think Watching Tutorial :D .Just kidding-

Comment button Reply

Collapse

Expand

Collaborating with different kinds of developers, we're in the people business where our main tool is technology, not the way around :)

Comment button Reply

Collapse

Expand

I guess Javascript. It is the only language I am most comfortable with.

Comment button Reply

Collapse

Expand


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK