Looking for some good design blogs

Quote from arhurt

This is the kind of read I like: http://www.flarkminator.com/2011/11/19/ ... r-systems/

or just, you know, agile development.

i don't think agile development cycles are the problem, i rather think that people do not understand how they should be used. the main reason for having agile development is to make the most of a reflective process. it seems you're having more of a problem with management of these processes than with the processes themselves. i never spoke of task lists or whatever other details you have in this, because agile development doesn't necessarily encompass them.

i look at valve's cabals and think of them as agile development processes, simply because they let many people iterate over the same chapters, levels, objects, etc. as far as i understood it, it is also a fairly unmanaged process, where people add whatever they think fits, and where they discuss about what they are doing in the individual cabals.

i'm trying to say that agile development isn't a management philosophy? if anything it is a framework for developing something, just like GRIP is. what that article essentially states is an agile development process, perhaps just optimized for creative heads. i mean the first drawing in itself describes an agile process that goes back and forth between iteration cycles. i don't think this is missing the point, i think it's just abstracting it to where the idea for it came from.

In my last studio managers were all hyped by agile development, everything was cut out in sprints of 2 weeks.

In the end i found it really bad news, because if the manager isn't that virtuous, people have less visibility over the project and it encourage them to take bad decisions that can make things WAY much harder in 1 or 2 months just to reach the end of the sprint. Imo it was more a cool looking fashion to give some credibility to the work of managers.

Quote from Pericolos0

agile is more about development and this is more about design.As usual with you, this is a discussion of semantics (your loose interpretation of agile vs my very strict interpretation of the development methodology that it really is), and pointless lol.

you know, if there was actually something worthwhile in that article i'd be all over it, but it just seems to rehash what agile development, or perhaps, as a better example, prototyping does already. development is an abstraction of design, because in design you fucking develop your design as well, whether it is a creative process or not. besides that, agile development is a methodology that can be abstracted to be used in everything (as a testament to the modularity in software development).

i mean, fuck, look at this quote:

Quote

Design is not linear, my friends, because it flows in four cycles. They are cycles, not steps, because you spin around inside them, picking up speed, excitement, and eventually, if it passes the test, you fling yourself out of that cycle to the next; where, like before, the process of building up speed continues and, most importantly, if you fail to maintain your speed, you fall back to a previous cycle — possibly out of the loop completely, which means, guess what, that idea didn’t make the cut.

compare it to:

[Blocked Image: http://i.imgur.com/ubJFY.jpg]

it's not exactly rocket science in spotting the similarities, i don't know why you are so vehement in saying that it ISN'T an agile development process, or why you bring shit like management and other details into it, when that is not even a necessary part of agile development. this tells me that you do not understand agile development processes more than anything else.

Just learn how hurricanes work guys, It's basically the same thing!

[Blocked Image: http://www.katrinahelp.com/hurricane-diagram.gif]

it's not exactly rocket science in spotting the similarities, i don't know why you are so vehement in saying that it ISN'T a hurricane process, or why you bring shit like management and other details into it, when that is not even a necessary part of hurricanes. this tells me that you do not understand hurricane processes more than anything else.

My exagerated point being: "As usual with you, this is a discussion of semantics, and pointless lol."

Wait, so basically it's a prisoner's dilemma?

I fucking hate scrum! I remember finishing my work faster than others sometimes and having nothing to do for one or two days because the producer, who also loved to do development on his side, was too busy with his own stuff or had no idea what to get me to work on next because he was unable to plan anything further than a 2 weeks long sprint.

But the worst thing i have ever experienced with scrum was losing virtually 80% of a work day once sticking goddamn post-its on a whiteboard and discussing if we should use planning poker or not to estimate if we would be able to complete all tasks in the sprint. Fuck that shit lol

Oh and yeah, sometimes tasks were not brokenup properly and the production graph looked stuck on the same level until the last one or two days of the sprint.

If i was lead i´d only have a whiteboard where people added their own tasks by themselves, for visibility sake. I also like quick morning meetings, thats the best thing about scrum imo.

Fuck graphs and stupid shit like that.

Quote from arhurt

Just learn how hurricanes work guys, It's basically the same thing![Blocked Image: http://www.katrinahelp.com/hurricane-diagram.gif]

it's not exactly rocket science in spotting the similarities, i don't know why you are so vehement in saying that it ISN'T a hurricane process, or why you bring shit like management and other details into it, when that is not even a necessary part of hurricanes. this tells me that you do not understand hurricane processes more than anything else.

My exagerated point being: "As usual with you, this is a discussion of semantics, and pointless lol."

Fucking hurricane processes man. Dont get me started on that.

and everyone is trolling again....

Quote from Sentura

and everyone is trolling again....

Everyone is trolling because you are somehow comparing

[Blocked Image: http://i.imgur.com/qOqDS.png]

to this

[Blocked Image: http://i.imgur.com/ubJFY.jpg]

Are you still so sure about the similarities (A hint; in the first image the P is not connected to the G).

I think you would score very low on those IQ tests where you have to match (or mismatch) logical images

skjalg, really, stop bullshitting.

so if you took in the quote i used, he explains how everything is connected, and how, my friends, design isn't linear. he explains how you can go back and forth between cycles, which is very similar to agile development. the point i've been trying to make all this time, which you have been apparently misunderstanding deliberately, is that agile development is iteration and reflection based. i did even say that maybe it was restructured for creative heads, but that doesn't mean that this isn't the same fucking thing. then you take in details like management, or show concrete examples of other frameworks such a scrum, and expect all agile development to equate to that. agile development doesn't have a tight fucking definition, because agile development depends on how you want to structure your framework. the framework then may be more tightly defined, but there are so many frameworks out there that STILL derive from agile development.

talking about interwebs an people using big words in their blog, or the lack of it ...

Quote from Sentura

skjalg, really, stop bullshitting.so if you took in the quote i used, he explains how everything is connected, and how, my friends, design isn't linear. he explains how you can go back and forth between cycles, which is very similar to agile development. the point i've been trying to make all this time, which you have been apparently misunderstanding deliberately, is that agile development is iteration and reflection based. i did even say that maybe it was restructured for creative heads, but that doesn't mean that this isn't the same fucking thing. then you take in details like management, or show concrete examples of other frameworks such a scrum, and expect all agile development to equate to that. agile development doesn't have a tight fucking definition, because agile development depends on how you want to structure your framework. the framework then may be more tightly defined, but there are so many frameworks out there that STILL derive from agile development.

So your defense here is that agile development doesn't have tight definition, and that its about how you want to structure your framework.

Great.

Then I can get away with saying that my kid uses agile development when shitting in his diapers. its an iterative process and whenever I change diapers I can tell that he's reflecting over what he's done (because he's smiling) So because agile development is such a lose term (all you really need is the keyword "iterate" right?) then this fits... /sarcasm

Point is, you cant wiggle your way out of yet-another-argument that you're losing by saying that your terminology (agile development) can mean everything in the world that is iterative design, and that you are right because in his design scheme he used iteration. Agile development does have a fairly tight definition. If you read up on wikipedia you'll notice how much the process described in that blog differs from agile development. (Look under characteristics)

Quote from Skjalg

my kid uses agile development when shitting in his diapers.

Let your kid out of this