You can say your boss and I won't judge you :) But really, what is the thing about your job in tech that you would really not like to do?
For further actions, you may consider blocking this person and/or reporting abuse
You can say your boss and I won't judge you :) But really, what is the thing about your job in tech that you would really not like to do?
For further actions, you may consider blocking this person and/or reporting abuse
Kathryn Grayson Nanz -
Susan Githaiga -
Roseanne -
Mr. Algorithm -
Top comments (17)
I would say - not like to do:
Like to do:
These are the things that mostly affecting me during any given sprint.
Great points.
What prevents you to introduce those changes in your team?
At least one of them?
Very good question.
Recently, we got a scrum master who is helping us to go to this direction step by step. Because we believe it would make it a better work environment
What's the main issue you are facing with that?
Your portfolio looks rather good to me elmerivincent.com/
Some recruiters and some companies are like this yes.
Fortunately there is a battle for hiring developers so others know better than that.
Have a look at daedtech.com/programming-job-witho...
If that's not enough you can contact me, find my email at jmfayard.dev/
Don't get me started on the hiring in this industry, I've written two tongue in cheek posts about it and am about to write a third. I have a good job, I'm experiencing burn out and frustration with changes, and personal health issues and the company has completely supported me. Coding tests, 1.5 hr interviews, silly challenges need to go away
What will your thrd article be about?
Sounds interesting to me
Terrible metrics:
Are those metrics used to judge your work? :O
Unfortunately yes.
Not # of tasks finished or something fuzzy like, "solved x crazy bug by spending time reading logs and meetings with different teams"
The amount of times something changes due to new requirements when you are just about to wrap development or testing.
For sure, digging holes and then filing them again is frustrating as hell.
Anything you can introduce in the way your team work to make that happen less?
I'd say it's almost impossible to change it since it is outside influences that cause the problem, not internal dev team.
The response will always be "Be Agile!"
Almost impossible doesn't sound good.
Personally I don't like to work in companies where important problems don't get resolved, so I try to bring them to the table in a polite but firm manner.
When that doesn't work... well there are lots of companies outside that need our skills.+Al
Repetitive tasks that could be automated given a little time, budget or a technology change. Top management however seems to have another way of seeing things 🙄
I would rather say that top management doesn't get into this level of detail,
so it doesn't realize how much time and money they are wasting with those repetitive tasks.
If you can make that case that they are wasting all of this,
they will happy to let you solve their problem by automating it away.
Too many meetings!