More features for our employee account lifecycle automations. The coding isn’t as much the hard part as keeping track of all the different moving pieces and how it all interacts.
For example, when using Azure Enterprise App user provisioning to sync data into AD from an HR system, it can only set the Name (separate from DisplayName) property when creating a new user. This limitation isn’t documented anywhere I can find, and it doesn’t even show as an error in the logs when it tries to update an existing one and fails.
It’s the curse of “one man army”: this shit is too complicated to keep it all in my head at one time, and also too complicated to bring anyone up to speed in a reasonable time frame. So I’ll continue soldiering on with it on my own. Thankfully the end is in sight.
Don’t do this sort of shit for any boss that isn’t worth it. Mine has no overtime expectations, is very obviously training me to move upward within the team, and each of the last two years I’ve gotten >10% raises.
More features for our employee account lifecycle automations. The coding isn’t as much the hard part as keeping track of all the different moving pieces and how it all interacts.
For example, when using Azure Enterprise App user provisioning to sync data into AD from an HR system, it can only set the Name (separate from DisplayName) property when creating a new user. This limitation isn’t documented anywhere I can find, and it doesn’t even show as an error in the logs when it tries to update an existing one and fails.
It’s the curse of “one man army”: this shit is too complicated to keep it all in my head at one time, and also too complicated to bring anyone up to speed in a reasonable time frame. So I’ll continue soldiering on with it on my own. Thankfully the end is in sight.
Don’t do this sort of shit for any boss that isn’t worth it. Mine has no overtime expectations, is very obviously training me to move upward within the team, and each of the last two years I’ve gotten >10% raises.