What development skills did you gain after 7-10 years of experience developing OO?

Question

Some development skills, such as refactoring operations, seem almost unlimited Pontic for training - only a fool will say that he has finished learning it.

Other skills are specific tools, and as good developers, we learn new tools most of the time.

But some skills are related to how you think about code and how you approach coding, sometimes how a particular function of a tool can be applied. Rotating pair programming and working closely with other people seems to be the best way to acquire these skills, although of course not the only method. (And sometimes you study things that SHOULD LEARN 5 years ago, these are not the ones I ask for)

So, I want to connect the program to all StackOverflow:

What are your belated coding skills?

Editing: I suppose I don’t think about what you would have learned as part of the curriculum if you left school today.

Answer 1

These are soft skills to be a better developer on the team than nuts and bolts, actually capable of creating an application that (more or less) complies with the specification and compiles and causes the user / tester not to scream too much.

• when you need to protect strict code, because you know that it will save you time in the end.
  • when not explicitly making a point (1).
  • how to work in a team
  • how to read and respond to a specification that is not surprisingly accurate or clearly written.
  • when (and how) for someone else to have a funky project because you're too busy drudge

Basically, there are times and places to be an alpha male about being the best animal packaging, but too often programmers cannot criticize, and we cannot always play with projects such as our toys,

If you cannot do this, then Guy Kawasaki and Joel Spolsky have written a lot of good material to create your own company.

Answer 2

Only when I realized that I needed people’s skills to complement my technical skills did I really begin to develop my career.

It is amazing how often programmers ignore this or are perceived as insignificant in comparison with “development skills”.

Answer 3

It may seem silly and obvious, but ... I think it took many years to understand how interested I am:

• Knowing when to write comments where they are really needed.
• Knowing when to NOT comment, because the code is now quite self-documenting.

Answer 4

Prototyping and Mocking.

I think of the times of the past when I sank into my legs - first in developing the in-situ function - it is much better to isolate the problem in the sandbox application.

Mocking - again, following the principles of isolation (Divide and Conquer), this is absolutely the core for any design that I have come up with these days.

Answer 5

Some skills when it was not, when I started coding:

• Module testing
• Refactoring
• Some other flexible paradigms.

You must stop training if you stop breathing.

Answer 6

Pragmatism and people's skills.

Be pragmatic in a situation. Yes, it may be perfect, but is it really necessary. Something may be the coolest feature in the world, but will it really earn more. By asking these questions and being realistic, you can filter out a lot of chaff from wheat.

I am still learning people's skills. It's not all about knowing all the answers, but rather passing them on to Management and Clients as they understand and hug. Being autistic with OCD and Bi-Polar is sometimes a little difficult.

Answer 7

Hmm, writing testable code through dependency injection. How did we deal before ...

For me, knowing what to test.

I was a fan for a while who said that everything should be checked, methods for receiving / installing DTO, etc. This is impractical and not necessary. You must experience (to death) complex and critical material, because this is where your complex and critical flaws are. Check the rest lightly.

Answer 8

I learned not to get attached personally to the code that I write. I no longer feel a personal attack / violation when people change my code or criticize my code.

Answer 9

That I probably do not belong to management (where I spent a couple of years). I am happier code than management :)

Edit: Also; I'm just starting to understand TDD, and I like it!

Answer 10

Software architectures, programming in general. I realized that software -> code and the question of programming languages ​​are tertiary at best.

Answer 11

Humility to see so much code, some good, some bad, and then some, which is just strange that you learn what you want to have, where you work, and what you don't want to have. For example, some, like cowboy-style programming, while others are completely methodical and will not do anything to be part of a plan that has been written, tested and signed by three senior people to have a blessing. which may take a couple of weeks.

Improve your organization of the code and see where you can reorganize to do something more general, to have more uses, or when trying to block something to make it happen, rather than cosmetic changes made over and over again when the client doesn’t I know what they want, but they don’t want the 101 prototypes they saw.

Answer 12

Knowing: although I can, it does not mean that I have to "pamper myself" and build every request that comes to my mind. My main task is to provide a solution, and if it means taking something already there and expanding on it, then this.

Answer 13

I really agree with the message "People Skills", but beyond that:

To name one thing, I really understood how languages ​​are not really languages. These are dialects.

It seems that for every micro-part of knowledge that goes into the autonomous parts of my fingers, I am blessed with the opportunity to generalize to a higher level of understanding of things. - These are the words of my father, who is a welder / steelworker. I can not agree more.

/Robert

Answer 14

Working with only the logical structure of my code and ignoring the locations of physical files as much as possible.