Lots of good comments in here. The only thing I'd add is that you need to cultivate what I'd call 'systems thinking'. What I mean by this is that you don't want to work on projects in a silo of...
Lots of good comments in here. The only thing I'd add is that you need to cultivate what I'd call 'systems thinking'. What I mean by this is that you don't want to work on projects in a silo of focus.
Out in the working world, stuff you build will 99% of the time be part of some larger system or use case than just the widget you are directly responsible for or working on. One of the things that sets great engineers apart is the ability to keep the larger picture in mind for consideration when they're producing work. Not thinking about that while designing a solution or building something is the #1 cause of frustration and friction. It's also a great way to continuously learn, and in some cases even stay ahead of your own project allowing you to anticipate what might be required.
Many decisions and direction will come from non-CS people. Many times Project Management/Product Owners/Managers are not nearly as savvy tech wise, but are still the ones setting the vision for products. Combining a good systems thinking mindset with the advice already posted here will make it MUCH easier to help direct good decisions and produce better work with less frustration.
Lots of good comments in here. The only thing I'd add is that you need to cultivate what I'd call 'systems thinking'. What I mean by this is that you don't want to work on projects in a silo of focus.
Out in the working world, stuff you build will 99% of the time be part of some larger system or use case than just the widget you are directly responsible for or working on. One of the things that sets great engineers apart is the ability to keep the larger picture in mind for consideration when they're producing work. Not thinking about that while designing a solution or building something is the #1 cause of frustration and friction. It's also a great way to continuously learn, and in some cases even stay ahead of your own project allowing you to anticipate what might be required.
Many decisions and direction will come from non-CS people. Many times Project Management/Product Owners/Managers are not nearly as savvy tech wise, but are still the ones setting the vision for products. Combining a good systems thinking mindset with the advice already posted here will make it MUCH easier to help direct good decisions and produce better work with less frustration.