I joined a small startup a few months ago. Working with our CTO:
First, he keeps on telling the dev team that we need to commit our source codes often at the end of the day. We are using git by the way. One day, I was so curious how he is committing and branching and I would like to learn git branching strategies from him by looking at a project he is solely working on. To my surprise, I cloned the repository of the project that he is working, looked at all the branches, and the last commit is 4 months ago which was from a developer who resigned. And he has been releasing the software every week and he is doing a manual build from his machine. Most likely he doesn’t commit anything to his local git repo.
One day I asked him if we need to do pull requests as part of our git workflow. I feel like he gave me a textbook answer of what a pull request is. But this was never observed in the company.
Second, his debugging technique. Our CTO keeps on doing print statements instead of debugging using breakpoints. I remember he was stuck on a problem for days, one of the developers helped and that developer used breakpoints and watch to debug and was able to easily resolved the issue.
Third, he showed us a V-model type of development that we should follow. Our CTO explained all of them in a textbook fashion including unit test, integration and system tests. I remember our CTO sent his source codes zipped via an email to one of the developers and that dev told me that there are no unit tests on it.
If I will be exposed to these things for years, it may eventually look normal to me in the future and I am afraid that I may pick up bad habits that I will be bringing to the future company that I will be joining with. What to do in this situation?
submitted by /u/throwthemaway8753
[link] [comments]