Keep on…

  • keep on ignoring requests coming from a QA team member;
    • keep on de-CCing QA on your bugs when said QA team member state that the fix is the wrong one, just stating that “it’s the wrong place open a new bug” when your solution was decided there;
    • keep on complaining if less than 1% of bugs filed, out of literally thousands lack a log file;
    • keep on asking me to not use the f-word because it makes it bad for you to be associated with Planet Gentoo (but on the other hand, feel no harm in being associated with people who repeatedly made Gentoo unusable for its users);
    • keep on spitting on me for pointing out that your unmask ideas are between reckless and totally stupid;
    • keep ignoring the bugs that are reported for your package;
    • keep bumping packages you don’t maintain, without looking into the further QA-related issues, and without declaring yourself the maintainer;
    • keep repeating the same mistakes and when asked to revise your attitude use the “but he did it as well” card.

Keep it up this way, then look back to see if there is QA at all.

17 thoughts on “Keep on…

  1. I know nothing about the dev in question, but I disagree with RealNC.Having bad developers can definitely be worse than no devs at all. If there are no devs, then there is hope for a better one to step up.I’d rather have the tree frozen until I can do something about it myself, than have it broken by someone else.

    Like

  2. Maybe you should reconsider your communication strategy.You yell at people and wonder why they then ignore you.You whine about issues where upstream and the maintainer agree that it’s the right way to do it, and then wonder when people tell you to choke on a cucumber.Every single point of your list of complaints goes back to you radiating negativity – everyone is stupid, everything sucks, I are teh greatestest. Maybe you should try not to be such an emo and say something positive once in a while … or stop writing all this negative stuff that makes some of us want to beat some sense into you.Just an idea. Not that I’d expect you to listen to advice, because you know better and we’re Dumas’es anyway.

    Like

  3. I have to agree with Someone’s post earlier. Spending the last couple of years reading your “oh poor me…” posts has made me re-think my use of Gentoo altogether. I once was quite adamant about using Gentoo for almost all server builds at several of my clients but now have shifted back to recommending more mainstream Linux distros. Personally, I still find Gentoo to be an awesome tool. However, the continual narcissistic rants on your part have soured me to the entire project. I come back from time to time to see if somehow you have either moved on or been kicked out but alas, it still has not happened. Please save us all the continued disappointment of listening to you and just move on to something else.

    Like

  4. I have to agree with Someone’s post earlier. Spending the last couple of years reading your “oh poor me…” posts has made me re-think my use of Gentoo altogether. I once was quite adamant about using Gentoo for almost all server builds at several of my clients but now have shifted back to recommending more mainstream Linux distros. Personally, I still find Gentoo to be an awesome tool. However, the continual narcissistic rants on your part have soured me to the entire project. I come back from time to time to see if somehow you have either moved on or been kicked out but alas, it still has not happened. Please save us all the continued disappointment of listening to you and just move on to something else.

    Like

  5. I agree with flameeyes,@someone#1The problem is not the negativity, but the fake positivity.Gentoo “stable” has so many real problems it’s not funny, and it seems strange that only flameeyes sees that.As a user, I feel that lately there are random version bumps everywhere without a second thought on Q/A. I end up fixing everything user-side.

    Like

  6. I too agree with flameeyes,Having stupid version bumps is very very wrong. “Devs” that do that shouldn’t have direct access to portage tree. I understand why Diego is mad sometimes. It’s because he is actually able to see the whole impact of those bad package bumps on tinderbox.@SomeoneYour inability to use your real internet nick but to hide behind “someone” gives your whole post ZERO VALUE.If you are one of the devs in question, please leave gentoo asap! We all will be much much happier without “devs” like you!I used the “devs” intentionally, because package-bumping is not what someone, that I call developer do.

    Like

  7. * keep on complaining complaining like a bitch and see if Gentoo is ever taken seriously.There is already the image that Gentoo is full of whiny teenagers, you’re not really helping debunk it. Devs should be able to solve problems internally; contact devrel. Washing dirty laundry in public for the sake of blog impressions is retarded. Sorry to see you go this way lately, I really enjoy your technical posts.

    Like

  8. Wrong way”Diego should work better on delivery the message, people receiving it should better take it and get a clue…”Good way”While Diego ideas from time to time are hindered by his rage, the issue he is posing is quite real and should require just a modicum more of care, everybody makes mistakes sooner or later…”Ok, the good way maybe is more the wordy way, still, Diego should keep himself cooler, people should listen to him.

    Like

  9. Diego,I follow your blog since some years now, and I see you’re getting more and more frustrated about the QA/Devs relationship. As a user with mostly “stable” gentoo, I think you’re right in this: “stable” is not that stable, and sometimes we have to fix things ourselves.Nevertheless, I think you’re yelling at the wrong people. Let me explain… Havis said earlier that some devs should not have access to the tree. There is some good sense in this, but why not push it further?Let’s have QA agree on EVERY package stabilisation. That way, the tinderbox would be even more useful and all ebuilds quality checks would be performed prior to stabilisation. The only drawback would be the longer time required for stabilisation. That’s why there is “unstable” packages as well, right?

    Like

  10. D’UH! Actually I don’t care _who_ said _what_ to _whom_ in particular. What pisses me off is people going personal all of a sudden, when there used to be mere technical problems to begin with.Stop. Right. There. Period.A story: I’ve been working in a small software company for little over three years now. Working on proprietary code won’t give you bonus for aesthetics most of the time, nor will it let you work on beautiful code unless you make it so. That’s technical. It turned out to let me pay my bills a bit more easily, though. That’s financial. So I achieve a compromise to make things work wrt. both aspects. That’s political. Due to lack of resources, the company tends to hire students for above-average salaries with the goal of retaining them not short but mid term, so they add value to the team, gain and bring knowledge, and help us get the job done in time. That’s economical. Most of the time, we pick us the folks who really add to the team, but once we hired a guy who made a decent impression at first. That’s in the human resources department. Later, he turned out to be unmotivated, incompetent, and unwilling to communicate at all. Instead of bothering to ask a question, he’d dwell in cluelessness, eventually making most of the problems he was to solve worse rather than better. Again, mostly technical. Once he started committing changes to the code which made methods do the opposite of what their name suggested, attitudes started to get personal since he made the impression not to be able to read, or give a damn, maybe even both. The project the team was working on was crucial for the persistence of a lot of jobs, if not the whole company, mind you. So, basically all the other team members were a bit on the edge about this young man. Still it was not desirable for anyone in the team to confront him on a personal level. We kept criticizing, trying to be as constructive as possible by any means, explaining things time and time again — as it turned out, to no avail, since he always claimed to understand, but when asked a provocative trick question his answer unveiled the truth — being the contrary. Try bringing someone into your team for like eight months, watching him tear your work apart, and you start to learn what frustration on a professional level feels like. That is emotional. Now try calling me (or anyone else, for that matter) an emo just for showing any emotions face-to-face, and I’ll go Black Metal ist Krieg! on your butt just for the taste of cliché, I dare you. Being serious again, we let go our most beloved fellow developer in the end — not due to behaving like a total fscktard while proving the contrary at the university, but for punching hours during which he coincidentally was seen walking around the city by the team lead. That’s the HR department, again. Personally I hold no grudge against the man, hell, I don’t even _know_ him, but after the show he pulled I can say I have neither the desire to _get_ to know him, nor can I have any kind of respect.Now if _anybody_ working on Gentoo is pulling off the same, that is, behaving in an incompetent manner first, continue being resilient to any learning process, then unable to handle constructive criticism, and finally going all personal — and by that, even start hitting beneath the belt line, before getting to know the victim of the childish attacks on a personaly level whatsoever — then I am luckily in no way obliged by professional boundaries to restrain my two middle fingers.Diego, don’t even try to expose that certain “someone”. Bet you know the rule about arguing with idiots. People who don’t even have the guts to show their face (or name for that matter) when pissing on other people’s blogs, don’t even deserve that level of attention. To consciously drop to their level for a moment, they can go take a dump for now, and come back later, none the wiser unfortunately. Now _that_ was emotional, personal, and most probably entirely incorrect.More or less sorry for the vocabulary, I strive to be a person where everybody gets what they deserve. That said, “Someone” is supposed to get his shit together, work on his personality and his communication skills, so in the future he can tell constructive criticism and personal blame apart. Whining is OK, for fsck’s sake, as long as it helps those doing actual work keep going despite all the frustration they feel. At least, the usual Flameeyes rant goes like “this issue is causing me trouble” and “that QA matter is getting on my nerves” and not “OMFG dev X is being a fscktard again” and “dev Y is acting out like a total drama queen, what a sissy”. Well, guess I just inadvertently decided to do the latter on “Someone”. If you’re still reading (suppose you’re not), next time you go all “Drama, Baby”, please use an avatar showing your actual self wearing a pink ballet dress. No offence intended, I am entirely ignorant about sexual orientation of my fellow humans, but _not_ about their behaviour.Now everyone, first and foremost myself, should tone things down a bit. Those technically involved shall find a forum to communicate on that level, and on that level ONLY, pretty please. Learn to play nice, everyone, and find the best solution there is. That may well be a bloody compromise for the time being, leaving the proper solution for later, but throwing dirt in every direction will get us damn nowhere.Secondly, Diego might decide to delete my comment due to “poor choice of words”, I can totally understand if he would rather not tolerate such language on what is still his blog.Last but not least, everyone should consider whether he would not rather choose a direct and private path of confrontation, instead of the public shitstorm we see every time anyone feels like someone else (sic ; ) is stepping on his toes.Time to come to an end for now. I’ll be back for further comments.Take it easy, everybody!

    Like

  11. To the various “somones”: I think you’re shooting the messenger. You should attack the problems not the people that make you aware of them or the way in which they do it. It’s about QA – not PR, stupid!

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s