Seriously? If your database of choice is a chore to backup while live, you need to rethink your choice.
Full or incremental backups should be a trivial operation, with support for intra-backup change capture only a little more effort (log shipping, replication, etc.)
Of all the reasons to lose data, "Backups are hard!" should not be in the list.
Funny thing I have noticed, in situations that pay overtime, there is rarely a significant amount of it. When Time = Money, managers quickly learn to plan projects accurately.
Oh it can be money all right. If you paid _actual_ market rates, based on real averages of people with similar experience, responsibilities, and geographic location, then you were on the right track.
However, companies who expect to get a (mythical) jack of all technologies, but pay sub-average rates will get only what they pay for (which sometimes may be nothing).
A lack of realistic expectations from employers is often the primary problem.
Although this is a site where the obvious answer is snv/emacs/vim/etc., the OP mentioned using UltraEdit and Notepad++, implying a Windows environment where these choices are not obvious, nor perhaps easy.
I transitioned (in part) from UltraEdit and SourceSafe to Vim and Subversion, and am happier having done so, but many of my colleagues are not ready to do the same - they went the Visual Studio and TFS route. To each his or her own.
For this audience, tools such as http://www.e-texteditor.com may make sense.
> Why do people insist that one size really does fit all?
Because people are lazy, and techies are no different. Many want to learn one technology, so every problem can be addressed with a minimum of intellectual effort. Look at any current whiz-bang buzzword tech, and you will see it is marketed as the solution to all your problems.
"Learn different languages for UI and data access. The hell you say!"
Then there are the little things that crop up over experienced usage - like the first time you try to take a MS SQL backup from one machine to another and end up perplexed for an hour. Or when you're 6 gig backup file won't copy from one machine to another without 3rd party software (really a windows issue, not SQL Specific). Experienced usage is the key term here. Every platform/environment has it's 'gotchas' - this is why there are still paid admin positions. The two examples above are easily avoided, if you know the proper procedures (and this concept is not a synonym for RTFM).
Slashdot Mirror
wow, i could write your 4000 lines of code in 3 days.... why does it take you a month?
Because there is a lot more to developing an app than writing code.
> Backing up a live database can be a bit tricky.
Seriously? If your database of choice is a chore to backup while live, you need to rethink your choice.
Full or incremental backups should be a trivial operation, with support for intra-backup change capture only a little more effort (log shipping, replication, etc.)
Of all the reasons to lose data, "Backups are hard!" should not be in the list.
Exactly how does the choice of OS make a difference in this case?
So true, many IT shops are located in or near the Twilight Zone.
IIRC, the equivalent is called "Windows Update"...
Funny thing I have noticed, in situations that pay overtime, there is rarely a significant amount of it. When Time = Money, managers quickly learn to plan projects accurately.
Oh it can be money all right. If you paid _actual_ market rates, based on real averages of people with similar experience, responsibilities, and geographic location, then you were on the right track.
However, companies who expect to get a (mythical) jack of all technologies, but pay sub-average rates will get only what they pay for (which sometimes may be nothing).
A lack of realistic expectations from employers is often the primary problem.
Wait a minute... outsourcing is now a valid reason for poor quality?
That and the _massive_ cost savings should make anyone who suggests it a candidate for CEO!
Although this is a site where the obvious answer is snv/emacs/vim/etc., the OP mentioned using UltraEdit and Notepad++, implying a Windows environment where these choices are not obvious, nor perhaps easy.
I transitioned (in part) from UltraEdit and SourceSafe to Vim and Subversion, and am happier having done so, but many of my colleagues are not ready to do the same - they went the Visual Studio and TFS route. To each his or her own.
For this audience, tools such as http://www.e-texteditor.com may make sense.
> Why do people insist that one size really does fit all?
Because people are lazy, and techies are no different. Many want to learn one technology, so every problem can be addressed with a minimum of intellectual effort. Look at any current whiz-bang buzzword tech, and you will see it is marketed as the solution to all your problems.
"Learn different languages for UI and data access. The hell you say!"