Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×

Comment What's there to celebrate? (Score 5, Insightful) 83

A franchise being milked dry by its IP holder, fans being sued for trying to create something, and mostly being sued for creating something that's better and closer to the core idea of the franchise than its IP holder creates...

What exactly is there to celebrate? Any "real" celebration would probably be snuffed instantly by the IP holders.

In the eternal words of Bones: "It's dead, Jim."

Comment Re:Something off the rails (Score 1) 113

Ok, then put out "disable ad-blockers if you want me to continue delivering content" and if people really want your content, they will.

There are also various ways to get people to actively pay for your content, and guess what: People do actually do that, crazy as it may sound to some.

Sorry, but for FAR too long unscrupulous advertisers have bombarded the people with ads. They should not be surprised that people defend themselves against it.

Comment Re:Whenever I want really... (Score 1) 228

I know, it DOES sound absurd, and in practice, it is. Now, it's "only" around 800 individual products actually delivered fresh each year, but because I'm having to touch and test older games as a part of that process, I'm in effect coding for thousands of shipped products per year, just to make it as sane as possible to continue each product line.

And yes, that means each day, I'm jumping between 15 minute mini-projects, reviewing and raising issues on design documents, throwing together project directories and rapidly configuring them, throwing those project into automated testing suites of tools (which I'm also cross-developing), testing the various inputs/outputs of other teams to make sure nothing will prevent delivery to spec.

I'm making active progress on around a dozen separate projects each day, contacting clients as needed to hammer out shared documents, then reacting to rare but important issues as they are raised.

Ryan Fenton

Comment Whenever I want really... (Score 2) 228

I code for thousands of mostly-unique commercial software products a year, using 8 languages (mostly C#), for many dozens of major customers, and lots of smaller ones.

Because of this, I have a huge chain of demands I keep track of, and methods of automation in order to collectively manage a constant flow of data requirements, and of course tracking issues both shared and common between these scenarios.

When I'm coding, I've got to code in a way that communicates these details to myself, consistent between all the languages I might have to touch for coding, scripting, database, reporting, and specialized languages a client may suddenly require.

Because of that, my code has to be a loose framework, a late-binding train station of logic, where demands may switch at any moment, and limitations imposed from other teams may similarly pop up.

My code is littered with multi-paragraph discussions of a technology I once had to interact with (customers often switch back), large sections of functions commented out rather than deleted, and other 'bad' practices just to give me landmarks and a 'flavor' of what a customer is occasionally interested in, amidst a never-ending avalanche of context switching between products and customers.

I've redesigned these several systems from the ground floor once (they used to only handle a small fraction of the work, using an antiquated language), and am working with a team to do a better design... but it's been very difficult for a team of perfectionists to understand how to react to an unlimited flow of changing requirements. Fortunately, the code itself has been quite usable, and they're using the same languages, but no system can really handle these demands truly consistently - I'd call it NP ridiculous. It's basically the "mythical man month" writ live, where I've got to do my work, and train a team whose work process may never really be able to do what I can do - definitely healthier long term, but can't help but result in some amazing process failures.

I actually would have made most of these design changes myself, but at the time, I was forbidden by management from making those choices, since I was doing my work directly at the production level - so it's actually a bit of a relief to see someone at least allowed to make some of the better choices.

In short (and yes, for this scenario, this is short), because I'm doing alone, for years, what a team of almost any size would struggle to approximate, as many of us seem to be doing, I've got no choice but to code how I need to in order to have a system that I can sanely maintain in an insane set of requirements. There's not really a choice in the matter, if your put in a position where "oh, we suddenly need this" exists as a live production task in a growing industry.

Ryan Fenton

Slashdot Top Deals

"Catch a wave and you're sitting on top of the world." - The Beach Boys

Working...