I've already seen this on the Internet when accessing a free site, they first showed me an ad and then i had to answer 3 questions about it before proceeding to the web site. I didn't mind it in that context because I was interested in the free web content (which turned out to be lame hairdos from the 80s, but oh well).
An independent contractor was NOT a big time suck, and I even had to file sales tax papers every month in Tennessee (something about I'm providing a product so I had to charge my client sales tax... what?!?). The biggest problem is if you aren't a responsible saver and don't set aside your quarterly income tax payments. I even paid less than I was supposed to and didn't get into any trouble, they figured out whatever penalties I had to pay and sent me a bill, never out of my ability to pay either. I don't have links to forms on hand, but it was easy and relatively painless for me to work as in independent contractor, even at only $25/hour back in the day... and I didn't go nuts on health insurance because I was single and pretty healthy (in fact, I skipped it altogether for a year just on principle but some don't let you have a lapse in coverage nowadays without going through a "pre-existing condition" review period so I wouldn't recommend it).
So, independent contractor is my recommendation to you, good luck! It's fun to get more money in your pocket... oh I miss those days sometimes... sigh...
I would wholeheartedly agree with dmorin. I think it's perfectly valid to have a development department in charge of their own "space". I've worked in that environment very successfully and at the satisfaction of both the development and IT groups. They stayed out of our way and we actually helped them with some of their problems.
I've also worked in an environment where the implementation group controlled everything (this was just when SMS came out, I still have the shakes), your computer was set up for you, they periodically came around and uninstalled screen savers and whatnot... but imagine monday morning when you come in to work and your computer gets the BSOD because some nitwit from tech support messed up your registry when ensuring your computer was "compliant" with corporate policies, or they screwed up your file links and now gcc can't find your mysql header files because you had a "non-standard" installation... Occasionally they would allow us to make the necessary changes ourselves if we were buddies with the technician -- let's face it, I feel more comfortable in my abilities to maintain my computer, I use the thing every day for crying out loud!
I can understand the IT department's headaches from users who screw up their machines, but developers are typically smarter than the average Outlook user (hopefully??) and can manage their own computers just fine. Computers as company property and subject to coroporate/IT policies is one thing... coding with my wrist chained to the chair is another.
...I do think we'll see XP sales exceeding Windows 98SE, ME, and Win2k combined, at least within the next 6 months.
I disagree. Companies running NT looking for an upgrade would most likely consider Windows 2k over anything else as it is the likely replacement for NT. Windows XP, from what I've seen of it and their marketing campaign, is most likely best served on the home user's desktop.
Of course, I don't have my pulse on the OS needs of the nation... (grin)
Negligence? So, does that mean that if I have a fenced in yard, and you trespass and slip on my kids' ice rink in my *fenced-in* back yard, that I am negligent? Why is it my responsibility to prevent you from hurting yourself? There is a fine line between negligence and blame-throwing and too often it is crossed.
But that is off the topic at hand...
I do, however, feel that Microsoft is responsible for the security issues with their software. I, for one, am thankful that the hackers force MS to patch their stuff, although it is a nuisance and it is destructive.
It is NOT the government's responsibility to provide an environment where we don't have to write efficient, secure code. Be responsible for yourself and for your product.
Still, after 15 years no editor comes close to emacs. B.t.w. the last 10 years or so (since version 20) emacs has a menu bar that you can use instead of keystrokes for all but the most basic things (which you learn in the built-in tutorial in 15 minutes); this enables you to gradually learn the keys for more complex things.
Also you can execute most functions with the function name (M-x browse-url for example) and while you do so emacs tells you which shortcut keystroke exists so after 3 times you know what key you might use (unless you're senile).
I echo those sentiments 100%! The learning curve for emacs is much smaller than vi because you have those menus and don't have to reference a manual for the keystrokes. Unfortunately, I always manage to find myself in a situation where I have to know minimal vi to edit some file during a demo or something where emacs is not available on the machine. It tried them both and stuck with emacs because I became proficient enough in a short amount of time.
Okay, so you can argue that I'm a dumb*ss and can't learn vi. (grin)
We argue because it's fun and it gives us something to rally around, it's all harmless and entertaining. I worked at a company where I was one of maybe 5 at the most who used emacs out of 20+ developers and we argued constantly about it, mostly just to get people's blood flowing.
Besides, it's more entertaining than listening to people b*tch about Microsoft. (smile)
Slashdot Mirror
I've already seen this on the Internet when accessing a free site, they first showed me an ad and then i had to answer 3 questions about it before proceeding to the web site. I didn't mind it in that context because I was interested in the free web content (which turned out to be lame hairdos from the 80s, but oh well).
By your own account, he's still owed the 12oz difference between 6-8oz cups (48oz) and 12-5oz cups (60oz).
Ha! They are serving it up to you, the user!!! Enjoy that pigeon 'poodoo' ;-)
An independent contractor was NOT a big time suck, and I even had to file sales tax papers every month in Tennessee (something about I'm providing a product so I had to charge my client sales tax... what?!?). The biggest problem is if you aren't a responsible saver and don't set aside your quarterly income tax payments. I even paid less than I was supposed to and didn't get into any trouble, they figured out whatever penalties I had to pay and sent me a bill, never out of my ability to pay either. I don't have links to forms on hand, but it was easy and relatively painless for me to work as in independent contractor, even at only $25/hour back in the day... and I didn't go nuts on health insurance because I was single and pretty healthy (in fact, I skipped it altogether for a year just on principle but some don't let you have a lapse in coverage nowadays without going through a "pre-existing condition" review period so I wouldn't recommend it).
So, independent contractor is my recommendation to you, good luck! It's fun to get more money in your pocket... oh I miss those days sometimes... sigh...
I would wholeheartedly agree with dmorin. I think it's perfectly valid to have a development department in charge of their own "space". I've worked in that environment very successfully and at the satisfaction of both the development and IT groups. They stayed out of our way and we actually helped them with some of their problems.
I've also worked in an environment where the implementation group controlled everything (this was just when SMS came out, I still have the shakes), your computer was set up for you, they periodically came around and uninstalled screen savers and whatnot... but imagine monday morning when you come in to work and your computer gets the BSOD because some nitwit from tech support messed up your registry when ensuring your computer was "compliant" with corporate policies, or they screwed up your file links and now gcc can't find your mysql header files because you had a "non-standard" installation... Occasionally they would allow us to make the necessary changes ourselves if we were buddies with the technician -- let's face it, I feel more comfortable in my abilities to maintain my computer, I use the thing every day for crying out loud!
I can understand the IT department's headaches from users who screw up their machines, but developers are typically smarter than the average Outlook user (hopefully??) and can manage their own computers just fine. Computers as company property and subject to coroporate/IT policies is one thing... coding with my wrist chained to the chair is another.
Freedom is not for the ignorant.
...I do think we'll see XP sales exceeding Windows 98SE, ME, and Win2k combined, at least within the next 6 months.
I disagree. Companies running NT looking for an upgrade would most likely consider Windows 2k over anything else as it is the likely replacement for NT. Windows XP, from what I've seen of it and their marketing campaign, is most likely best served on the home user's desktop.
Of course, I don't have my pulse on the OS needs of the nation... (grin)
No kidding, I'd hate to get a pacemaker made "the Microsoft way". (grin)
Negligence? So, does that mean that if I have a fenced in yard, and you trespass and slip on my kids' ice rink in my *fenced-in* back yard, that I am negligent? Why is it my responsibility to prevent you from hurting yourself? There is a fine line between negligence and blame-throwing and too often it is crossed.
But that is off the topic at hand...
I do, however, feel that Microsoft is responsible for the security issues with their software. I, for one, am thankful that the hackers force MS to patch their stuff, although it is a nuisance and it is destructive.
It is NOT the government's responsibility to provide an environment where we don't have to write efficient, secure code. Be responsible for yourself and for your product.
Still, after 15 years no editor comes close to emacs. B.t.w. the last 10 years or so (since version 20) emacs has a menu bar that you can use instead of keystrokes for all but the most basic things (which you learn in the built-in tutorial in 15 minutes); this enables you to gradually learn the keys for more complex things.
Also you can execute most functions with the function name (M-x browse-url for example) and while you do so emacs tells you which shortcut keystroke exists so after 3 times you know what key you might use (unless you're senile).
I echo those sentiments 100%! The learning curve for emacs is much smaller than vi because you have those menus and don't have to reference a manual for the keystrokes. Unfortunately, I always manage to find myself in a situation where I have to know minimal vi to edit some file during a demo or something where emacs is not available on the machine. It tried them both and stuck with emacs because I became proficient enough in a short amount of time.
Okay, so you can argue that I'm a dumb*ss and can't learn vi. (grin)
We argue because it's fun and it gives us something to rally around, it's all harmless and entertaining. I worked at a company where I was one of maybe 5 at the most who used emacs out of 20+ developers and we argued constantly about it, mostly just to get people's blood flowing.
Besides, it's more entertaining than listening to people b*tch about Microsoft. (smile)
e-Hitler, lmao! i have no desire for XP either.