DEV Community

Discussion on: What are your guiding principles in software development?

Collapse
 
cjbrooks12 profile image
Casey Brooks

Slow down, take the time to do things right. You'll end up going faster in the end.

Numerous projects I've worked on with this in mind seemed to have really slow progress in the beginning, but really fast progress towards the end. In all cases we've always hit our initial timeline goals, but exceeded expectations on follow-up work.

Collapse
 
champi profile image
Champi • Edited

Yeah and do TDD.

Collapse
 
sergio profile image
deleteme deleteme

I disagree with TDD. Sure write tests for your things, but TDD is just kool-aid that caught on in early 2013. Academically it makes sense, but in reality it's not practical.

Collapse
 
shostarsson profile image
Rémi Lavedrine • Edited

That is indeed a good approach but as I had experimented in a lot (too many for sure) of organizations, you are too often force to rush on things because of business deadlines, promises made (not by the devs) to the upper management, and the list could go on and on.
So if your Product Owner, Stakeholders, etc... are not from technical background you are going to have a hard time.

So I found it very useful to make quick Brown Bag Lunch open to everyone, so that anyone, from technical background to marketing etc can join, have fun and have a better understanding about what it takes to develop something. But as it is not the end, debug it, test it, deploy it, etc...

It is very helpful for everyone. And then if everyone speak a common language it makes things easier and we can tend to take the time to do things right so that we can go faster in the end.