btxbmbr
   |
Posted - 2011.01.26 14:41:00 -
[1]
thx for your honesty. after a couple of days in eve, i d like to say some wordsą
well, you know, today i am (among others) a young mathematician, a scientist who spend too much time in eve. ;) but before that i manage/concept large it projects for german gov and institutes. of course, a mmo is different to this but maybe i know a bit about it management, elemental things you touch. you know, my projects were those where you lost 100k euro for every h you are offline.
as far as i can see you do your job very good. you seems to have a good staff. this depends of course on someone experienced or... some islandish beer, i dont know. many years hardened you.
so, first of all: i will not talk too much, i am sure that you are most experienced, and you made your own mmo experience too. what i might have to say then? how about an anonymous opinion, which should remain anonymous?
- a crash... well, its a crash then. it has never bothered me, and a normal user, who has even a problem with the city traffic or economic system, is often worried about so called failures in complex systems, sometimes too obstinate. but yes, tests are good, trivial: its part of company public affairs/politic stuff.
- never underestimate the inexperience of some programmers in complex systems (ie system theory); i watched it over years: some people recognize big things as small (blind for differences between systems with 100 and 100 mil nodes, for example, or between a team of 3 and 300). they might be fast, but they are bad architects and frameworkers, and you lose if you use them wrong.
- never talk to customers of "errors", "failures" or "crashes", or too much of it. the meaning of words does not sit in your good intentions or the words itself. use "bug" or better "unusual" instead. i saw such crazy situations where too genuine programmers talk to customers (executives) about "crashes". in one case... a (although good) programmer provoke a single call which starts a call chain, and before i knew it, i got calls from the mayor office to explain a so called "crash" and our progress. expensive naivity. materialists. machinists.
- even if you want to be fast: significant downtime must be scheduled generously. it is always better to quit before the deadline. it is a management failure when you delay patch/update dates. ever. there is no excuse for it, only in your patch plan or patch qa or update routine, or in management above: ressource management, whatsoever.
- i wonder that you got problems in patching from stage/test to live. you should change something. i had never problems like that. i had always a stage system (complete duplicate of live) where i patch first. then i upload (or often just hardlink/switch) from stage to live. there were no hot patches on live. and sure, in the last years i worked on clusters.
- what else? damn it, its snowing...
- do not trust apple gossip. its such a waste of time and ears. there are always myths about better security on macs, because of its obscurity/unpopularity, but if i am a hacker and need serious gov infos, i will be pleased when you use mac. if you have something to hide, never use a mac. i hacked macs before... cocoa/safari is cheese.
- i heard about account hijacking. ok, consider this: what kind of users were hijacked? were they experienced? if so, it maybe depends of 3rd party tools and not mails. it is easy to develop a backdoor tool with very useful infos... those little friends track your keyboard input. i did it 10 years ago, for fun. and... if i had the time, i would hack you, yea for fun, to help you, to show bugs. unfortunately, i have no. ;) (yea yea, i said nothing, i am a blender.) but... i would shoot first at your in-game-safari/chrome-browser, because its big as an open barn door.
- well, nothing more... i am sure that you have your own hierarchy and daily stuff, meetings, orga. it would be absurd and useless if i said something to this.
:)
--
he can divide by 0 |