Reputation: 14 Tradesman
- Active Posts:
- 44 (0.05 per day)
- 30-December 11
- Profile Views:
- Last Active:
- Jul 21 2012 10:07 AM
- Dream Kudos:
Posts I've Made
Posted 11 Jul 2012We never know when our direct supervisor might turn wicked. And we may never figure out the reason. It can be envy, or the need for a scapegoat, or who knows what.
My supervisor was not afraid to lie about it me, and he lied a lot. He wanted his boss to think I was dumb and useless.
He worked hard at getting rid of me, and I think he had planned it 2 years before. It did not matter how nice and agreeable I was, it did not matter how much I learned or improved my work.
I got better, and my performance reviews got worse.
It was like going to work in a mine field every day, never knowing what stupid excuse my boss would find for trashing me.
He had me half convinced that I am no good at programming and too old to learn.
Posted 10 Jul 2012
Quotesurvive there without too much misery.
I knew where to assert myself to not fall into the negative pit of the last place...
Ok, that's what I want to know. How to not fall into anything negative. The main thing is, I think, try to do a good job. But is that enough? Someone told me I have to bake cookies and bring them to the office, but that just is not me.
Posted 10 Jul 2012Yes I certainly see what you mean toq. I am not expecting to love any job. What I want to do is survive there without too much misery. I am not looking for the secret of life, just some tips on how to make a good impression at the beginning of a new job.
I plan on switching to freelance in a couple of years anyway. I want to survive at this job for 2 years. In the past year at the old job, I hoped I would get killed in a car accident on the way to work on Monday mornings.
The old job was ok, or at least not a nightmare, for 10 years. That's all I am looking for.
Posted 1 May 2012The only editor I used, for years, was VIM, because I felt that's the only way it could become second nature.
First thing I do after any fresh install is remove the alias from vi to point to vim, & replace it with a link from vi to /usr/local/bin/vi or where ever it's installed. I completely agree. You work with what's efficient. Though vi may not seem efficient to others, it's saved my ass more times than I really care to admit. When something doesn't boot right, & you get that minimal boot for maintenance, yeah. I find myself editing the fstab with vi for say a disk failure, or something dependent. Plus network connections, & so on.
I think it is good to know vi/vim, and it takes practice to learn them. That's why I used only vim for several years, even though other editors may be easier. Vi is always there on any unix system, and it starts up instantly. And you can make it into your one IDE by customizing as much as you want.
i use a different editor most of the time now, because my boss told me to. I don't know why, but I had to mindlessly obey. But there are still plenty of times when I have to ssh to a remote server and vi a file. So I'm glad I don't have to look up the commands.
Posted 30 Apr 2012I'm just wondering...considering the amount of effort it takes to successfully contribute to a project, do most experienced, active-in-the-community programmers actually do it after they come home from their full-time job?
from what I read about Linux development, the vast majority of work is done as part of someone's job.
I am using an open source library in the project I am doing at my job. I found some bugs in the library so I fixed them, while I was at work. That is probably very common, because any time you use an open source library for your job you might find bugs, or things you want to improve. If someone is contributing to open source at home, just for fun, then I guess they are working on their own project, rather than helping to fix someone else's.
- Member Title:
- New D.I.C Head
- Age Unknown
- Birthday Unknown
searcher920 hasn't added any friends yet.