Skip to main content
Software Engineering

Return to Question

Post Closed as "Not suitable for this site" by Ixrec, durron597, Community Bot, Bart van Ingen Schenau
Post Reopened by gnat, BЈовић, Martin Wickman, Rachel, Michael Brown
changed title to better fit question text
Link
gnat
  • 20.5k
  • 29
  • 117
  • 310

What can a technically proficient senior software developer study to keep improving

edited tags
Link
gnat
  • 20.5k
  • 29
  • 117
  • 310
edit to reopen: removed polling and "asking about your attempted solution rather than your actual problem" // detailed discussion at http://meta.stackoverflow.com/a/66378/165773
Source Link
gnat
  • 20.5k
  • 29
  • 117
  • 310

Say you have been programming for over 10 years. You know many languages, with few of those at very detailed level. You have been designing architecture for solutions, worked on and delivered larger projects. You have been studying patterns, best practices, effective coding guidelines, unit testing, multi-threading, etc.

And then you slowly develop a feeling that most of the books you read, give less and less valuable information per 100 pages of text. So they start giving diminishing returns. You still learn, but you no longer improve by leaps and bounds.

So what do you do next? Is there any other field that's very close and beneficialWhy does learning become less productive compared to software developershow it was before? Any books that have changed

Back then, it used to change your way of thinking, taught you new things and broadened your horizons that later improved either your current profession, or allowed to invent/manage/build something new?

Should you look outside. Why is it no longer the software field, or keep improving in your area of expertisecase?

Say you have been programming for over 10 years. You know many languages, with few of those at very detailed level. You have been designing architecture for solutions, worked on and delivered larger projects. You have been studying patterns, best practices, effective coding guidelines, unit testing, multi-threading, etc.

And then you slowly develop a feeling that most of the books you read, give less and less valuable information per 100 pages of text. So they start giving diminishing returns. You still learn, but you no longer improve by leaps and bounds.

So what do you do next? Is there any other field that's very close and beneficial to software developers? Any books that have changed your way of thinking, taught you new things and broadened your horizons that later improved either your current profession, or allowed to invent/manage/build something new?

Should you look outside the software field, or keep improving in your area of expertise?

Say you have been programming for over 10 years. You know many languages, with few of those at very detailed level. You have been designing architecture for solutions, worked on and delivered larger projects. You have been studying patterns, best practices, effective coding guidelines, unit testing, multi-threading, etc.

And then you slowly develop a feeling that most of the books you read, give less and less valuable information per 100 pages of text. So they start giving diminishing returns. You still learn, but you no longer improve by leaps and bounds.

Why does learning become less productive compared to how it was before?

Back then, it used to change your way of thinking, taught you new things and broadened your horizons that later improved either your current profession, or allowed to invent/manage/build something new. Why is it no longer the case?

Post Closed as "off topic" by Caleb, Community Bot, gnat, Frank Shearar, ozz
Source Link
Coder
  • 7k
  • 5
  • 40
  • 49
Loading

AltStyle によって変換されたページ (->オリジナル) /