Your Coding Process?

off.the.walls

So i've coped lately that I have a flow for when coding up functionality.

1. Document
2. Code
3. Test
4. Debug
5. Test Again
6. Streamline the code.

What's everyone else approach or would it be fairly similar?

Encrypted Pigeon

Mines mostly

1. Hack
2. Test
3. Refactor
4. Repeat

Not always as disciplined with no. 2 but eventually get covering tests.

padraig_f

1. Dream
2. Hack
3. Hack
4. Hack
5. Dark night of the soul
6. Release

Anesthetize

In work:
1. Write test
2. Write code until test passes
3. Refactor
4. Repeat

At home:
1. Hack
2. Test
3. Hack
4. Hack
5. Test
6. Repeat

Fenster

1. Idea.
2. Hack.
3. Hack.
4. Hack.
5. Due date.
6. Despair.
7. Hackhackhack.
8. Release.

Manach

Google "How to code X"

Anesthetize

Manach wrote: »

Google "How to code X"

Step 2. Copy and paste

Tar.Aldarion

Anesthetize wrote: »

Step 2. Copy and paste

Got to click into stackoverflow first

Evil Phil

1. Design
2. Code
3. Test
4. Fix issues
5. Google error message produced by issue I can't fix
6. Implement stackoverflow fix found via google
7. Scream
8. Wish I'd done accountancy instead, I'm good with numbers supposedly
9. Debug/Troubleshoot until I find a solution
10. Dream about a career as a data scientist
11. Repeat.

c_man

1 - Receive requirements. Usually this takes the form of an incomplete sentence.
2 - Email POs/UE on what they actually want.
3 - Start dev work with common sense assumptions on what they want.
4 - The email thread becomes a monster, a meeting is scheduled.
5 - Continue dev work.
6 - Initial testing done. All good!
7 - Meeting takes place. Stakeholders decide on a complete different direction for the feature. You'll have to spend a good while explaining the edge cases and how their proposed changes impact existing features. People will speak and suggest things just for the sake of it.
8 - Get revised requirements.
9 - Implement these. Spend the next couple of days tracking down the many tiny, obscure bugs introduced/existing already which the new code highlights.
10 - Testing. Then fix existing features broken by new requirements/code, these features are usually undocumented and the domain knowledge of one person. Hope they haven't left the company.
11 - Deliver feature.
12 - Vent about this in sprint retrospective.
13 - Repeat.

RPSmedia

1. Design
2. Code
3. Testing
4. Fix issues
5. Testing

Esho

padraig_f wrote: »

1. Dream
2. Hack
3. Hack
4. Hack
5. Dark night of the soul
6. Release

5. Glad it's not just me!

L.Jenkins

1. Slurry spreading of ideas
2. Code
3. Debug
4. Code
5. Hack a Solution
6. Code
7. Realisation that testing on anything other than Production is for pussies
8. Refer back to stage 1.

Giblet

1. Type
2. Type
3. Type

Saint_Mel

- Write test cases
- Code
- Test
- Amend Test case to match actual results
- Pray
- Release
- Drink
- Let Support deal with the consequences

:-)

Ziycon

For work it would be:

- Investigate effort needed
- Document
- Implement
- Dev Test/Tweaks
- UAT Test/Tweaks
- Prod Release
- Prod Test
- Documentation

For my own projects:

- Think of feature
- Code it

dutopia

1. Requirements nailed down
2. Start framework
3. Get core work done
4. Almost done - snag time
5. Client changes requirements
6. Change code to meet requirements
7. Client changes requirements
8. Change code to meet requirements
9. Client changes requirements
10. Change code to meet requirements
11. Stress, coffee, stress, final final final changes
12. Done

gargargar

1) Get clarity on functional design
2) Think about technical design
3) Write tests
4) Write code
5) Submit to acceptance test
6) 3/4/5 on iteration
7) Sign off
8) Deploy

Encrypted Pigeon

Itzy wrote: »

7. Realisation that testing on anything other than Production is for pussies

My hero

BmCon

Get requirements.
Plan
Write sudo code.
Work my balls off.
Get update on requirement changes.
Wish I was as good as everyone else at coding.
Go onto boards and see we are all the same.
Go back to coding.
Find bugs.
Fix em.
Finnish.

Colonel Panic

I wish I could just type "sudo code" and have my computer take care of it! It's "pseudocode"!!

BmCon

Colonel Panic wrote: »

I wish I could just type "sudo code" and have my computer take care of it! It's "pseudocode"!!

Thanks man for finding the bug for me...