1) Your developer is way out of his or her league 2) A more popular framework than .NET? Really? .NET has built in membership providers which means the encryp

1) Your developer is way out of his or her league 2) A more popular framework than .NET? Really? .NET has built in membership providers which means the encrypted password should be a non-issue. If your lead developer is rolling their own login system then they shouldn't be your lead developer. The timezone issue and recurring events are also no brainers. I don't think you're micro-managing at all, you're just trying to avoid horrible design decisions which will hamstring your application down the road.