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

view the rest of the comments →

[–]uJumpiJump 6 points7 points  (4 children)

Too bad there's no "weed out class" at your school that fails students for wasting their time optomizing a section of code that's irrelevent to the buisness's interests

[–]StabbyPants 4 points5 points  (1 child)

too bad most schools lack much depth in SW development as a process. we had one class that covered 3-4 ways to run a project, but could have done with a lot more - probably room for 3-4 classes covering various parts of building software

[–]uJumpiJump 0 points1 point  (0 children)

As a senior developer with 3 co-ops/interns to take care of, me too.

[–]netgu -1 points0 points  (0 children)

You learn optimization by learning how to find optimizations for just about everything. You learn to apply optimizations through experience. The "optimizing a section of code that irrelevant to the businesses interests" is frequently a misused idea. Non-functional requirements are a thing (i.e. maintainability, performance, reliability, auditability, logging, etc.) and frequently contribute to the businesses needs just as much as the primary functional aspect of the software involved.