- TBD read article of personal user manual and create own framework.
Working with a Team
TODO Review list and think if this deserves its own post, possible it would require a section to join all the posts (Being a Senior Software EngineerBeing a Senior Software Engineer
TBD
TODO
Definition of Senior Software Engineer:
why Engineer over Developer?
Senior as a concept that encapsulates Mid, Staff or any lead role that mixes managment with devel..., The future of Software Engineering (2024)The future of Software Engineering (2024)
Context
There's an interesting article published by Gergely Orosz That talks about the current state of the Tech Ecosystem and the future ahead for software engineers. In the talk he gets deeper i..., etc..)
Problems I've found:
- Lack of information about the product or the code.
- Merge conflicts that makes me start the feature from the begining (idea for future post: "Merge conflicts are a red flag").
- Broken tests.
Some solutions:
- Constant communication to avoid working in the same knowledge area.
- Slice better the user stories into smaller chunks.
- (related) Make branches shorter and quicker to be merged into main.
- Constant update with main branch.
-
Ideas?
- Related Being a Senior Software EngineerBeing a Senior Software Engineer
TBD
TODO
Definition of Senior Software Engineer:
why Engineer over Developer?
Senior as a concept that encapsulates Mid, Staff or any lead role that mixes managment with devel...
References
- Personal User Manual
- Being a Senior Software EngineerBeing a Senior Software Engineer
TBD
TODO
Definition of Senior Software Engineer:
why Engineer over Developer?
Senior as a concept that encapsulates Mid, Staff or any lead role that mixes managment with devel...