Used to do DevOps before they even called it that way: Linux. Python. Perl. Java. Docker. For fun and profit. CTO level generalist working for a mid-sized tech-centric company.
Dresden, Germany
Depends upon how your project is managed and how you interact with your customer(s) I suppose. In an agile understanding, it would be good to embrace change early - as it might be better to change a project rather than completing something that apparently might not meet changed requirements anymore. I'd really try going through small iterations, coming closer and closer to what the customer needs and, in each iteration, talk about requirements, effort needed to implement them - and whether feature X or Y is really required or worth the effort. But again this really depends upon your customers expectations and your contract. ;)
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.
Depends upon how your project is managed and how you interact with your customer(s) I suppose. In an agile understanding, it would be good to embrace change early - as it might be better to change a project rather than completing something that apparently might not meet changed requirements anymore. I'd really try going through small iterations, coming closer and closer to what the customer needs and, in each iteration, talk about requirements, effort needed to implement them - and whether feature X or Y is really required or worth the effort. But again this really depends upon your customers expectations and your contract. ;)