Article/Code Creation Order

Shog9 0

Code. Then article. Then more code, since the original code didn't match what i'd written...

Ravi Bhavnani

Code first, article text next. Like many other authors, the code I publish at CP stems from general purpose modules I've used in my own (i.e. not for my employer or on my employer's time or while at work) apps for several months/years. /ravi

This is your brain on Celcius Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com

Nish Nishant

Ah there you are. I ended up being the butt of this morning's repost jokes.

Regards, Nish

Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)

Ravi Bhavnani

'Allo, old fruit! My apologies! /ravi

This is your brain on Celcius Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com

Ravi Bhavnani

I must confess I've fallen prey to the charms of Sarvana Bhavan and Amy's delectable fried egg sandwiches (max 2 per week, though - it's my only source of eggs). I'm fast turning into an overweight mass of saturated fat. And... my fridge is stocked with Russian ham. :cool: /ravi

This is your brain on Celcius Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com

Marc Clifton

Code first, or sometimes code and article concurrently. I once wrote an article first, and tossed the whole thing because the code ended up being significantly different than envisioned. Marc

Thyme In The Country

People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith

PJ Arends

Always the code first. The code is written to fill a need and then I decide that it is worth sharing so I write an article for it.

You may be right
I may be crazy
-- Billy Joel --

Within you lies the power for good, use it!!!

PIEBALDconsult

Hear hear.

Michael Dunn

Some of my tutorials were done in parallel, especially the WTL series. I had to go deep into some part of WTL (on my own, to teach myself), but the code from that effort wouldn't have worked well in a tutorial article. So I wrote an outline for an article, then came up with an idea for the sample code to go along with the article, then wrote both the code and article together.

--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ"); Ford, what's this fish doing in my ear?

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