[…] Here you can find 71234 additional Info on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Read More on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Read More on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Read More Info here on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Information on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Here you will find 9674 additional Info to that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Information on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Read More Info here on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Here you will find 47357 additional Info to that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Find More Info here on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Find More to that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Read More Info here to that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Find More on to that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

[…] Find More Information here on that Topic: startupsanonymous.com/question/constant-tech-issues/ […]

That is a strong sign that either your people are incapable or delivering or the requirements are too big for the timeframe. Judging by your responses below, there is a chance your people are too scared to tell you if something is wrong.

Another issue you are probably not writing use cases and expecting them to read your mind. The best way to get what you want is to clearly lay out expectations and needs. So If you want password validations to be shows, specify that as being a requirement for acceptance.

Developer are robots – you tell them to do X, they do X. Asking them to do more, is futile. You need better UX and user design. I have a lot of friends who do this type of work, that’s what they get paid for. Their job is to see the small things like error messages, how should those error messages be presented, how do they go away, what is the user procedure for fixing errors, etc. etc. etc. You need to hire or develop those capabilities so problems like this don’t happen. It’s not really the developers job to say, “Hey, I think we should have a blue and white modal that says error with this copy,” and also make them create the user flow to fix the error. I mean, c’mon, if your leadership team hasn’t figured out how to hire an experiential designer, user test groups, or an architect, then it’s a failure of leadership. Even when I made a tiny app, user error and cancellations were big part of the engineering process. It was mapped out in the UML from day 1. Your problems are bigger than your developers.

Also, babysitting is an accurate description — but hey, it’s part of the job — you just have to continue hiring “attention to detail” type people (in all roles) and reward/promote them. Marginalize or fire the ones that require too much baby sitting. It’s a constant process (in any job, at any company).

Okay, I see more of the problem now (not just queiries). You are suffering from what nearly ALL software development project go through. You are correct, they (developers) should be looking left and right and using better judgement. But that is true with ALL employees in every position — some give a shit, others don’t and short cut.

What you are describing is the need for Quality Assurance (or software testing). I’m currently us a Ukraine Ruby on Rails developer (I’m on East Coast US) and I run into same frustrations (even when using multiple developers). The password issue is classic (lots of sites suffer from this). Want to see something stupid — go to most any hotel site (like Hilton) and select room for week of Christmas — you’ll get some stupid “ERROR, ROOM not AVAIL” message at top of screen. I’m thinking, geez, this is Hilton, can’t they hire better programmers.

So what to do? You need someone to do software testing (I do my own, it’s a pain). Maybe you are the best one to “own the product/User experience”. Maybe you can hire someone — really anyone who is NOT a developer can test to make sure your site works in a manner that will satisfy users. Maybe give one of your clients a discount for pointing out flaws. Be creative!

And constantly send emails back to your developer to say “guys, fix this, fix that” and say “come on at least take SOME time to look at this from the User’s perspective (I bet they complain about same password error when they try to buy something online from other site).

Then, REWARD those that do look Left & Right. Rewards/incentives always better than punishment — people love recognition.

Of course, firing the slacker in the bunch is always good idea too. I had team of 20 developer at my last startup and the good ones were always glad to see the slackers go.

Good luck, this isn’t easy stuff.

Its not only related to the queries. The things that make me angry is that people cosntantly don’t look left or right. Example:

We have a signup on our website with a password with password rules in place. The developers did not see it necessary to give a meaningful error response like (password does not have a minimum of 8 characters, a number etc.) Instead we show some cryptic error message that something went wrong.

Another example: If a client cancels we neither get a message and there is a bug that did not set the client as inactive. We falsely billed clients already because of this.

3rd Example: The app crashes (becomes unresponsive) because a client integrated us wrong and this affected all other clients too. We are build on cloud (so all clients run on the same version / infrastructure).

I am furious about the issue we are having. Maybe they take it too easy and I should fire some people to set an example ? I would expect people to look a little bit left and right and not behave like robots. I don’t want to babysit every little bit here.