The differences in Teaching to Code

Some weeks ago I started to live code using my Twitch project. I use this mainly to spend a few hours a week to get (again) familiar with .NET and C#. I stopped using it (in a professional way) when .NET was available as version 3.5. Indeed, my very last project was a migration project from 3.5 to 4.0.

While I was in the role of a dev/Sr. dev I used to code mostly in pair programming. Great experience. Not for everyone. I loved it. I learned a lot. Every time you stuck, you pair helped. EIther you thought and explained and he/she coded or the other way around. A major element of the secret is that you learn most when you explain.

Live Coding

The same seems to be true for live coding. Live coding is some kind of horror if you do new things. And it probably is utterly boring for all others seeing you looking up documentation and examples. However, there is quite a lot you learn while you are explaining – or at least while you try to explain. Probably, because you are trying to explain, i.e. you try to understand.

Said that I tried to implement an exercise from a recent programming course. I wanted to see, what the students face.

Problem 1: No documentation of the code

Part of the exercise was: Try to understand what the code does. In other words: reverse engineer. That’s some discipline not everybody is good in. Others are way better than me. I do need a lot of silence and time to understand what the intention of the author was when writing the code. Doing this live is quite q lot of stress. Remember, you try to talk at the same time. Anyway, I think it is a very bad example to give to students. I should try to avoid this in the future.

Problem 2: The exercise was about how to do things not what to achieve

I never thought of this before about exercises. It was about implementing a Delegate and an Interface, an Indexer and o on. Implement a subclass and use the base constructor the same way. No words about what to achieve. I think it took me two hours just to get half of the exercise done. Would I have learned how the concepts work? Have I understood the new features of the language? No way.

Problem 3: The artifacts

I really think about what I have created. Some code. No added value. Meh.

The Post-Show: How things worked much better

Afterward, there was something I had on my todo list. As we started out podcast recently, I want to generate episode covers automatically. I am a big fan of letting things being done by the robotic overlord.

Difference 1: How I started

I thought about the requirements:

  • needs to run on Windows and macOS
  • needs to be called from the command line to be used in scripts
  • needs to put some text on an existing image
  • needs to be accomplished before 1 a.m.

Difference 2: How I proceeded

I did some research (aka Googling). I was looking for some articles about how to deal with image processing in .NET. I found an article from Scott. I had a look at the different frameworks mentioned by him and decided to check out the capabilities of ImageSharp. I checked out the examples and I wrote the piece of code.

Difference 3: What’s different

I had to figure out how to do what I wanted to accomplish. I learned about at least three existing frameworks. I figured out how to use one of these frameworks. I had to figure out how to use NuGet to get the packages. I had to fiddle with some command line magic in Visual Studio projects. I learned about one new öanguage feature.

Conclusion

I have to go on with live coding because I want to become much better in it. It is quite challenging, especially if you haven’t written code for years. And it forces me to face challenges. So if you want to see me fail writing code, feel free to join the live stream in the future.

The more important fact is, that I have to re-think how we teach programming. Yes, you need to explain concepts. But one should not enforce them to be used. If doing it feels like pushing a developer in some direction. Do it with delegates and interfaces and so on. There are probably 100 different ways to accomplish your goal. Let them try out some of these ways. The might end up with the ideal solution – or not. If there is one at all.

The Open Source Issue

After working several years for Microsoft (before MSFT started to open source code), I already used quite a lot of open-source software. I run my own Linux server in the cloud internet and used a whole bunch of free and open-source software. Actually, I also open-sourced quite a bit of my code as well as contributed to various open-source projects, such as the openHAB project.

I have quite a fan of Ubuntu and nevertheless how much I would like to, I probably never will find time to contribute in a meaningful manner until I retire. Also, I have an endless list of ideas of things, I would like to write, code and probably open-source, I eventually will never get along with that list. Even worse, there is a whole list of abandoned projects I would like to claim and push forwards, but again this will never happen.

Quite some time ago, I had a friend who wrote open source. At one day, he said farewell to the community with the word “Sorry guys, however, I now have to work for real money.”, which actually point out the issue quite well.

I haven’t thought about this friend for quite a while until I meanwhile started using my very own OwnCloud server. I started browsing the addons and apps and was faced a quite frustrating situation.

For one of the plugins, I was looking for I found the following announcement

Due to the massive testing effort and the problem of nearly no donations I’m going to stop the further development. If anyone wants to step in, feel free

For another plugin in Firefox, I heavily used on for years I got the notification the project will not be continued in the future.

I am absolutely aware that maintaining OSS need quite a lot of effort and dedication. Especially if the OSS is created and maintained by private persons. Therefore, I was very disappointed by one comment recently made at on one of my projects:

..but in our org we cannot just sit and wait until someone fixes the issue.

You could still bay the author to fix the issue. This would instantly address the point made by my former colleague mentioned above. And here we go, I realized that sometimes companies doe use OSS as it does not cost money, but also the are not willing to pay to get things fixed or to fix these issues and contribute to the project due to company policies. Been there. Seen it.

I hope there will be a mind shift towards OSS and fewer comments as the one above.

Organizing Ideas – A not yet lost Battle

Recently, I have the problem to organize my ideas. To put it upfront: I don’t provide a solution. I simply describe the problem here.

Every time I surf the web, read blogs or news sites and scroll through my twitter feed, I find something interesting. Sometimes colleagues or friends point me to something, sending my a message through on of the many messengers.

Eventually, I want to work through all these articles and sources but often I simply get lost. I forget, don’t find the time and when I have time I don’t remember what or where to look at.

Problem 1: To many Inboxes

Multiple private E-Mail accounts, work e-mail, SMS, multiple messengers, blogs, news sites, work e-mail, Confluence to-do lists, private Microsoft OneNote, work Microsoft OneNote, Teams at work, an Evernote account and so on, this is an endless list of inboxes. Fome quite some time I used Pocket to collect many of these inputs but eventually Pocket turned out just be one additional growing inbox.

For now, I became very pragmatical and forward everything to one single mail account. Links, tweets, articles, photos and so on. Everything I want to read later just piles up on one single account.

Problem 2: Working through the Pile of Shame

For those with kids, they know the problem. Between work, preparing meals, keeping things up and running and spending time with the kids, there is only a little time to get other things done. Especially tasks which take a good amount of thinking, coding or diving deep into technologies. Over time this became a growing list, a queue with no consumer. One problem here is indeed to organize your ideas. I tried Microsoft OneNote, Evernote TheBrain. Eventually, I created just more lists to work through.

At one point I thought about how I organized my ideas and thoughts while writing my doctoral thesis. Eventually, the answer was the act of writing itself. I wrote everything down into a large document which ended up as my thesis. A lot of information was deleted on the way, but at the very end everything was well structured, perfectly organized and compressed to the most relevant information.

While writing another book is still on my list, the solution to my utter problem became obvious. I started to revive my blog. I wrote regularly until 2011 but due to changed focus in my jobs, blog entries became more and more infrequent. I rethought the initial idea of the blog: writing for myself and started to work through my lists and putting down as much as possible to my blog.

How is it going?

Here you are and read one of the things I had on my list. I recently tried to get rid of my “old” lists, one after another is being worked through for interesting stuff, ending in the blog. I am still looking for a nice tool setup which might help me to organize all this information without creating just another inbox, though. Therefore, the problems are not solved yet, but at least they are addressed.

Twothousandandeighteen

2018 was not bad at all. Here are some of the major achievements and events of last year. Quite a few things happened during the last year.

  • After I bought a 4K TV, I finally got my XBOX One X as there was a great deal at Amazon. Finally, I was able to fully utilize my TV.
  • In February, I started teaching Interactive Systems and MCI at the Baden-Württemberg Cooperative State University in Karlsruhe. It looks like the course went quite well as the University decided to offer it a second time during the autumn where I gave the lecture a second time. As a fun fact, they forgot to tell me until I got a note some days before the course was scheduled.
  • In May I started teaching a second lecture covering data structures and algorithms, also at the Baden-Württemberg Cooperative State University in Karlsruhe which will be given annually.
  • As a result of the lecture, I started to write a book covering this topic using .NET Core. However, I am afraid I won’t be able to finish it in 2019.
  • I also was appointed as a member of the examination board of Baden-Württemberg Cooperative State University in Karlsruhe where I advised two students writing their bachelor thesis.
  • Also in May, I became a certified Product Manager after becoming a Certified Scrum Product Owner in 2017. The course, given by Product Focus based in London, UK is highly recommended.
  • Our son celebrated his very first birthday and started walking this year. Not really my personal achievements but something you are proud of as a dad.
  • In September we switched from HomeKit to Amazon Alexa and changed meanwhile almost all our Lights to Hue and IKEA TRÅDFRI.
  • There is only a little I was able to achieve in my day job, however, our team managed to finish a five-year multi-million migration.
  • As some side projects, I started learning Ansible as well as Docker and moved my 10-year-old handcrafted, homebrewed server to the latest generation of automated container based version.
  • I also started again blogging, especially about my experiences with Docker, Ansible and further Automation.
  • Unfortunately, our rabbits died by the rabbit hemorrhagic disease. Actually, this was a rather sad event. The vaccine is not easily available for this particular and very variant of the virus. It was an event I learned a lot about vaccines, viruses as well as diseases at all.
  • Also, it seems as we experienced one of the longest droughts in Germany. We did not have any rain for weeks or even months.
  • In December, I was appointed at a teaching assignment of Software Engineering of Complex Systems at the University of Heilbronn. I will start this lecture in February ’19 as well as a lab covering software development. I am really looking forward for these new courses.
  • All over the year, I suffered from overall sleep deficiency. I wish I would know where our 16mo takes his energy from.
  • One highlight was definitely visiting my former manager and old friend from Microsoft Research who meanwhile is head of a university.
  • Eventually, I started using Twitter again.

Although I thought 2018 was a rather boring year, it looks as there was a lot going on. Unfortunately, I was not able to read that many books as I am used to, but his might change in 2019. So I am looking forward to an exciting next year and many new things to learn.

The Open Office Dilemma – Collaboration vs Working Side by Side

During the last 20 years, I worked in quite some companies, studied at universities, was self employed, worked full time remote and travelled a lot to customers. Currently, I do work in an environment where open office is a maxim and fully supported as this environment should encourage collaboration.

The Project Setup

I worked some days from home office but traveled most of the time to the customer. I slept in hotels a lot. When I was in a city where we had an office, usually Friday was “office day” where our team was not at the customer’s site.

We did have shared desks at the office, everybody had an pedestal and took the next free desk.  That was ok. We used the office day a lot to chitchat and to build up relationships with co-workers. We prepared for the week after, installed software, talked to to IT-support, went to lunch. Sometimes during the week we went to the office late so finish something we could not accomplish at the customers site. We stayed there late and had fun. When in the office it almost felt like a hackaton every time. Also managers and the CEOs worked that way. And the hours in the office it felt more like fetching up with your wo-corkers. Sometimes we run out of desks, so we went to a desk together. But this rarely did happen.

On the other side there was the customer’s site. These were just large project areas where a huge amount of workers tried to do things. At that time there were no meeting rooms for most of the projects I was involved. We just did the meetings and hinted down the project goals. As this job was exhausting, I did not care about the office, the project room and the open space. I never thought of “you could be more productive if not interrupted all the time” because he just chased down the project road.

In both cases there was a lot of collaboration. Within the companies offices it was like a family, we helped each other and were happy to see each other. At the customer’s site collaboration was formed due to the urgency of the projects. We where firefighters, stormtroopers and the emergency.  Why did it work that way? The project were ingeniously staffed. If these teams would have used offices, the probably would have moved to the hallway to work together. It was a team thing, though.

Everything worked, because it was a limited situation. Everybody was aware, that the projects will end. The situation will change with the next project. So you do not care that much. Also once you left the project, you are not interested much in its future. Also this sounds harsh, one has to face this.

The Team Room

Once I joined a high performing team in a SMB in the software development field. Their location was a team room, applying scrum , QA, ProductOwners and ScrumMaster did live in the same team room. With twenty people it was a crowded place. While doing pair programming, it was a noisy place as well. The setup was fair, tables were separated side by side. But one did not face the pair in front of the table as they have been separated by partitioning walls. Half of the tales have been empty. For bi-weekly sprints you worked on different places, however everybody had its own desk, drawers and so on. It was a fair environment and you felt home, even if it was noisy all the time.

At one point we had to perform deep thinking tasks that took several days and weeks. Major do overs and architectural changes. At that point some of os moved (still as pairs) to smaller rooms. for a limited time to get these tasks done. This was backed by the team as everybody did know, there tasks will not be done right if one is interrupted all the time. Still, other team members came over or you were sitting from time to time in the team room.

As this was not my preferred environment, it worked. The team room was fine, we delivered an unbelievable amount of output and the team played well together. There were a lot of offsite activities by the team members, and still, some years afterwards we meet every year to see each other.

In terms of collaboration, it was very good, as the team worked as such, but there also were individuals who did “their thing”. We had no phones at all, and did almost not use any e-mail. It was simply not necessary as everybody was colocated.

 The Team Lead in the Team Room Fail

Several years ago, I took part in establishing a new development team for a new product as a team lead. We got an small office with one meeting room, a team room and a separated office for the Product Manager and the CEO. First of all, we kicked the CEO out of this office and away from the neighborhood of the developers. Also my desk, which was placed right in front of the developer desks, was removed. I went to the separated office together with the PM. We had to talk a lot and spent a reasonable time  on the phone. I did a lot of PoCs which needed some deep thinking time. Sometimes I did this work from my home office.

The team on the other hand worked together similar as in the situation above. However, it was much more “civilized”. The team was only a fith of the size and everybody was a specialist in his field. Everybody got a huge amount of time for their work without interruptions. This team performed in an outstanding way and produced an awesome output within few months in a exorbitant rate of quality – after I removed my desk out of the team room.

The Virtual Team

When I joined Microsoft I think in 2004, I joined a overall virtual team. Quarterly meetings in a regional office with our managers and from time to time some events. How could one collaborate this way? To make it clear from the very beginning: This was one of the most freaking awesome teams I have ever been with. E-Mails was on a minimum but chatting was always present. I think my chat log where about a Gigabyte. We hacked technology like insane – – always linked to each other. Coordination with management was on a minimum. We had our goals and did everything to reach and regularly to beat them.

Even though we worked everybody for him- or herself, we collaborated in an outstanding manner. The most impressive memory to this team are our come togethers. They were half party half hackathon, there was no or little welcome and no goodby ceremony. We just met, worked and left with a simple, see you tomorrow – knowing we already talk in the chats half an hour from that point on.

At that point we had this idea of mobile blogging restricted to the size of a SMS. We pitched this idea to an Redmond based product manager who told us, this idea has no potential. A few years later, Twitter emerged. Also I do not remember the PM, I really do hope he regrets this moment, every day since then.

Collaboration in this team was on an unbelievable level. There was a goal for the entire team, not for a single member of it. Management played an overall role in this and still, one of our managers is a good friend of mine today.

The Remote Worker

In 2006, I joined Microsoft Research. At the very beginning as software developer as remote worker.  Over time the team grew. We had members from Russia, Spain, Italy, France, Germany, UK and the US. You know what? Collaboration was on a almost all the time high. We had simple rules for the code, few guidelines, a lot of automation and awesome team members. From time to time we met at conferences or events. On a irregular timebase we met in person in Cambridge, UK as flights were cheap to this location.

We used e-mail, chats and video phone calls. At this time Skype was not used, it was even banned, within Microsoft, so we fought to use it. We used almost every technology available. I was on a kind of 24/7 standby as you knew knew if you get a call from any country in the world. In fact I was once called in the middle of the night with the request to remote setup some demos as they were supposed to presented in front of Bill Gates. I did not kew about this until I got the call. So we fixed it. Another Sunday, I got a call from Redmond. It was my architect, telling me that he is preparing a demo for the next day and I broke the build. So I fixed it. Even I never switched off my phone, this was never really stressful. There were goals we worked on (and usually reached them) and there was a high level of collaboration. Again, the team was almost fully virtual.

The Office Day Fail

Right now, I am in product management role, doing a lot of in-house consultancy regarding enterprise architecture. My employer has an awesome policy of all work must be able to be performed from any place. And the same way we have shared desks and a clean desk policy. So far so good, but than again, there is this 20% home office rate as we do not have desks for all employees at the same time. We have open space offices or 8 open floors. Table groups of four everybody facing each other. The open space is supposed to encourage collaboration. However, everyday I see how many of my co-workers just work side-by-side rather than collaborating. E-Mails and Chats are on a all time high, Mails are written and read during meetings. There are many meetings. The places are crowded, it’s noisy and there are endless interruptions.

There is only little deep thinking you can perform. You are just interrupted that often. The most I was able to sit down 360 seconds before being interrupted and being asked “Do you have five minutes?”. I usually have 20 or more of them after such an interruption.

As there is no barrier as an office, the obstacle to interrupt someone is very low. This in fact does include myself as well. I do interrupt people way to often, which I do regret immediately afterwards.

I love being on the phone or doing Skype calls. I hate it in the office. There are thirty co-workers sitting in your neck. Also I do perform really bad in negotiations in an open space. Behind a door – I do really good I think. I just do not want to bother my co-workers to much. It happened to me that I went to a  toilet to do a Skype call for a negotiation just for having some privacy – and to say things only to be said… behind closed doors.

I don’t know how much I perform in open space in terms of coding and architectural decisions. Creativity drops down to a minimum when being afraid of being interrupted any second. On the other hand I come to the office every morning with new ideas. After sitting just for one or two hours in the evening without being interrupted.

My mails suck. Even though I try to avoid writing e-mails, I happens more than once to me that in the middle of the progress of writing, I was interrupted. Once the interruption was over, and the next interruption just queued up, I accidentally sent the mail. With an unfinished sentence in the middle of the unfinished mail.

When I try to write some code (mostly PoCs or demos nowadays) it takes ages. I either do it before the majority of co-workers arrives or later, when most of them have left.

I take my mandatory home office day. I usually get more intellectual work done during this day than in the rest for the week.

Without exact measurements, I feel like in a disruptive environment, I only perform 25% of what I could achieve otherwise.

If I look at the team, everybody works side by side. Almost no collaboration. Excessive usage of communication tool for remote communication and ticketing systems are utilized rather than collaborating.

Is it Only Me?

I wondered if this only for me. No one seems to have an issue with this. Everybody seems to be happy, beside me. Until a few weeks ago.

Two co-workers told me, that If I want to get something done in code, I should join there every-evening.-coding session. So they set up a Skype conference for one or two hours almost every evening where they actually do the new things.

Another co-worker came by with an awesome presentation. He did an overall comparison of platforms. He showed it to us, and showed us a book he worked through. He did during night hours for the last few weeks.

Actually, these are my top developers. I have to wonder why they have to do this during night hours. When they are not disrupted.

And then I read something here:

If your work environment fosters distractions (commonly known as “open space”), a grand majority your engineers will be stressed to the bone, and probably doing 10% of what they can actually accomplish.

tl;dr Conclusion

Also this is my very personal opinion, I had the best collaboration experience in remote teams – workin remote. Not based on working hours. Working on-site was never that awesome.

Good people will probably always sacrify their free time to fetch up disruption at their work place.

But why does remote work rock that much? In my opinion, you can work when you can perform the best. Who says I work the best at 8 am in the office? Maybe “my creative time” is 11 pm to 2 am.

If you set up an remote working environment,  this might not work out for everybody. There are always individuals not providing sufficient discipline for self-responsible work. However, in my experience, if you set up a remote working team, you usually have only team members in it, capable of providing this kind of work.

This might not work for a given team, but should be considered when creating new ones as already Martin Fouler pointed out in his article.

The fact that you can get a better team by supporting a remote working pattern has become increasingly important during my time in the software business and I expect its importance to keep growing.

Based on my experience, remote first teams can outperform co-located teams due to many aspects.

Fingerprints as Security Token

I am still wondering how people can even think of using fingerprints as security tokens. You spread them all over. It’s like writing down your credit card PIN wherever you are.

Therefore, fingerprints a great for identifying you, however, not for authenticating yourself.

Think about it. These are two absolutely different things.

Total Costs of Ownership

If someone can’t let things go because they did cost much money at some point in time, consider the following:

  • What was the value of this item once you purchased it?
  • What would it costs if you had to buy it today again?
  • Would you spend that money for this item today?
  • Do you still use this item or do you keep it just because it did cost money some time ago?
  • What a re the costs of keeping it?

From all thoughts, I propose the latter is the most important. Keeping things does come with cost (time for organizing, time for tidying up,…). If you are not using something at all and probably not using it anytime in the future while you spend time in carrying it from one place to another, there is no rational reason to keep it. Calculate the costs of doing so, and you will realize that the original investment of purchasing it, was only a minor portion of the total costs of ownership