kmoorevs wrote:

I'm now renting a virtual rig at Azure for new apps and that could conceivably take over by re-pointing the domain as you did. Of course, that still requires my ability to access Azure which was not fun on a mobile, last time I had to do it!

Having worked through a couple of DRP exercises, I'll take "not fun" as a vast improvement over "not able to".

I'm not with CDP. I think that both he and you are so wrapped up in your own spam-centered stereotype that you are ignoring the OP's actual subject. He's not considering sending out hundreds of text messages trying to scam folks, he's looking into a simple way to selectively alert multiple employees -- e.g., sending out a notice when there is an opportunity to work overtime. That is not a bad thing. My wife signed up to get text messages from the state office she works in when they are starting late due to weather issues. When I was working for Molina Healthcare, they had a similar "Emergency Notification System" that broadcast recorded messages -- you'd hear cell phones going off all over the office whenever there was a decision to close early because of an incoming storm. So ditch the self-righteous indignancy and either answer his question or go vent somewhere that you're not driving off the folks who might.

Sander Rossel wrote:

I really hate regions! :sigh: They obfuscate the code, you only get to see parts of it, but I want it all! If your code is really so properly written you shouldn't need regions.

I fundamentally disagree, Sander. First of all, regions do not hide anything -- nobody holds a gun to your head and forces you to collapse them. Instead, they only allow you the option of not having to look at it every time you scroll up or down. Working in SQL all day long, I consider anything which makes navigating between key sections code faster or simpler to be A Really Good Thing. Second, regions are a purely for organizing your code, and outside of a Microsoft demonstration there is no class too small to benefit from a little functional structure (e.g., these functions are for the customer UI, these are for the auditors, and those are for the order-fulfillment folks). If a single-page essay can be more readable by being divided into 3 regions (introduction, body, and conclusion), then what makes you think that a 6- or 7-function class couldn't? Lastly, I question whether code is really any better when you take a 12-step chunk of linear (a.k.a. "spaghetti") code and refactor it into a 3-step process with each step having 4 layers of abstraction in the form of calls to other functions. I would say that there are many occasions where spaghetti code is more readable to both the human and the compiler.

Don't forget to also weight according to the severity of the motivational floggings that are part of the debugging process. ;)

For some of us, "Transact-SQL" <> [Transact-SQL]. In Sybase SQL Anywhere, you can get a current date-time value using "CURRENT_TIMESTAMP", "GETDATE( )" , "CURRENT TIMESTAMP" or "NOW( )". Good luck using either "CURRENT TIMESTAMP" or "NOW( )" in Microsoft SQL Server.

CDP1802 wrote:

If the minor differences between databases already make you cry, then please stay away from anything that has to do with browsers.

But it's the minor differences that cause the subtle bugs which take the most time and require the greatest pulling of hair to resolve.

Jörgen Andersson wrote:

why do you need to support more than one database?

Because one features premium pay and the other features ubiquitous jobs?

Mark_Wallace wrote:

anyone with a non-apple OS has no interest in running it on their machine

I have an interest. It's just not enough of one that I feel like ponying up hard-earned lucre to pay the Jobs tax.

Mark_Wallace wrote:

I wanna be a eunuchs developer! Pass me a bread knife!

Don't you need a butter knife than that? Unless you're one of those guys who leaves unfinished stubs in place of working functions...

>We need another option: > >4) The author should be run through a leaf shredder as a service to mankind. Why a leaf shredder instead of a chipper? Or are chippers only for friends?

Personally, I'm heading away from SSIS in favor of Powershell for increased flexibility and vastly increased debugging transparency.

First, having written a couple of small LOB apps that I got away with naming "[somename] Transmogrifier", it's nice to see someone else use "transmogrify" correctly in a sentence. Second, you might want to look at avoiding the overhead of Visual Studio and recompiling for every change by using Powershell instead -- it read CSV files as datatables, or you can use regular expressions to read the files line by line (been there, done that with my own VB.NET Transmogrifiers).

Well, then there's also the time spent fielding questions once I get to the office after I'm done reading stuff like this over breakfast and initial caffeination.

I've always tended to go the other way -- for a few years, I told people my job title was either "Chief Technowhiz" or "Staff Non-Technophobe"