1
Ask HN: How to set up SD practises and processes in a startup as a senior dev?
I am working with an enterprise SaaS startup that is about a year old. They have the product validated, conducted some pilots and are now into the revenue and growth phase.
The founders don't have enough knowledge/experience about software development.
Initial they hired developers who could create a working system but without any systematic organisation and practises like testing or code reviews.
I joined a few months back and seen the code-base get uglier day by day and all I have done till now is ask people about technical documentation for every feature/fix they code, writing tests and following proper branch structure in git so as to merge the code with a peer review.
But nothing such has been happening and I am afraid, we will reach a stage where making changes to existing code will ensue lot of side effects.
It is my responsibility now to make sure these processes are setup and followed by all the devs. Given that its a small team of 7-8 devs, it should be easy to enforce these practises but that hasn't been the case.
How do I go about it? How do I make sure that business execs don't pressurise the tech people enough to cut corners and flung the process?
As a not so experienced developer, what are other things I should focus on?
And is it possible to implement this without taking a hit to productivity?