|
W∴ Balboos wrote: Raises are very few and far between
I was less than amused to hear that no bonuses were being given out to employees in 2017, yet, there in a public record filing, is a $1.3M bonus for the CEO. Riiiight.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Hear I dance at the edge of the Soapbox: for all the big corportate tax break, very few regular employees saw any of it. Sure - a few big "news" items, like higher minimums at a few places (like Amazon) but that money, as usual, didn't trickle down. I only dare post this here as I'm not blaming either party for what corporate "leader" do: business as usual.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Marc Clifton wrote: But then I get back to smacking myself -- I know better. I should have taken the initiative to request code reviews. I should have utilized this really smart person's knowledge and skill better.
Probably no call for you to smack yourself. After all, would they have actually had time to do that? If they're any good, their dance card is probably already overflowing.
|
|
|
|
|
It really doesn't matter, companies always find a way with their business...or fold... or outsource the work to some other company that has the developers to handle such stuff.Or even throw it away.
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
|
Mycroft Holmes wrote: I don't believe it is the job of a senior developer to try and change the management teams priorities.
And yet they would ask me for suggestions on improving processes. All of which was shot down, and of course I'm wise and jaded enough to know that whenever I hear management say "we want to hear from YOU!" that it's really only a way for them to find out who the boat rockers and dissenters are.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Sympathy. It sounds so familiar, even the insurance part.
You do what you can, no regrets. They got their moneys worth.
Learn, move on, enjoy. You leave your legacy behind.
Best wishes.
|
|
|
|
|
Just accept it as part of life and work.
One could always strive for perfection, but there's always other people and lack of time coming in the way.
Reading your post and previous posts I can say that in my opinion you've done more than what could/should be expected.
|
|
|
|
|
Could be worse.
You could have done a good job, and get punished for it, because you're going against the status-quo. My current projects does that and it sucks.
Oh well, it's just one project. It either ends next year or I quit the job.
|
|
|
|
|
Make sure the db admin has your contact information and knows you'll be a reference for her so when she's looking to leave that sinking ship she has at least one reference for her next job search. Other than that, don't look back.
|
|
|
|
|
Tell them you'll be available for (remote) "support" ... at a reasonable rate, etc.
(I was on-call 2 weeks into my first job ... one survives.)
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Hi All,
Working on time critical project, all going well and then management. The last project I worked on escaped management interference and was delivered early and under budget (  ). So when I started on the upgrade I followed the same procedure as before, Test, find fault, tell the developer of the fault (to ensure they hadn't got to far out of the 'zone'), rasie ticket & fault is fixed everybody happy. Then my Boss is told by 'Management' to tell me she had complaints that I was disturbing the software dept. So I stop disturbing the software dept and am asked at the next stand up why I haven't been reporting faults, haven't I found any... So normal service resumes until said management type get involved again. I give up!
|
|
|
|
|
Doesn't your company have a bug tracking system that's available to developers ?
|
|
|
|
|
RickZeeland wrote: Doesn't your company have a bug tracking system that's available to developers ?
Yes, Management. Didn't you read his rant.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
|
So raising a ticket is already considered "bothering development" ? 
|
|
|
|
|
You are as lost as I am, I think this management person is either trying to prove to new overlords they are useful or trying to justify there existence...
|
|
|
|
|
glennPattonWork wrote: she had complaints that I was disturbing the software dept
Then please, please stop preventing everybody from doing their work.
Now that you mention it, it is the same here, we always get interrupted by customer contracts and customer requests and customer this and customer that. Do we really need customers ? They are such a nuisance, keep interfering...
modified 20-Nov-18 7:07am.
|
|
|
|
|
Customers are great, they don't know what they want but they want it NOW! 
|
|
|
|
|
glennPattonWork wrote: they want it NOW!
Wow! How have you managed to beat them down to such reasonable deadlines? Ours usually want it YESTERDAY at the latest. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Years ago, I worked in an office next to a sales person named Thelma, a beautiful blonde older lady who wasn't always there, if you catch my drift.
One Monday she dropped an awesome line.
She had a client on the speaker phone, going over a change order that he wanted to get done as fast as possible.
The conversation went something like this:
Thelma: So, when do you need this done?
Customer: I need this done yesterday!
Thelma: Well, I'm sorry, sir, but we're closed on Sundays!
|
|
|
|
|
Speaking for development, "Please bother us!" 
Like most developers, I'd much rather have someone in the company discover a problem than have a customer scream about it later. The former is far less personally embarrassing and painful. Oh, and yeah, its good for the company too
|
|
|
|
|
I know, I did development for many years before I became a tester. I only really became a tester as it was the only job on offer...  . Seem to be good at it, as I report issues before they get include in a build that is release...
|
|
|
|
|
Yeah, in many companies, its regrettably a difficult relationship between the development and QA teams. It should be entirely collaborative, but can (unfortunately) so easily become adversarial.
I think it most often arises when companies de-value the benefits of QA.
Regrettably, many companies have two cultures: the actual culture and the aspirational culture shared in "feel-good" presentations. In the aspirational culture, the company values QA and factors in time for developers to support it. In the actual culture, it is often the opposite.
Unfortunately, as developers, we often have almost no clear requirements prior to a task. We often find ourselves simultaneously developing both the requirements and the code. As a consequence, we often have nothing concrete to share with QA until after the code is completed.
Comically, we are frequently not allowed any time, even when the code is completed, to write up information/documentation. This leaves QA with inadequate information to do their job. And, perhaps even more worrying, leaves customers in a similar situation.
The problem is sometimes worsened by ill-advised methodologies that require QA to begin testing simultaneous with the process of coding. It is absolutely possible to design tests for something with clear requirements, before coding is completed. It is similarly possible to be "agile" and start coding with unclear requirements. It is not possible to do both. This is simply fallacious thinking.
Sometimes, this leads to friction between the development and QA teams, since we are given competing agendas by the company. This can result in development misdirecting frustration at QA and vice-versa. They are simply both put in a bad situation by their company.
My guess is that sort of disconnect between aspirational and actual company goals, for development and QA, will always exist. Its simply too seductive for companies to chase short term gains at the expense of long term success. Regrettably, team cohesion and morale are the predictable casualties of that approach.
|
|
|
|
|
I only worked for small firms that had a you build it, you test it policy. It is more fun to get the software look at and think if I was a user I would try this... The issue was there was no QA then it started to grow...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
