These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Note on some broken CREST things

First post First post
Author
Katarina Jayne
Doomheim
#61 - 2016-06-17 16:13:39 UTC
CCP FoxFour wrote:
Just a quick note on some known CREST issues:

  • Any killmail that involves a faction ID, especially relevant for FW kills since they all have a faction, are broken
  • Setting waypoints only works 1 in 1 million times
  • Same with opening market details
  • Same with opening a specific contract


I wanted to get this fixed today, Thursday, but Friday is a day off here in Iceland and we don't like to do deployments on Fridays. Since tomorrow is a day off today is essentially a Friday since no one is in tomorrow. because of that these fixes are all scheduled to go out on Tuesday the 21st.


In other words you have no idea what is wrong and are buying time to figure it out.... Because I find it hard to believe you have a fix but won't deploy it despite Eve as always peeking in numbers and activity over the weekend and you expect everyone to believe the "day off" scenario... This is Eve... There are no days off!!!
ISD Buldath
#62 - 2016-06-17 16:35:30 UTC
This Popcorn Is Really Buttery.

~ISD Buldath

Instructor King of the Forums! Knight of the General Discussion

Support, Training and Resources Division

Interstellar Services Department

I do not respond to EVE-Mails regarding forum moderation.

Ayuren Aakiwa
Shadow Legion X
Seriously Suspicious
#63 - 2016-06-17 16:55:47 UTC
ISD Buldath wrote:
This Popcorn Is Really Buttery.

Salty too šŸ˜€
Michael Galazy
The Scope
Gallente Federation
#64 - 2016-06-17 19:23:28 UTC
Lol Thanks Eve! Was wanting excuse to check out Elite Dangerous!!! Maybe their Devs won't wait 5 days to implement a fix!!
Squizz Caphinator
The Wormhole Police
#65 - 2016-06-17 19:33:16 UTC
Michael Galazy wrote:
Lol Thanks Eve! Was wanting excuse to check out Elite Dangerous!!! Maybe their Devs won't wait 5 days to implement a fix!!


Roll
Maybe you should pay attention to E:D news and how quickly their devs respond to outstanding issues.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com

Fivenake
University of Caille
Gallente Federation
#66 - 2016-06-17 19:34:35 UTC
I feel that this topic has only confirmed that people know little to nothing about proper release management.

I worked on a release management team for one of the largest US (and most hated) telecom company. People have no idea how much is affected by a simple push. My team specifically dealt with set top boxes. Change control boards for some people are once a week, our CCB was once a day.

I don't care who you are pre-prod environments are never exactly built like prod. You don't have an insane amount of users connecting, not including other tidbits in the mix of it all.

And to break it down Barney style how we did release management, it went like this (and were still hated for not being up 100% of the time).

Code gets developed and pushed during a sprint (we use agile), then it's released to the thousands of boxes in the home offices, my building had like 30 floors and that wasn't even HQ, HQ is the tallest building in Philly. We had numerous boxes and tvs on each floor and they were all connected running new versions constantly, we measured random resets and everything under the sun, then we enter metrics review. After metrics were good we moved to beta which was employee only boxes who signed up for beta builds. Once again we gather metrics on metrics on metrics.

After all that testing you come to the board and say hey we wanna release build x.xx on this day to 1% GA. 1% is millions of customers so not breaking stuff is really important and after you get approved you release incrementally. 1-10-50-100. Rinse and repeat for new code being pushed. WE NEVER RELEASED CODE ON THURSDAYS because the box picked up the new code at 3am est Friday (which is why the box asks you to reset at 3am). That way if poop hits the fan because prod environments aren't easy and get moody you aren't running around to have people rollback versions.

So relax and let the Devs and CCP do their jobs, you want rushed code and bad patch management go play an EA game on launch then come here and complain. Until then sit your little behind down and be patient, new Eden isn't going anywhere anytime soon.

Change and release management has a process that spans days for a reason, metrics are in place for a reason. Suck it up.
Ohno no Borrox
xX-Crusader-Xx
Tactical Narcotics Team
#67 - 2016-06-17 20:40:07 UTC
Fivenake wrote:


So relax and let the Devs and CCP do their jobs, you want rushed code and bad patch management go play an EA game on launch then come here and complain. Until then sit your little behind down and be patient, new Eden isn't going anywhere anytime soon.

.


Would you buy a car that operated like that. Just because its endemic does not mean we should accept it. Otherwise slavery would still
be a thing. So looks like we're just getting bad code, that is being managed well - result!
CCP FoxFour
C C P
C C P Alliance
#68 - 2016-06-17 20:43:22 UTC
Ohno no Borrox wrote:
Fivenake wrote:


So relax and let the Devs and CCP do their jobs, you want rushed code and bad patch management go play an EA game on launch then come here and complain. Until then sit your little behind down and be patient, new Eden isn't going anywhere anytime soon.

.


Would you buy a car that operated like that. Just because its endemic does not mean we should accept it. Otherwise slavery would still
be a thing. So looks like we're just getting bad code, that is being managed well - result!


Oh wow! This thread just got to some new highs that I NEVER would have thought possible. EVE development just got related to slavery and NOT for over working the employees but for under working them. My god... this thread is amazing. :D

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Will Gauss
TerminalDogma
Lucky Starbase Syndicate
#69 - 2016-06-17 20:56:06 UTC
Katarina Jayne wrote:
CCP FoxFour wrote:
Just a quick note on some known CREST issues:

  • Any killmail that involves a faction ID, especially relevant for FW kills since they all have a faction, are broken
  • Setting waypoints only works 1 in 1 million times
  • Same with opening market details
  • Same with opening a specific contract


I wanted to get this fixed today, Thursday, but Friday is a day off here in Iceland and we don't like to do deployments on Fridays. Since tomorrow is a day off today is essentially a Friday since no one is in tomorrow. because of that these fixes are all scheduled to go out on Tuesday the 21st.


In other words you have no idea what is wrong and are buying time to figure it out.... Because I find it hard to believe you have a fix but won't deploy it despite Eve as always peeking in numbers and activity over the weekend and you expect everyone to believe the "day off" scenario... This is Eve... There are no days off!!!

Readonly Fridays, go look it up. No matter how broken your systems are, deploying a fix on Friday is courting worse disaster.

You do not EVER EVER EVER deploy shortly before time you're not going to be there, whether due to your obligation to be somewhere else or a company's obligation to not have you there.
CCP FoxFour
C C P
C C P Alliance
#70 - 2016-06-17 21:27:30 UTC
Ix Method wrote:
CCP FoxFour wrote:
CCP Bartender

...

Who knew I could love CCP more?


He is a pretty cool dude who is going to take great care of all you creeping, weird, and wacky people along with CCP Tellus and CCP SnowedIn. :D

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

CCP FoxFour
C C P
C C P Alliance
#71 - 2016-06-17 21:31:58 UTC
Ayuren Aakiwa wrote:
ISD Buldath wrote:
This Popcorn Is Really Buttery.

Salty too šŸ˜€


nom nom nom

[img]https://media.giphy.com/media/3oGRFKLA7T6OpgYadO/giphy.gif[/img]

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

CCP FoxFour
C C P
C C P Alliance
#72 - 2016-06-17 21:48:47 UTC
Katarina Jayne wrote:
CCP FoxFour wrote:
Just a quick note on some known CREST issues:

  • Any killmail that involves a faction ID, especially relevant for FW kills since they all have a faction, are broken
  • Setting waypoints only works 1 in 1 million times
  • Same with opening market details
  • Same with opening a specific contract


I wanted to get this fixed today, Thursday, but Friday is a day off here in Iceland and we don't like to do deployments on Fridays. Since tomorrow is a day off today is essentially a Friday since no one is in tomorrow. because of that these fixes are all scheduled to go out on Tuesday the 21st.


In other words you have no idea what is wrong and are buying time to figure it out.... Because I find it hard to believe you have a fix but won't deploy it despite Eve as always peeking in numbers and activity over the weekend and you expect everyone to believe the "day off" scenario... This is Eve... There are no days off!!!


I mean... OK. I cannot force you to believe things. Keep in mind however that this is a non-critical service and if you find killmails, which still work in the client and just not via the API in about 1% of the cases, to be critical I highly recommend reconsidering your priorities.

Anyways, off to scan some more wormholes and watch The Do Over.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

MachineOfLovingGrace
V0LTA
OnlyFleets.
#73 - 2016-06-17 22:08:45 UTC
CCP FoxFour wrote:
We have a growing number of automated tests. These range from testing if the server starts to regular python unit tests. The art department also has a bunch of tests they run as well for things like performance testing so we can see if performance changes over time. Anyways, point is those are all automated.

We then also have a large number of automated build jobs that monitor specific files and run builds if those files change and check in the resulting artefacts.

Beyond that we than have a daily build job that runs every day at 22:00 for each branch. This can also be triggered manually when desired. For example during the day when we want to update Sisi with some changes from the morning we will run the build and deploy that.

As for deploying it really depends on the server. All our smaller test servers we can deploy updated pretty much with a couple of clicks. For larger test servers such as Sisi this takes a little more effort. Usually a manual shut down, open special web page and upload build, click deploy build, run any database updates, and click the start cluster button.

TQ is a completely different beast that unfortunately is stuck a bit in the past and has a fair bit of manual steps for deploying to. Generally requires a few people from ops, at least a DBA, and preferably some others on hand.

That is all for the EVE sol/proxy/client code. We have a growing number of other services (image server, SSO, VGS, paparazzi, NGINX servers, sphinx, etc.) that are all built and deployed differently. :)


Sounds surprisingly close to our setup, and we do nothing like eve, hehe. I guess you have all sorts of update textures/shaders -> render new icons -> update resources chains and that, I can only image the size of your repositories.
CCP FoxFour
C C P
C C P Alliance
#74 - 2016-06-17 22:15:31 UTC
MachineOfLovingGrace wrote:
CCP FoxFour wrote:
We have a growing number of automated tests. These range from testing if the server starts to regular python unit tests. The art department also has a bunch of tests they run as well for things like performance testing so we can see if performance changes over time. Anyways, point is those are all automated.

We then also have a large number of automated build jobs that monitor specific files and run builds if those files change and check in the resulting artefacts.

Beyond that we than have a daily build job that runs every day at 22:00 for each branch. This can also be triggered manually when desired. For example during the day when we want to update Sisi with some changes from the morning we will run the build and deploy that.

As for deploying it really depends on the server. All our smaller test servers we can deploy updated pretty much with a couple of clicks. For larger test servers such as Sisi this takes a little more effort. Usually a manual shut down, open special web page and upload build, click deploy build, run any database updates, and click the start cluster button.

TQ is a completely different beast that unfortunately is stuck a bit in the past and has a fair bit of manual steps for deploying to. Generally requires a few people from ops, at least a DBA, and preferably some others on hand.

That is all for the EVE sol/proxy/client code. We have a growing number of other services (image server, SSO, VGS, paparazzi, NGINX servers, sphinx, etc.) that are all built and deployed differently. :)


Sounds surprisingly close to our setup, and we do nothing like eve, hehe. I guess you have all sorts of update textures/shaders -> render new icons -> update resources chains and that, I can only image the size of your repositories.


Oh god yea. I have never really touched it but the art team has a whole publishing pipeline, image rendering, and all sorts of other things. :)

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

FearlessLittleToaster
Federal Navy Academy
Gallente Federation
#75 - 2016-06-17 23:25:40 UTC
Hello this thread! I gotta say this is amazing to read. Also it provoked me into having strong opinions, and since I firmly believe everyone is entitled to my opinion on the internet I’m going to put it here!

I’m a career manager who has worked for the US Military in armored operations and as a civilian in industrial logistics (these two are way way more similar than you think). I’m not a technical person at all, the limit of my coding knowledge is writing a bubble sorter in visual basic. No, my job is getting **** done… somehow.

Much of the time that involves keeping all the specialized people on task no matter how catastrophically ****** things are. That means doing hard things that people not in management never have to do, like telling people ā€˜no’ and setting priorities. Also, it frequently means cleaning up after my people when their lack of social skills combines with stress, anger, and short deadlines to cause them to damage relationships with others who they have to rely on in order to do their jobs.
All this kind of makes me want to take some of the rage posts out of here and use them as teaching points. The lesson would be something like, ā€œRead the words by these people. Laugh at the words by these people. But whatever you do, don’t be like these people.

Why is this, the rage posters might reply? Well, let me try and put this in context. One of my people busts into my office in a rage and says, ā€œSir, one of our vendors has an issue that causes degraded performance in 1% of a non-critical function! I talked to the technical expert and they aren’t deploying the fix until Monday in case it breaks something bigger, because there wouldn’t be anyone there over the weekend to fix it!ā€

During this speech my expression would have gradually changed from concern to confusion to something that implied the speaker had just sprouted a huge floppy **** from his forehead and it was bouncing off the tip of his nose as he spoke. With that in mind my reply would be something like, ā€œSo this keeps us from functioning over the weekend?ā€

This uniquie and beautiful individual would then say something like, ā€œNo, but we’re customers and the product isn’t perfect! And I just sent them a horribly mean email telling them they fail at their job because of it!ā€

Now, my reply from there would really depend if I was in uniform or not. If I was a civilian I would have a professional development session with this person. If I was in the military I would conduct the session while they held a 40lb medicine ball over their head. Then, once they had hopefully learned something, my next action would be to pick up the phone and call the vendor. I would humbly apologize for my subordinate’s conduct, assure them it would never happen again, and ask if they had any other issues they wanted to bring to my attention.

You see, for the rage-posters who are making demands for an immediate fix, all you are doing is making yourselves look like stupid assholes. There are a few reasons for this. The problem is really quite small. It impacts a small portion of a secondary part of the game, and a fix is in the works. In fact communication about the fix has been quite clear and direct; this is how you want to find out about problems from a supplier! Because of the point above the degree of anger and simple meanness appears, to an objective observer, to be quite out of proportion to the actual problem. Now, you can always be mean on the internet, and you can abuse Foxfour to your heart’s content without facing any real consequences, but if you are going to cloak your criticism in terms of, ā€œBut it hurts Eve!ā€ you are either a **** looking for a justification or you are woefully ignorant about how things work in the real world.

You see, anyone who has actually been there and done stuff will tell you relationships between suppliers and customers are hugely important. By acting as if this utterly trivial problem is the end of the world, and by taking a very nasty tone when you do it, all you are damaging the community’s relationship with the Devs. This makes the Devs less likely to listen to feedback about other problems in the future. Since some of those future problems are going to be far more consequential you do Eve a disservice, and you make yourself look like a douche in the process.

Then, just for variety, we get to the anger about somebody taking a weekend off with a small technical problem outstanding. Now, if the servers were down, or even if maybe killmails weren’t being recorded at all, I could see why people would be mad. But that isn’t the case. No, it’s a tiny problem that will go away in 96 hours. Contrast that with the fact that Burnout is real, and bad for productivity. I know, I’ve been in places where quitting wasn’t an option and seen how it ruins people. Being on call because this change got pushed on a Friday would degrade Foxfour’s weekend. I know enough about experts to say that an hour of clear, thoughtful code writing is worth a day of exhausted pecking. Plus, lack of focus makes bugs more likely. So why, given the tiny scope of the problem, should she have to worry about during off hours? Again, that lack of proportion is not doing you hater types any favors here.

Still, feel free to keep the rage coming. It’s fun to read, and the Eve community wouldn’t be the same without it. Plus, some of you might even enjoy the feeling of that great big willy tapping your nose with each key-stroke.

Also since this thread has gone from code releases to slavery in only four pages, I must complete the circle. Foxfour, you are Hitler for not releasing a fix for this on Friday. Not like Hitler, you are literally a small Austrian man over a century old who tried to conquer Europe. And thus the Godwin has been achieved, in accordance with the book of Internets!
CCP FoxFour
C C P
C C P Alliance
#76 - 2016-06-17 23:31:34 UTC
FearlessLittleToaster wrote:
Hello this thread! I gotta say this is amazing to read. Also it provoked me into having strong opinions, and since I firmly believe everyone is entitled to my opinion on the internet I’m going to put it here!

I’m a career manager who has worked for the US Military in armored operations and as a civilian in industrial logistics (these two are way way more similar than you think). I’m not a technical person at all, the limit of my coding knowledge is writing a bubble sorter in visual basic. No, my job is getting **** done… somehow.

Much of the time that involves keeping all the specialized people on task no matter how catastrophically ****** things are. That means doing hard things that people not in management never have to do, like telling people ā€˜no’ and setting priorities. Also, it frequently means cleaning up after my people when their lack of social skills combines with stress, anger, and short deadlines to cause them to damage relationships with others who they have to rely on in order to do their jobs.
All this kind of makes me want to take some of the rage posts out of here and use them as teaching points. The lesson would be something like, ā€œRead the words by these people. Laugh at the words by these people. But whatever you do, don’t be like these people.

Why is this, the rage posters might reply? Well, let me try and put this in context. One of my people busts into my office in a rage and says, ā€œSir, one of our vendors has an issue that causes degraded performance in 1% of a non-critical function! I talked to the technical expert and they aren’t deploying the fix until Monday in case it breaks something bigger, because there wouldn’t be anyone there over the weekend to fix it!ā€

During this speech my expression would have gradually changed from concern to confusion to something that implied the speaker had just sprouted a huge floppy **** from his forehead and it was bouncing off the tip of his nose as he spoke. With that in mind my reply would be something like, ā€œSo this keeps us from functioning over the weekend?ā€

This uniquie and beautiful individual would then say something like, ā€œNo, but we’re customers and the product isn’t perfect! And I just sent them a horribly mean email telling them they fail at their job because of it!ā€

Now, my reply from there would really depend if I was in uniform or not. If I was a civilian I would have a professional development session with this person. If I was in the military I would conduct the session while they held a 40lb medicine ball over their head. Then, once they had hopefully learned something, my next action would be to pick up the phone and call the vendor. I would humbly apologize for my subordinate’s conduct, assure them it would never happen again, and ask if they had any other issues they wanted to bring to my attention.

You see, for the rage-posters who are making demands for an immediate fix, all you are doing is making yourselves look like stupid assholes. There are a few reasons for this. The problem is really quite small. It impacts a small portion of a secondary part of the game, and a fix is in the works. In fact communication about the fix has been quite clear and direct; this is how you want to find out about problems from a supplier! Because of the point above the degree of anger and simple meanness appears, to an objective observer, to be quite out of proportion to the actual problem. Now, you can always be mean on the internet, and you can abuse Foxfour to your heart’s content without facing any real consequences, but if you are going to cloak your criticism in terms of, ā€œBut it hurts Eve!ā€ you are either a **** looking for a justification or you are woefully ignorant about how things work in the real world.

You see, anyone who has actually been there and done stuff will tell you relationships between suppliers and customers are hugely important. By acting as if this utterly trivial problem is the end of the world, and by taking a very nasty tone when you do it, all you are damaging the community’s relationship with the Devs. This makes the Devs less likely to listen to feedback about other problems in the future. Since some of those future problems are going to be far more consequential you do Eve a disservice, and you make yourself look like a douche in the process.

Then, just for variety, we get to the anger about somebody taking a weekend off with a small technical problem outstanding. Now, if the servers were down, or even if maybe killmails weren’t being recorded at all, I could see why people would be mad. But that isn’t the case. No, it’s a tiny problem that will go away in 96 hours. Contrast that with the fact that Burnout is real, and bad for productivity. I know, I’ve been in places where quitting wasn’t an option and seen how it ruins people. Being on call because this change got pushed on a Friday would degrade Foxfour’s weekend. I know enough about experts to say that an hour of clear, thoughtful code writing is worth a day of exhausted pecking. Plus, lack of focus makes bugs more likely. So why, given the tiny scope of the problem, should she have to worry about during off hours? Again, that lack of proportion is not doing you hater types any favors here.

Still, feel free to keep the rage coming. It’s fun to read, and the Eve community wouldn’t be the same without it. Plus, some of you might even enjoy the feeling of that great big willy tapping your nose with each key-stroke.

Also since this thread has gone from code releases to slavery in only four pages, I must complete the circle. Foxfour, you are Hitler for not releasing a fix for this on Friday. Not like Hitler, you are literally a small Austrian man over a century old who tried to conquer Europe. And thus the Godwin has been achieved, in accordance with the book of Internets!


9/10, would read again. Missed a point for not linking to a funny gif of some kind...

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Fivenake
University of Caille
Gallente Federation
#77 - 2016-06-18 06:20:54 UTC
FearlessLittleToaster wrote:
Hello this thread! I gotta say this is amazing to read. Also it provoked me into having strong opinions, and since I firmly believe everyone is entitled to my opinion on the internet I’m going to put it here!

I’m a career manager who has worked for the US Military in armored operations and as a civilian in industrial logistics (these two are way way more similar than you think). I’m not a technical person at all, the limit of my coding knowledge is writing a bubble sorter in visual basic. No, my job is getting **** done… somehow.

Much of the time that involves keeping all the specialized people on task no matter how catastrophically ****** things are. That means doing hard things that people not in management never have to do, like telling people ā€˜no’ and setting priorities. Also, it frequently means cleaning up after my people when their lack of social skills combines with stress, anger, and short deadlines to cause them to damage relationships with others who they have to rely on in order to do their jobs.
All this kind of makes me want to take some of the rage posts out of here and use them as teaching points. The lesson would be something like, ā€œRead the words by these people. Laugh at the words by these people. But whatever you do, don’t be like these people.

Why is this, the rage posters might reply? Well, let me try and put this in context. One of my people busts into my office in a rage and says, ā€œSir, one of our vendors has an issue that causes degraded performance in 1% of a non-critical function! I talked to the technical expert and they aren’t deploying the fix until Monday in case it breaks something bigger, because there wouldn’t be anyone there over the weekend to fix it!ā€

During this speech my expression would have gradually changed from concern to confusion to something that implied the speaker had just sprouted a huge floppy **** from his forehead and it was bouncing off the tip of his nose as he spoke. With that in mind my reply would be something like, ā€œSo this keeps us from functioning over the weekend?ā€

This uniquie and beautiful individual would then say something like, ā€œNo, but we’re customers and the product isn’t perfect! And I just sent them a horribly mean email telling them they fail at their job because of it!ā€

Now, my reply from there would really depend if I was in uniform or not. If I was a civilian I would have a professional development session with this person. If I was in the military I would conduct the session while they held a 40lb medicine ball over their head. Then, once they had hopefully learned something, my next action would be to pick up the phone and call the vendor. I would humbly apologize for my subordinate’s conduct, assure them it would never happen again, and ask if they had any other issues they wanted to bring to my attention.

You see, for the rage-posters who are making demands for an immediate fix, all you are doing is making yourselves look like stupid assholes. There are a few reasons for this. The problem is really quite small. It impacts a small portion of a secondary part of the game, and a fix is in the works. In fact communication about the fix has been quite clear and direct; this is how you want to find out about problems from a supplier! Because of the point above the degree of anger and simple meanness appears, to an objective observer, to be quite out of proportion to the actual problem. Now, you can always be mean on the internet, and you can abuse Foxfour to your heart’s content without facing any real consequences, but if you are going to cloak your criticism in terms of, ā€œBut it hurts Eve!ā€ you are either a **** looking for a justification or you are woefully ignorant about how things work in the real world.

You see, anyone who has actually been there and done stuff will tell you relationships between suppliers and customers are hugely important. By acting as if this utterly trivial problem is the end of the world, and by taking a very nasty tone when you do it, all you are damaging the community’s relationship with the Devs. This makes the Devs less likely to listen to feedback about other problems in the future. Since some of those future problems are going to be far more consequential you do Eve a disservice, and you make yourself look like a douche in the process.

Then, just for variety, we get to the anger about somebody taking a weekend off with a small technical problem outstanding. Now, if the servers were down, or even if maybe killmails weren’t being recorded at all, I could see why people would be mad. But that isn’t the case. No, it’s a tiny problem that will go away in 96 hours. Contrast that with the fact that Burnout is real, and bad for productivity. I know, I’ve been in places where quitting wasn’t an option and seen how it ruins people. Being on call because this change got pushed on a Friday would degrade Foxfour’s weekend. I know enough about experts to say that an hour of clear, thoughtful code writing is worth a day of exhausted pecking. Plus, lack of focus makes bugs more likely. So why, given the tiny scope of the problem, should she have to worry about during off hours? Again, that lack of proportion is not doing you hater types any favors here.

Still, feel free to keep the rage coming. It’s fun to read, and the Eve community wouldn’t be the same without it. Plus, some of you might even enjoy the feeling of that great big willy tapping your nose with each key-stroke.

Also since this thread has gone from code releases to slavery in only four pages, I must complete the circle. Foxfour, you are Hitler for not releasing a fix for this on Friday. Not like Hitler, you are literally a small Austrian man over a century old who tried to conquer Europe. And thus the Godwin has been achieved, in accordance with the book of Internets!



Former 31 Bravo here. Never got along with the yellow or blue cords Big smileBig smile
Ohno no Borrox
xX-Crusader-Xx
Tactical Narcotics Team
#78 - 2016-06-19 08:05:10 UTC  |  Edited by: Ohno no Borrox
FearlessLittleToaster wrote:
Hello this thread! I gotta say this is amazing to read. Also it provoked me into having strong opinions, and since I firmly believe everyone is entitled to my opinion on the internet I’m going to put it here!

I’m a career manager who has worked for the US Military in armored operations and as a civilian in industrial logistics (these two are way way more similar than you think). I’m not a technical person at all, the limit of my coding knowledge is writing a bubble sorter in visual basic. No, my job is getting **** done… somehow.

Much of the time that involves keeping all the specialized people on task no matter how catastrophically ****** things are. That means doing hard things that people not in management never have to do, like telling people ā€˜no’ and setting priorities. Also, it frequently means cleaning up after my people when their lack of social skills combines with stress, anger, and short deadlines to cause them to damage relationships with others who they have to rely on in order to do their jobs.
All this kind of makes me want to take some of the rage posts out of here and use them as teaching points. The lesson would be something like, ā€œRead the words by these people. Laugh at the words by these people. But whatever you do, don’t be like these people.


Also since this thread has gone from code releases to slavery in only four pages, I must complete the circle. Foxfour, you are Hitler for not releasing a fix for this on Friday. Not like Hitler, you are literally a small Austrian man over a century old who tried to conquer Europe. And thus the Godwin has been achieved, in accordance with the book of Internets!


What a well written response. Good Job there. Question: You're sitting in your office shuffling your big pile of papers and in walks a technician. He tells you that 1/100 times the ejector seat wont function - and cos its friday the manufacturers won't give you a fix till Monday in case it breaks something else. Which medicine ball would you give him then. You see, my friend, both you and the P seem to be missing a number of points here

People get different things from the game - to some just blowing stuff up is important, for others its mining and for some it's killboards. Apparently if it's killmails, you should reconsider your priorities, and so for some it's mission critical.

But the main point I was trying to make - and is either being deliberately (bad) or accidentally (very bad) being misinterpreted - is this. Just becaiuse software has always been released before its ready does not mean that we should accept it. The refeneces to slavery etc were to illustrate that bad things should not be accepted, not to compare anyone to slavers. If the end-user (us) always accept poor systems of working then they are not going to be fixed. And how do we do that, you may ask. Well the method i choose to do that is to let the devs know that I find it unacceptable, rather than play the game for a few months then decide that it's broken and go to play another game that will have the same problems.

The software industry should have a look at 6-sigma practices. It may be found insightful

p.s. Hitler was considered tall for the time, but the winner writes the history. Now if I was your superior and you came to me without checking the facts i'd be making you bounce the medicine ball off your head to knock some sense into you
MachineOfLovingGrace
V0LTA
OnlyFleets.
#79 - 2016-06-19 10:32:35 UTC
Ohno no Borrox wrote:
But the main point I was trying to make - and is either being deliberately (bad) or accidentally (very bad) being misinterpreted - is this. Just becaiuse software has always been released before its ready does not mean that we should accept it. The refeneces to slavery etc were to illustrate that bad things should not be accepted, not to compare anyone to slavers. If the end-user (us) always accept poor systems of working then they are not going to be fixed. And how do we do that, you may ask. Well the method i choose to do that is to let the devs know that I find it unacceptable, rather than play the game for a few months then decide that it's broken and go to play another game that will have the same problems.


So you complain about software being released before it's ready, and about PEOPLE TAKING MEASURES TO MAKE SURE SOFTWARE IS NOT RELEASED BEFORE IT'S READY at the same time? Wha...?

Also, was that a Goodwin? I'm not familiar with that phrase, I'm not sure.
Ohno no Borrox
xX-Crusader-Xx
Tactical Narcotics Team
#80 - 2016-06-19 10:54:05 UTC
MachineOfLovingGrace wrote:
Ohno no Borrox wrote:
But the main point I was trying to make - and is either being deliberately (bad) or accidentally (very bad) being misinterpreted - is this. Just becaiuse software has always been released before its ready does not mean that we should accept it. The refeneces to slavery etc were to illustrate that bad things should not be accepted, not to compare anyone to slavers. If the end-user (us) always accept poor systems of working then they are not going to be fixed. And how do we do that, you may ask. Well the method i choose to do that is to let the devs know that I find it unacceptable, rather than play the game for a few months then decide that it's broken and go to play another game that will have the same problems.


So you complain about software being released before it's ready, and about PEOPLE TAKING MEASURES TO MAKE SURE SOFTWARE IS NOT RELEASED BEFORE IT'S READY at the same time? Wha...?

Also, was that a Goodwin? I'm not familiar with that phrase, I'm not sure.


If the first part was achieved, the second part wouldnt be necessary - look I answered without using capslock