My story begins sometime around 1985. Born in 1971 in a small town in hessen, germany, I grew up in a time when phones had houses attached to them via cables, required you to speak into a dog chew bone, had dialtones and rotary dials, which took way too long to go back to zero when you had to dial fast.

And somehow during my adolescence, when computers were for me just part of science fiction, I knew that one day I would work with them.

My first computer was a C64, which came without a storage device. So I…

Lukas, you actively and willingly misrepresent what is in this video. Which is the usual thing you conspiracy people do.

You take Buzz Aldrins answer to a different question and portray it as an answer to a question which was not asked. Just to spin his answer in your special conspiracy way.

The girl asks (paraphrased) "Why did we not *go back* there" and Buzz Aldrin answers (again, paraphrased) "This should not be an 8 year olds question, it should be my question. Because we didn't. We didn't go there".

Yes, taken out of context, i.e. ignoring the question that…

… or where does the data go in the end

As part of my current devslopes ios academy I try to invest as much time as possible into learning swift. In theory. In reality I have a fulltime job as a freelance java developer in one of the rather complicated areas, which is german institutional reporting. And this project takes a rather big toll on me right now. Which is ok, since I really do like to work this way. But sitting down and more or less going to school at the end of an ordinary stressfull day is not…

Sorry, but in my opinion this is nonsense. I've seen firsthand when people all of a sudden try to start writing functional code. What a mess. You can truly and deeply f# up your code in many styles, be it oop or functional. The amount of data being copied into new structs / objects every time you change something is amazing. No, I'd rather take the oop approach, strip it from all the unnecessary clunkiness (like deep levels of inheritance) and make the code easy and good to understand.

So no, introducing the next holy grail will not solve the problem.

Solving the problem is what actually solves the problem. Meaning: Do no just try to blame the bad code on the underlying languag and its princibles. Blame it on the fact that writing good code requires passion and diligence.

The first task of week four, devslopes academy, was rather simple. “Write a method in swift that prints the first 100 numbers of the fibonacci algorithm”.

In my head the code was almost done even before I started to type the first letter in xcode. As usual for the experienced developer. Do a oneliner of recursive magic, and voilá, task done.

So, the very first version was:

But hang on, what is that! Ok, here we go. Arithmetic overflow. I never had done the fibonacci algorithm before, so the fact that the numbers more or less grow exponentially and go…

Gunnar Stahl

Born in 1971, finished school after 13 years in 1990. Professional developer sind 1992. Freelancer since 2009. Maried, father of two sons. Autistic.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store