Chris Roberts being distracted by loud fans
-
Due to an increasing amount of loud fans giving Chris Roberts a headache, Star Citizen will no longer publish development roadmaps.
Star Citizen Studio Calls 'Loud' Fans A 'Distraction' In Very Bad Post
A change to the game's roadmap system could have been messaged better
And the relevant quote:
In hindsight, after living with this new Public Roadmap for the past 6 quarters, we’ve come to realize that this was a mistake. It put too much attention on features that had a high probability of shifting around. It has become abundantly clear to us that despite our best efforts to communicate the fluidity of development, and how features marked as Tentative should sincerely not be relied upon, the general focus of many of our most passionate players has continued to lead them to interpret anything on the Release View as a promise. We want to acknowledge that not all of you saw it that way; many took our new focus and our words to heart and understood exactly what we tried to convey. But there still remains a very loud contingent of Roadmap watchers who see projections as promises. And their continued noise every time we shift deliverables has become a distraction both internally at CIG and within our community, as well as to prospective Star Citizen fans watching from the sidelines at our Open Development communications.
So, the ad-hoc development and failing to deliver things that was promised over 10 years ago, because Chris Roberts has a new idea that MUST BE IMPLEMENTED NOW every minute is not a problem, it's a feature. And those complaining should just shut the fuck up and accept that Star Citizen is developed in a "fluid" style, as in the keeping on pouring all the money straight down the drain to make whatever new idea Chris Roberts comes up with only to scrap it two weeks later because he had another idea. And all those "Roadmap watchers" that see items on the roadmap as things that will be delivered within a reasonable timeframe based off the roadmap and voicing objections are a loud and annoying distraction that is ruining the fine work environment at CIG, disrupting the community and turning away prospective new
whalesfans from the game.
-
And that, dear friends, is why friends don’t let friends do Agile.
-
@Arantor This isn't Agile. This is Badgile. Agile means you can cycle through ticket after ticket while managing delivery expectations. This kind of shit happens when they don't have any processes in place to solve the problems of delivery and expectation management, so they call it "agile" because it's a big important buzzword and people don't really know what it is so they can get away with it.
-
@Shoreline said in Chris Roberts being distracted by loud fans:
This is Badgile.
Also called Waterfail.
-
@Shoreline wait, that’s a thing now? When did that happen? Every implementation I’ve ever seen of Agile is just “get as much done as quickly as possible and pray the customer doesn’t complain this week”.
(Though of course, my original line was
)
-
@Arantor said in Chris Roberts being distracted by loud fans:
@Shoreline wait, that’s a thing now? When did that happen? Every implementation I’ve ever seen of Agile is just “get as much done as quickly as possible and pray the customer doesn’t complain this week”.
(Though of course, my original line was
)Agile is like communism. Sounds nice until you think about it properly and in practice is a terrible shitshow.
-
@MrL
Real Agile Has Never Been Tried!
-
@MrL Agile is like iPhone 4 in that everyone is using it wrong. It's great for what it's meant for, except the inventors and popularizers of Agile are lying about what it's meant for. It works very well for projects in semi-maintenance phase where changes, while frequent, are limited in scope and every given task takes no more than a week start to finish. But it just doesn't work for anything big.
-
@Gąska said in Chris Roberts being distracted by loud fans:
@MrL Agile is like iPhone 4 in that everyone is using it wrong. It's great for what it's meant for, except the inventors and popularizers of Agile are lying about what it's meant for. It works very well for projects in semi-maintenance phase where changes, while frequent, are limited in scope and every given task takes no more than a week start to finish. But it just doesn't work for anything big.
Yeah. We're not really agile, but a similar "move fast" mentality is present. And my current, basically green field project is suffering. We've now rewritten the core domain model multiple times due to starting off in directions that (after actually talking to people) didn't make much sense...and that's way more difficult when you actually have live data.
-
@Gąska said in Chris Roberts being distracted by loud fans:
@MrL Agile is like iPhone 4 in that everyone is using it wrong. It's great for what it's meant for, except the inventors and popularizers of Agile are lying about what it's meant for. It works very well for projects in semi-maintenance phase where changes, while frequent, are limited in scope and every given task takes no more than a week start to finish. But it just doesn't work for anything big.
Yes. But also 'agile' is used as an excuse to never plan anything, never be prepared for anything, not fixing bad processes/culture, not introducing processes, not drawing consequences from fuckups, etc.
Or in short: for management not doing its job.
-
Yeah, that's a problem. When developing something brand new a better approach would be a more traditional model of making up requirements, building them and then releasing version 1.0 to afterwards shift to something more agile-like for maintenance and feature adding.
And Chris Roberts probably could have released his original Star Citizen vision years ago had he done that and decided what musts has to be included for version 1.0 and then go about adding extra content to that in minor and major content patches.
But Chris Roberts does Star Citizen in the way an inexperienced developer does a hobby project: throw together any idea fully ad-hoc and without any thought about the big picture or delivering a finished product, because he's building his MASTERPIECE, his MAGNUM OPUS. And it wont be v1.0 until everything is in place, fully working, with all his grand ideas realized. And all his less grand ideas forgotten and thrown in the bin, including content players has already bought. But those players should not cry, they should buy the next grand thing planned and if that also doesn't get realized, well, that's just the nature of things!
Just missing that critical detail that ideas comes all the time, and if you want to have an actual product you need a damn good reason to implement ideas coming during development and not putting them in the "future content" folder, to be considered and developed after the v1.0 release.
-
@Shoreline protip, in the worst case call it Kanban.
-
@Gribnit said in Chris Roberts being distracted by loud fans:
in the worst case call it Kanban.
“Can ban? Perfect for users!” NOTWELCOMEHERE
-
@Atazhaia and that’s what I don’t get. Agile jokes aside, Roberts has shipped a number of games - are we to infer from this that the only reason Wing Commander shipped is that someone else at Origin organised it around/for him?
-
@Arantor said in Chris Roberts being distracted by loud fans:
are we to infer from this that the only reason Wing Commander shipped is that someone else at Origin organised it around/for him?
That's what I've read. At Origin he had those pesky producers and other managerial types keeping him on track and making sure he did actually work towards finishing the games and not run off on tangents because he got a new idea every 5 minutes.
Now that he's the main producer and game designer... well...
-
@Atazhaia I read the headline and thought the complaint was about bad HVAC.
-
@HardwareGeek I was thinking of the ones in his developer PC, actually.
