Skip to main content
27 events
when toggle format what by license comment
Oct 20, 2021 at 13:17 comment added gnasher729 Don't think you are the only one who knows about some methodology. Probably almost everyone knows about it and decided it's not worth the effort.
Oct 19, 2021 at 21:48 comment added Thorbjørn Ravn Andersen CI should be a very low-hanging fruit if they use a modern version control system (like git). Gitlab is nice.
Jun 25, 2021 at 6:00 history tweeted twitter.com/StackWorkplace/status/1408303979218489344
Jun 16, 2021 at 9:41 answer added Sybille Peters timeline score: 4
Nov 30, 2017 at 1:56 comment added MaxW Having gone through methodology changes let me assure you that to drive such change requires a sponsor with high enough authority to drive the change. The ripple effect of of an organizational methodology change is wide.
Oct 25, 2013 at 12:34 comment added drabsv "told me that it would be nice" - this implies that he only made a suggestion to you, no an explicit requirement or am I wrong? In either case, I can't see why not have a discussion with him first over pros and cons.
Jun 15, 2013 at 7:21 answer added Meredith Poor timeline score: 1
May 6, 2013 at 14:55 answer added Monica Cellio timeline score: 14
Apr 13, 2013 at 10:09 vote accept lortabac
Apr 4, 2013 at 14:57 comment added user5305 @Angelo agreed, yet when the project isnt going anywhere, it can still take less to to do that than to reteach and manually do the testing for every single change, every time someone new joins the company
Apr 4, 2013 at 12:29 comment added Angelo @RhysW, the reality is never a choice between "one-time-writing-of-automated-tests" vs "50x manual testing". Getting to the point of correctly implementing automated testing where it has not existed before is a VERY LONG process with a long-term ROI. It requires deep changes in the organization and any kind of change is particularly difficult for newcomers to pull off.
Apr 4, 2013 at 7:41 comment added lortabac @RhysW One of the reasons why I am afraid of this responsibility is that I am new. I think removing this part of the question would give an incomplete picture of the problem.
Apr 4, 2013 at 0:59 answer added jmac timeline score: 1
Apr 3, 2013 at 15:55 comment added JB King Have you talked with your teammates about considering these changes?
Apr 3, 2013 at 15:23 comment added user5305 One more question, i dont think being a new comer affects this question, its not you dont want to do it because youre new, but because you dont want it to become your responsibility, is this correct or not? If yes then we can edit the question to be more general and attract more answers
Apr 3, 2013 at 14:58 history edited gnat CC BY-SA 3.0
minor spelling correction
Apr 3, 2013 at 14:29 review Close votes
Apr 3, 2013 at 14:58
Apr 3, 2013 at 14:21 answer added HLGEM timeline score: 6
Apr 3, 2013 at 14:18 answer added Dunk timeline score: 0
Apr 3, 2013 at 13:53 answer added acolyte timeline score: 2
Apr 3, 2013 at 13:15 comment added user5305 Whats slower and more painful, one time writing of automated tests, or 50 times, manual execution for an old legacy codebase trying to test one of your changes?
Apr 3, 2013 at 12:58 answer added Telastyn timeline score: 4
Apr 3, 2013 at 12:49 answer added superM timeline score: 21
Apr 3, 2013 at 12:49 review First posts
Apr 3, 2013 at 13:43
Apr 3, 2013 at 12:38 comment added lortabac @NikolaiDante Simply developer. There is no formal junior/senior difference, but there are developers who have been working here for almost 10 years.
Apr 3, 2013 at 12:35 comment added NikolaiDante What job title do you hold in the IT department? Developer, Senior etc..?
Apr 3, 2013 at 12:29 history asked lortabac CC BY-SA 3.0