Article/Code Creation Order

J Dunlap

Depends on the sort of article. For simple how-to articles, I write up a point list of things to cover, then write bits and pieces of both code and text to cover them, and then put the code snippets together into a demonstration project. For articles that center on a component or class I've written, generally it starts as code that I write for a project or experiment. I get it functionally finished - which means it's to the point where I know exactly what the article will cover - then write an article, then do more testing to make sure there are no hidden problems in the code, and make sure that the comments, formatting, and object model are just how I want them.

Joe Woodbury

Code then article and then I often revisit the code. I've changed code as the result of trying to explain it.

Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

peterchen

Code. [edit] And only if I see it's good, (in my veiled view of reality), I write n article [/edit]

Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Linkify!|Fold With Us!

Rajesh R Subramanian

Rama Krishna Vavilala wrote:

Writing is too difficult coding is too easy.

You're right! :-D

Nobody can give you wiser advice than yourself. - Cicero ப்ரம்மா

Eytukan

For the Grand Negus, separating the article from the code would be a tiresome processes ;P :-D

Code-Frog:So if this is Pumpkinhead. Time for him to run and hide. It's an interesting thought really.

Aryo Handono

Too Bad, I haven't post any articles yet.... Since I don't have much time to think anything to write. :-D

"Courage choose who will follow, Fate choose who will lead" - Lord Gunner, Septerra Core "Press any key to continue, where's the ANY key ?" - Homer Simpsons Drinking gives me amazing powers of insight. I can solve all the worlds problems when drunk, but can never remember the solutions in the morning. - Michael P Butler to Paul Watson on 12/08/03

Ed Poore

Ravi Bhavnani wrote:

My apologies!

Why? It's good that someone finally managed to catch him out ;P

I have no idea what I just said. But my intentions were sincere.

Poore Design

Ed Poore

:laugh: If he ever writes any articles :suss:

I have no idea what I just said. But my intentions were sincere.

Poore Design

Sceptic Mole

Nishant Sivakumar wrote:

I've always had the code first, and then written the article.

I wonder what he's writing about when he has no code? :laugh:

Gary R Wheeler

That sounds similar to my approach to my (one and only :-O) article. The original code was for something I had done at work. That code had to be stripped to its essentials, the article written, and a suitable sample application written to go along with it.

Software Zen: delete this;

Fold With Us![^]

TheGreatAndPowerfulOz

code first. else how do you know what to write? hmm, maybe both together.

Silence is the voice of complicity. Strange women lying in ponds distributing swords is no basis for a system of government. -- monty python Might I suggest that the universe was always the size of the cosmos. It is just that at one point the cosmos was the size of a marble. -- Colin Angus Mackay

Eytukan

Cheers :beer:

Code-Frog:So if this is Pumpkinhead. Time for him to run and hide. It's an interesting thought really.

Raj Lal

Rama Krishna Vavilala wrote:

Writing is too difficult coding is too easy.

i will second that

Omit Needless Words - Strunk, William, Jr.