9 karma · joined September 28, 2011
A skilled developer can single-handedly shake up the paradigm and drive things in a new direction. The real challenge for the organization that grows up around that game-changing idea is to avoid behaving like the one it replaces.
Lived in SQL Server from when it was hard to differentiate from Sybase / OS/2. Did anyone ever have the problem that if you unplugged the monitor on an Sybase / OS/2 machine the whole box would crash?
In the mid-90's, the saving grace for us with VBIII / SQL Server was a small, self-published (at the time) book, Hitchhiker's guide to SQL Server, by Bill Vaughn. Actually went to dinner once with the guy- He flew helicopters in Vietnam on SAR missions... give him a couple of drinks and he'll tell some -very- interesting stories.
Three very cool years 2003-2005 creating games using Torque and GameStudio to host educational content (an FPS, hosting .avi's instead of shooting), then the C# .Net world on the desktop and the web. A little Python and Pearl thrown in for fun.
I'm lucky that I'm the go-to guy for weird requests. Keeps the job interesting.
Who knows... -We- surely don't. I feel like I'm outlining a plot for a Tom Clancy novel.
It's easier to benefit from a false-flag attack by just doing it- denials don't carry as much weight in an emotional, post-attack context. When forewarning is given for a false-flag, you give the accused a chance to back away and say "it's not us" before an event, lodging enough doubt that the size of the crowd with torches and pitchforks isn't as big afterwards... I think this would be counter-productive for the guys staging the false-flag attack.