No more joy in writing software. Instead my time is spend in writing user stories and specifications as good as possible.

Migration isn't easy, as this venerable application uses ADO.NET Datasets with TableAdapters and plenty of stored procedures. The syntax is almost compatible though. But not enough unfortunately.

For our next product, we're sure to bet on PostgreSQL instead.

(yes, a successor is planned, but it will be a huge amount of work)

I drive a Tesla Model 3 daily and agree to the critism about it's interface. On my last holidays I rented a Suzuki Vitara. Indeed it's much easier to find and operate the standard controls like for climate. Also cruise control with its 6 buttons took only a little learning.

The worst turned out to be CarPlay, a feature I always thought I'm missing with my Tesla. Occasionally it just didn't work, even though the phone was connected. So you get no navigation or you stop/start/wait until it works. And repeat that after every car stop situation. And when it works, forget about zooming or seeing anything more than the next step on this tiny display.

All in all I was happy to return to my Tesla again. But then I know all important controls from memory.

Anyway: Analog cars ruled indeed. I'd just use a simple phone holder too rather than anything like CarPlay.

I'm a huge XPS15 advocate at work and really love these machines as a Windows developer. But the standby just doesn't work. If I close the lid and throw it in my bag, then the battery will be empty and the bag will be hot as hell. This is a huge failure and makes me shutdown my XPS15 every evening. Which is just nonsense. I'm a Mac user at home and just never shut these laptops down ever.

https://de.wikipedia.org/wiki/Stadtbach_(Aare)

Started as a Windows line of business software developer almost 20 years ago. At first we got clear specifications with UI mockups and a description what each and every button should do. When there were questions, these specs where updated and we implemented and tested and fixed until our boss was happy.

Over the years we got more and more customers yet less and less time for tests and fixes. So we switched to "agile" and dropped the specs, instead wrote quick notes about what must (roughly) be done. At first all were happy. But now we have a huge amount of features that not one dev knows. You have to ask and search around until you find all the lose specs.

Now I'm managing such a team of developers and have the same issue. I don't have the time to write a clean specification, yet alone discuss it with the actual customer, which anyway doesn't really understand all the implications. So they start coding by adding more if and else blocks to an already bloated code base.

Pity the days we would start with a class diagram or just some quick drawing about how the components would interact and be testable.

Make sure to get also Super Mario Odyssey. This game is just such a joy. It feels like a trip to a funfair every time.

And sure, Mario Kart 8 for some multiplayer fun.

6 years in, and the Switch is still the most used console in my family with 3 kids.

But Shrinking is really worth watching.