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
Read next
It's Spooktober ๐. Here are top 15 Google fonts to make your website spooky ๐ป
Paul -
็ฌ็ซๅผๅ่ ๆณๅไธไธชไบงๅ๏ผๅฆไฝๅ็ฐๆฝๅจ้ๆฑ๏ผ
่ฑ้ด้ -
Designer-Developer Collaboration: 2024 Survey Results
Kathryn Grayson Nanz -
Navigating SaaS Billing Software: A Developerโs Perspective
Roseanne -
Top comments (97)
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
My ability to relax and stop working
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?
Honestly, get out doors that's the best way to solve problems, I used to do my best work on the way home
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.
Hahahahaha ! The most important thing of all!
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
You are the real human, peace
And to you Atul
ummm, I like to make responsive designs and till now I have created lots of plan for different software and tools to help our humanity.
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 estimating, and ignoring deadlines
Some deadlines go away on thier own and some things cannot be known :) devils advocate here
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.
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!
Abstracting complex things and explaining it the easy way.
Also adapting to change and new technologies I guess.
Understanding Dinosaurs and combing spaghetti. My life since 2019.
Wow. Such nice way of describing it. Love that.
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! ๐
Forget about algorithms and data structures for one. I've been a software developer for 20+ years professionally, and I started coding when I was 9, implying I've got 39 years of software development experience in total - And the last time I needed "an algorithm" was in 2001 (partially a joke, but still seriously intended).
For instance, who cares about how to implement QuickSort, I've got
List<t>.Sort, and why bother about binary tree structures when 99% of your work persists data in PostgreSQL (or something) ...?Sure, understanding the theory behind algorithms and data structures is important, but vanishingly less and less important due to better abstractions, the same way most developers hardly know any CISC x86 assembly code these days.
My most valuable skill as a developer is composition, architecture and design. It's what makes my code readable, both by others, and by my self (6 months down the road). If you want to sum it up in one word, I'd choose "beauty" ...