You have to keep a dozen of your favorite problems constantly present in your mind, although by and large they will lay in a dormant state. Every time you hear or read a new trick or a new result, test it against each of your twelve problems to see whether it helps.
Every once in a while there will be a hit, and people will say: “How did he do it? He must be a genius
1. Realtime OS Event monitor.
Not perfmon data, not tracing ETW calls through xperf, not event logs. Process + OS state changes monitor (Procmon on browser on steroids..). Has to be evented (maybe GWMI + WQL)
3. Unified alerting framework for the state changes above (Email, Gtalk,Skype + SMS/Phone+ Email + Log)
4. Effective way to implement long-running powershell scripts. Maybe jobs, but something better than jobs which survives a session close / shutdown.
5. Intercept a Shutdown Command
6. Unified Powershell Cross-Cutting Tools. Not just a function or a module, but a background job / service which implements this across different functions.
– Log Writing
– Error Handling.
7. Take a txt file with conditional logic and parse it into ACTION statements which can be executed. Maybe like Bartek Biewalski’s Powershell AST code
8. Simplified multi-threading of powershell code. (Boe Prox, Oisin samples..)
9. Fast compare-object, using SQL instead of .net
10. Someway to assign resource requirement to a script, before you execute. Idea is to scope the problem before you start executing stuff which will blow your system off.
11. Powershell Chaos Monkey (inspired by Netflix Chaos monkey)
Netflix is going to OpenSource Chaos monkey. We can take some inspiration from that.
12. Better Get-Random for small ranges (0-1000). Test for randomness of Get-Random.