Post

Richard Groß
@richargh.de

Offloading work to another entity means you do not train the required skills, eventually you get worse. Writing code seems like one of those skills where it’s ok to offload it. We are engineers, not artists. We are here to solve a problem, sometimes with code.

Richard Groß
@richargh.de

Yet I wonder if that’s a good idea. When I write code I learn. Things that I thought where clear from the description become ambiguous when written as code or when interacting with existing features. Slowly my mental model of the application builds up and I can express part of the app with drawings.

0 reposts1 like

Richard Groß
@richargh.de

I learn to reason about the application. I learn about the domain because I model it as clear as I can. I learn how to slice problems so I can implement them in baby steps. And of course I get fast feedback.

Richard Groß
@richargh.de

So here is my conundrum: is coding just a typing activity and I can afford to lose it OR is it interrelated with my other skills and they boost each other? Is coding the linchpin that I need for all the other stuff to work?

Richard Groß
@richargh.de

There are of course drawings I can use to reason about the software (UML has ~13 of them) but aren’t they more a artifact which developers with a mental model use to collaborate on the design? We were here before when we wanted to design software only through UML diagrams.