Coding is when we're least productive
codemanship.wordpress.com
Coding is when we're least productive
1–10 of 59 posts
Re: Coding is when we're least productive
#2Coding is when we carefully write down our solution to a problem.
(Manager pushes paper, pen and a list of problems in front of you and demands, “Now write, just write! And fast!”)
Re: Coding is when we're least productive
#3Coding is the 5 minute result for an hour of thinking.
Re: Coding is when we're least productive
#4Oh, that must be fun to be hired by the client directly... I wish each my programming job was not an ivory tower :(
Re: Coding is when we're least productive
#5So the only anecdote you could find from your long career is one example at the start of your contracting? What the hell with all those low quality shite talking about code this, code that?
> Founder of Codemanship Ltd and code craft coach and trainer
Ooh, it’s all coming together.
Re: Coding is when we're least productive
#6This is one reason I always roll my eyes when people talk about how vim keyboard bindings are so great because you don't have to move your fingers from the home row. The actual action of typing text is a small part of the process of coding.
Re: Coding is when we're least productive
#7E.W. Dijkstra: "Measuring programming progress by lines of code is like measuring aircraft building progress by weight".
Personally, I think, much of the art of programming is to do as much as possible with as few lines of code as possible.
Re: Coding is when we're least productive
#8This is one reason I always roll my eyes when people talk about how vim keyboard bindings are so great because you don't have to move your fingers from the home row. The actual action of typing text is a small part of the process of coding.
Depends on how you work I guess. I explore solutions through coding different versions of some algorithm, sure I could theorycraft as well but I am stronger by just writing code and see if it runs. I type a lot so vim motions help me a ton.
Re: Coding is when we're least productive
#9Coding is the result of intense productivity... or was. Hm.
Re: Coding is when we're least productive
#10E.W. Dijkstra: "Measuring programming progress by lines of code is like measuring aircraft building progress by weight". Personally, I think, much of the art of programming is to do as much as possible with as few lines of code as possible.
There’s more to it than that though. The solution using the least possible lines is often inscrutable and brittle. The art is in finding the right level of abstraction which can deliver the performance required while being sufficiently legible. Depending on the specific problem you have to weight your solution accordingly, if performance is critical you must often forfeit legibility. The art is in recognising and dealing with trade offs.