3 ms·

Yeah I recently dumped my .net job and ran for the hills. Now I've got my slices /etc/host'd, and I can just sshfs in and gvim around to my hearts delight. (I

by kleevr 17y ago

Yeah I recently dumped my .net job and ran for the hills. Now I've got my slices /etc/host'd, and I can just sshfs in and gvim around to my hearts delight. (I actually got reprimanded for using gvim at the last job, luckily we struck a compromise with vs+viemu.)

DrJokepu 17y ago
Why would anyone at your job care about the editor you're using? Sounds like unnecessary micromanagement to me. Why I can't understand why would you ever pick vi over VS, but if they had a problem with your choice of IDE then you were right to leave, sounds like an awful place to work at.
- lnguyen 17y ago
  It shouldn't matter up until the point where the results of your customized development environment cannot be (readily) replicated. Part of the reason for standardization is to help avoid "it works for me"-type issues. This isn't an issue for independent development efforts but it is critical in team and enterprise settings.
- kleevr 17y ago
  I was learning C# (had just come from Java/Eclipse land), and I was using the command-line compiler just to get comfortable and learn some in's and out's. I was the first CS programmer they hired (I was still in school), they were crewed up with a lot of nice guy MIS's... it was funny when they hired another CS guy and he started doing the same things I did when I started, and getting in minor trouble with management. They also wouldn't let us use ANY scripting languages for anything... everything should be compiled code based on "Principal", it runs faster and is "strongly typed" which is philosophically "better" I was told without a reason. Never mind that most of the other coders still used strings for everything (especially numbers), and 50%+ of the code base was XML serializers/deserializers. (Also the web apps were hideous,... WebForms what a shitty set of web-dev metaphors.) I also got in trouble for wasting my time writing unit tests, we were an "agile" company with no time for tests. Yeah, once I had a plan and some cash, I got the fuck out of dodge. (ultimately, while still there, I ended up in vs+viemu, which I found fairly productive, and would highly recommend it to any VS code slingers)

by kleevr 17y ago

DrJokepu 17y ago

Why would anyone at your job care about the editor you're using? Sounds like unnecessary micromanagement to me. Why I can't understand why would you ever pick vi over VS, but if they had a problem with your choice of IDE then you were right to leave, sounds like an awful place to work at.

lnguyen 17y ago
It shouldn't matter up until the point where the results of your customized development environment cannot be (readily) replicated. Part of the reason for standardization is to help avoid "it works for me"-type issues. This isn't an issue for independent development efforts but it is critical in team and enterprise settings.
kleevr 17y ago
I was learning C# (had just come from Java/Eclipse land), and I was using the command-line compiler just to get comfortable and learn some in's and out's. I was the first CS programmer they hired (I was still in school), they were crewed up with a lot of nice guy MIS's... it was funny when they hired another CS guy and he started doing the same things I did when I started, and getting in minor trouble with management. They also wouldn't let us use ANY scripting languages for anything... everything should be compiled code based on "Principal", it runs faster and is "strongly typed" which is philosophically "better" I was told without a reason. Never mind that most of the other coders still used strings for everything (especially numbers), and 50%+ of the code base was XML serializers/deserializers. (Also the web apps were hideous,... WebForms what a shitty set of web-dev metaphors.) I also got in trouble for wasting my time writing unit tests, we were an "agile" company with no time for tests. Yeah, once I had a plan and some cash, I got the fuck out of dodge. (ultimately, while still there, I ended up in vs+viemu, which I found fairly productive, and would highly recommend it to any VS code slingers)