The Forced Writing of Code

http://webr3.org/blog/general/forced-coding/

So you found a link while surfing and thought "I'll share this on 4chan!". Now you have two problems (btw the links bullshit)

Don't read related material to get you in the flow.

That doesn't sound right to me.

HOW TO PROGRAM
1. Don't do stuff that isn't programming.
2. Do stuff that is programming.


Now to repeat this into 10 steps, put on the internet, and WEB2.0 FAME!

Looks like the ranting of a low-level Java codemonkey. EXPERT PROGRAMMERS know when and what they need to do, because they've achieved Satori.

The part where it suggests not planning is the worst idea.

Planning allows you to segment your work into chunks.  You know how much you'll get done for the day.  You have a goal, not just some pile of shit that is seemingly endless ("why bother, it'll never be done").

Planning also helps you not waste your damn time designing a shitty architecture for something you don't understand.

This article also fails to mention a major reason why code doesn't get written: you get sidetracked with optimization or infinite generalization ("oh, if I code it at this abstract level, it would work for other projects! oh, I can abstract that too for even more projects! oh, now I can never get this done because it's too large scale..."). 

Anyway, this shit sucks Alan Turing's Pseudo-Penis.

8 Name: Anonymous 2011-02-03 2:16

9 Name: Anonymous 2013-09-01 14:00

Addition is associative (κ + μ) + ν = κ + (μ + ν).

---

Don't change these.

Name:		Email:
Entire Thread Thread List