Skip to main content
16 events
when toggle format what by license comment
Dec 5, 2018 at 3:16 answer added DigitalBlade969 timeline score: 3
Dec 4, 2018 at 20:37 comment added NKCampbell If you are writing a new system that ignores this old tool completely - what's the problem? Old developer got his feelings hurt? He's either valuable enough that the company will preserve his feelings and go back to the old system, or the new work is important enough that they'll thank him for his past contributions and carry on with the business at hand.
Dec 4, 2018 at 16:14 comment added Fattie In software this is a total non-issue. Totally forget it - because it's an irrelevant non-issue. What's the next thing that has to be done? "What can you do?" The issue is a billion years ago, put it out of your mind. Do nothing.
Dec 4, 2018 at 15:25 review Close votes
Dec 10, 2018 at 17:00
Dec 4, 2018 at 14:09 comment added dwizum based on your second to last paragraph, I'm not sure why you still need the other developer. You're saying that the new system is operational and bugs are addressed quickly. It may hurt to have burnt a bridge, but what are you hoping to get out of mending the relationship?
Dec 4, 2018 at 12:10 comment added serge1peshcoff By phone, no, as it would cost too much. Probably on Skype, that can be an option. Though I'm not sure if he would want to talk to me in person.
Dec 4, 2018 at 12:08 comment added Caroline Is it possible to phone this person? In my experience people are more reasonable when they are speaking to someone, rather than just writing an email.
Dec 4, 2018 at 12:01 comment added serge1peshcoff I don't have such a possibility, as we are living in different cities and meeting in real life is not an option for me.
Dec 4, 2018 at 12:00 comment added Caroline Did you apologize in person? Did you speak with this person face-to-face?
Dec 4, 2018 at 12:00 history tweeted twitter.com/StackWorkplace/status/1069924414245036034
Dec 4, 2018 at 11:27 answer added ItWasLikeThatWhenIGotHere timeline score: 6
Dec 4, 2018 at 10:26 comment added serge1peshcoff @rath valid point. Our problem was, since it is all voluntary, there were little to no people who wanted to test it and give their feedback. Given that, we decided to rely only on our internal testing and kinda enforce using it. I'm still not sure if if was the right decision and how it could be done in other way.
Dec 4, 2018 at 10:12 comment added rath It should be noted that management should not have announced the adoption of a new system without some user acceptance testing. This is important to note down for future migrations
Dec 4, 2018 at 9:15 answer added gnasher729 timeline score: 10
Dec 4, 2018 at 8:50 review First posts
Dec 4, 2018 at 8:58
Dec 4, 2018 at 8:46 history asked serge1peshcoff CC BY-SA 4.0