Jump to content
Kerberos

Single most scariest moment of my life.

Recommended Posts

1UnhlUb.png

 

I have never seen a VAC before. And I most certainly do not cheat at TF2... Kinda defeats the whole purpose of me being an admin here.

 

I shit my self when I got this.

 

Anyone else getting this/got this? 

  • Upvote 1

Share this post


Link to post
Share on other sites

What server where you on when this happened?

Share this post


Link to post
Share on other sites

Oh this happened to me, verify game cache, restart, blahblahblah happens a lot to people laugh.png

Share this post


Link to post
Share on other sites

I saw other complaints about these sort of issues after one of the more recent TF2 updates.

 

Just valve testing everything real well as always.

  • Upvote 4

Share this post


Link to post
Share on other sites

I saw other complaints about these sort of issues after one of the more recent TF2 updates.

 

Just valve testing everything real well as always.

 

Contrary to popular belief, things are generally well tested! Most bugs in software are known to the QA department at times of release. At my last company I could have stood upside down naked with the bugs written on my body in glowing inks and they still would have shipped to meet deadlines -.-

  • Upvote 1

Share this post


Link to post
Share on other sites

Contrary to popular belief, things are generally well tested! Most bugs in software are known to the QA department at times of release. At my last company I could have stood upside down naked with the bugs written on my body in glowing inks and they still would have shipped to meet deadlines -.-

Ehem. If you would have done that, it wouldn't have surprised me if they'd completely ignore the bugs...

Also, on topic - if this is the scariest moment in your life, i envy you... ph34r.png

  • Upvote 2

Share this post


Link to post
Share on other sites

I got that issue when I installed an new anti-virus. It blocked as "Suspicious Activity." lol

Share this post


Link to post
Share on other sites

Contrary to popular belief, things are generally well tested! Most bugs in software are known to the QA department at times of release. At my last company I could have stood upside down naked with the bugs written on my body in glowing inks and they still would have shipped to meet deadlines -.-

>Valve

>Well tested

130891161175.jpg

  • Upvote 2

Share this post


Link to post
Share on other sites

>Valve

>Well tested

130891161175.jpg

Considering I've more experience in this than you, yes, it is in my opinion. The implication that valve should run exhaustive testing is a really naive notion. They will never pick up every bug.

Share this post


Link to post
Share on other sites

Considering I've more experience in this than you, yes, it is in my opinion. The implication that valve should run exhaustive testing is a really naive notion. They will never pick up every bug.

I've been playing Valve games for years. I don't care how efficient their QA department is (in reality, it doesn't exist), but the end result is that their games are filled with bugs - and not only they are filled with bugs for a few days after a patch is released (which is to be expected), a good amount of bugs persists for several years. I don't expect of them to pick up every bug, but when a bug has been in the game for years, and is well known and documented by the community, they sould at least take some time and try to release a patch which won't break every server in existence. You can't explain to me that a small developer like Mojang which has 7 developers working on the most successful PC game of all time can make a more complex product with less bugs than a developer like Valve whose "people" page requires an entire alphabet of links on the sidebar.

Valve also has no QA department (there are actually no departments in Valve at all). People do what they want to do, and noone does QA. Therefore Valve's QA is shit.

  • Upvote 1

Share this post


Link to post
Share on other sites

I've been playing Valve games for years. I don't care how efficient their QA department is (in reality, it doesn't exist), but the end result is that their games are filled with bugs - and not only they are filled with bugs for a few days after a patch is released (which is to be expected), a good amount of bugs persists for several years. I don't expect of them to pick up every bug, but when a bug has been in the game for years, and is well known and documented by the community, they sould at least take some time and try to release a patch which won't break every server in existence. You can't explain to me that a small developer like Mojang which has 7 developers working on the most successful PC game of all time can make a more complex product with less bugs than a developer like Valve whose "people" page requires an entire alphabet of links on the sidebar.

Valve also has no QA department (there are actually no departments in Valve at all). People do what they want to do, and noone does QA. Therefore Valve's QA is shit.

 

You realise its much easier to do QA in smaller companies yes? :)

 

I've worked on products with bugs that were known about since before I was born - the length of time a bug is in a product has zero baring on the requirement to fix it. 

  • Upvote 1

Share this post


Link to post
Share on other sites

1UnhlUb.png

 

I have never seen a VAC before. And I most certainly do not cheat at TF2... Kinda defeats the whole purpose of me being an admin here.

 

I shit my self when I got this.

 

Anyone else getting this/got this? 

 

 

He hacks. Please ban, look up alts.

  • Upvote 1

Share this post


Link to post
Share on other sites

He hacks. Please ban, look up alts.

Well, as we're looking up alts...

  • Upvote 4

Share this post


Link to post
Share on other sites

The length of time a bug is in a product has zero baring on the requirement to fix it. 

 

True dat.  Commercial experience is an eye opener.

Share this post


Link to post
Share on other sites

True dat.  Commercial experience is an eye opener.

It's a matter of pride to fix it, though.

I've got a complete list of bugs in our software, with estimated time to fix it. Whenever i got the time, i fix it. So far, i never had anything longer in the software than 1 year.

<.<

Unless it's a feature, and not a "bug" because the customer thinks so.

"Why is this font not dark blue? Fix this bug asap!!!!!!"

u w0t m8? fuggoff....

  • Upvote 2

Share this post


Link to post
Share on other sites

It's a matter of pride to fix it, though.

I've got a complete list of bugs in our software, with estimated time to fix it. Whenever i got the time, i fix it. So far, i never had anything longer in the software than 1 year.

<.<

Unless it's a feature, and not a "bug" because the customer thinks so.

"Why is this font not dark blue? Fix this bug asap!!!!!!"

u w0t m8? fuggoff....

 

Yeah I know what you are saying....I suppose it depends how you work.  We worked using SCRUM and Agile and so the product owner decided what he spent his "points" on, we just estimated stuff..sometimes we got to say "hey look this has kicked around a while and we want to fix it as it's a quality issue and would please end users"...I suppose it depends on the team/company though.  Valve might have a flat structure but there is an underlying network of power players (according to that girl who relatively recently left from their hardware team at any rate).

Share this post


Link to post
Share on other sites

Yeah I know what you are saying....I suppose it depends how you work.  We worked using SCRUM and Agile and so the product owner decided what he spent his "points" on, we just estimated stuff..sometimes we got to say "hey look this has kicked around a while and we want to fix it as it's a quality issue and would please end users"...I suppose it depends on the team/company though.  Valve might have a flat structure but there is an underlying network of power players (according to that girl who relatively recently left from their hardware team at any rate).

 

We work on scrum, but it's purely based on what the customer pays for. Prime example, I raised 67 bugs with one product, 4 got fixed cos they were the ones the customer paid to get fixed. Doesn't make me bad at QA if a product goes out the door with 63 bugs in it. 

 

Contrary to popular belief QA has zero baring on if a product gets shipped or not. We just report what doesnt work, it's a project management choice as to whether to ship or not. 99% of the time a product will ship regardless of known bugs purely due to deadlines or money running out. 

Edited by Domino
  • Upvote 1

Share this post


Link to post
Share on other sites

Yeah I know what you are saying....I suppose it depends how you work.  We worked using SCRUM and Agile and so the product owner decided what he spent his "points" on, we just estimated stuff..sometimes we got to say "hey look this has kicked around a while and we want to fix it as it's a quality issue and would please end users"...I suppose it depends on the team/company though.  Valve might have a flat structure but there is an underlying network of power players (according to that girl who relatively recently left from their hardware team at any rate).

Well, yeah. it's easier when you "only have one product" and don't do much on customer demand.

 

We work on scrum, but it's purely based on what the customer pays for. Prime example, I raised 67 bugs with one product, 4 got fixed cos they were the ones the customer paid to get fixed. Doesn't make me bad at QA if a product goes out the door with 63 bugs in it. 

 

Contrary to popular belief QA has zero baring on if a product gets shipped or not. We just report what doesnt work, it's a project management choice as to whether to ship or not. 99% of the time a product will ship regardless of known bugs purely due to deadlines or money running out. 

Oh yes. "But boss, this was just the prototype, this is in no way a fully functional version, and surely not bug free!" ~ "I tested it. It does what it should." ~ "Uh... but... yeah... if you think so..."

*sighs*

Then again, Valve doesn't have a boss who tells them when it's ready for shipment. They take pride in that.

Share this post


Link to post
Share on other sites

We work on scrum, but it's purely based on what the customer pays for. Prime example, I raised 67 bugs with one product, 4 got fixed cos they were the ones the customer paid to get fixed. Doesn't make me bad at QA if a product goes out the door with 63 bugs in it. 

 

Contrary to popular belief QA has zero baring on if a product gets shipped or not. We just report what doesnt work, it's a project management choice as to whether to ship or not. 99% of the time a product will ship regardless of known bugs purely due to deadlines or money running out. 

 

Spot on, you're just there to find stuff...obviously sales and marketing won't find that sexy though...bar stewards xD

  • Upvote 1

Share this post


Link to post
Share on other sites

Spot on, you're just there to find stuff...obviously sales and marketing won't find that sexy though...bar stewards xD

 

Marketting people are the biggest load of knobs going XD

  • Upvote 2

Share this post


Link to post
Share on other sites

Marketting people are the biggest load of knobs going XD

Amen to that, sister.

  • Upvote 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...