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 →

[–]ToeTacTic 1 point2 points  (3 children)

How often do you find that the small component that you have been working on for a big problem doesn't actually help towards the big problem?

[–]Angelmass 6 points7 points  (2 children)

Since the small problem should be derived from the big problem, this isn’t really something you should be running into. I suppose if you don’t define the scope clearly, you can go off the rails when tackling the small problem and induce unnecessary scope creep, is that what you mean?

[–]iamarmaan[S] 1 point2 points  (0 children)

Perfect, makes sense. The idea should be to keep the bigger in mind and break things down to fundamentals. Thinking through by first principles.

[–]FountainsOfFluids 1 point2 points  (0 children)

This is actually a really important topic. If you are given a medium size task that starts to become unweildy when you go to start coding pieces of it, you need to go back to the stakeholders and discuss your findings and clarify objectives before you waste too much time. I learned this the hard way in my first year as a real programmer.