[flipper35]

That's what I was thinking, I am outside getting a bit of a workout. I could even listen to music if I wanted to pop the earbuds in.

The meeting today was frustrating. The developer we are talking with says it will take months to make a change so out users can go more than 42 days before changing a password. I said it is either a change in a database for the number of days or it is hard coded. If neither of those it was poorly implemented and they need to hire better developers. Same with the way we log in. There are two choices and we only use the one choice. Ever. Why can't you set a flag so when we want to log in it looks at the URL to see who we are and not offer the second, never used, login. When I asked why it takes 3 months to make that change she said it is a long technical explanation and is not an easy change. I said yes it is. My fear now is they have improperly written a bunch of it and have a bunch to go fix. Even if it is a shared resource between different companies and just the subdomain determines which database it isn't that hard to do.

How hard is it to write - If this company URL, skip to this specific login. Or set a flag in a database. It isn't three months work. I hate when people get info from the development team and pass it on as gospel truth since the liaison doesn't understand it either. Excuse me while I beat a head against a wall.