25+ years as a Software Developer. I'm passionate about process improvement using technology. Let's all work smarter not harder and do more with less.
MY THOUGHTS ARE MY OWN
This assumes you have a separate development branch but ok. Yes. My TFS build/release pipeline runs on check-in of code.
This assumes your software has bugs but if you do UAT (User Acceptance Testing) (I'm getting to this) then you virtually eliminate bugs. If you use TFS you don't need a separate bug database.
Fix code before and while writing new code. Yes.
Yes. This is actually a great point and practice. It hold developers accountable.
No. Agile development is against written specs. User stories and lots of collaboration.
Yes. I would love to have a door I could close.
Yes. VS baby!
Yes. The actual users. I will make my UAT point here. I'm not bashing QA folks but if you stress developer unit testing and set a UAT/QA culture you can get away with not having a separate QA team. It is better to have the people that will be using the software every day testing the software making sure requirements are met. While I will admit this opens yourself up to scope creep and a long UAT/QA phase but when your software finally make it to production it is essentially bug-free and you don't get feature requests for at least 6 months. Living the dream.
You are crazy not to these days. This is why I love TFS. You get requirements, project, build and release management ALL-IN-ONE!
My next hire will write code. BEWARE.
Yes and it's amazing when it works.
Full disclosure: I'm a software development manager at a large company.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Full disclosure: I'm a software development manager at a large company.