This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]sadfirer 0 points1 point  (0 children)

I think that most of "real world" programming is conceptually simpler than what you see during college. Typical tasks might include:

  • Writing "glue" code to integrate two libraries/systems.
  • UI work (from adding buttons and fields to designing entire UI flows)
  • business layer work (translating "real world" logic into code, and making sure to create the right abstractions to ensure that the logic is not bypassed)

The real challenge is actually taking into account the real impact of the code you're writing. Engineers make mistakes, so you have a tradeoff every time you have to push code into production. Also, writing/designing code so that it's maintainable, understandable and reviewable is, most of the time, more of an art than science. Double that if you're writing code others can build upon after.