When looking for a nice design the colour palette is one of things I usually fail epic.
Lospec is a website providing a pixel editor, pixel art tutorials and more important to me some hundreds of colour palettes based on a wide range of 8- and 16-bit games.
The Lospec Palette List is a database of palettes for pixel art. We include both palettes that originate from old hardware that could only display a few colors, as well as palettes created by pixel artists specifically for making art. All palettes can be downloaded and imported into your pixelling software of choice
I like using these palettes when creating a logo (also I am not good in this discipline) and presentations when not bound to any corporate identity.
The palettes can be downloaded as png image or even as Adobe Photoshop, Paint.NET or GIMP file to be used in your favorite application.
I told last post about setting up a streaming project. I usually do this to set myself a deadline. And it worked.
During the last few days, I set up my Twitch account, created a YouTube brand, and started my first live stream. During the first evening, I did set up the Website using Ansible and Docker in my first three hours live stream. I also tried a second stream with my s***y headset and even managed to record it and throw it onto YouTube. I have to apologize for the bad quality, but I am still learning.
I learned a lot about filters and hardware, are still looking for a schedule and how to manage this whole setup. I probably start streaming frequently in September.
For streaming and recording, I decided to use OBS Studio. There are some alternatives out there as well as some variants with various extensions.
I have set up a hardware wish list at Amazon (Hey! Sponsors where you?) as this is an educational and non-commercial project. Altogether it has been a busy week but a huge part of the infrastructure is in place, including a lot of learning but also failing.
Next step: I am starting chatting about the podcast. Maybe this will start soon as well.
Said that there was a major decision I had to make. All content created for and provided by Hack-The-Planet TV will be solely in German. The audience in the first place are students of mine speaking German most of the time. Also, there is a lot of content in English already available, Much more than German. But I see and feel the need for content in their first language.
I have struggled with this idea for a while. Meanwhile, I live in the countryside. I have to drive 45 minutes to the next city. It’s quite a distance. And I have a toddler. Two, there will be soon. Consequently, it is not that easy to quickly join a Meetup or User Group meeting in the evening. And I miss talking to other techies. Kids change you live. Especially if you are a nerd, geek, and techie.
In addition, I will start a new position in September 2019 as a professor for Software Engineering. I will cover all the hot shit topics like DevOps, Cloud Computing, maybe some Big Data stuff and basically everything that will come along in the future.
Teaching at university, however, is old school. Platforms like Coursera and others are nothing else. It’s just old school (but online, yeah). So I have a plan. I will try to make things different. I will meet my students (and probably a lot of other folks) in the world I grew up and still live. Here. Online.
What do I do? Rising Geeks! Teaching computer science and software engineering by day, I will do the fun parts not covered in the official curriculum by night.
We’ll do Let’s Plays, Let’s Codes and just talk. I teach in German, and so the overall Project will be in German. Sorry to you all out there as you’ll miss the best parts.
While this is going to be a challenging project I want to cover a couple of things:
Streaming: I’just started my Twitch channel HackThePlanetTV. I’ll be working on a schedule. I plan to stream once a week. I have to figure out a schedule. Until then I will rather stream occasionally. Apologize for the short notice in the near future.
Let’s Code: Not only but also in the streams, I want to cover typical problems you are taught at university. I’ll do live codings with whatever technology and other stuff – record these and put the videos online.
Open Source: I’ll try to put as much as possible everything OSS. Therefore, everything will end up on GitHub.
Podcasts: I commute a lot. I enjoy listening to podcasts. I’ll try to set something up where we (currently looking for to with whom I’ll team up) talk about all the geeky stuff creating an own podcast.
www.hack-the-planet.tv: Of course, I will try to host as much content as possible by myself. Therefore, during my first stream, I have set up my own web presence for the project: www.Hack-The-Planet.tv
And now you probably think: Why the heck is he doing this? I used to be a developer, architect, I run my own business, I was a team led and spend the last five years as a product manager. I got bored with engineering stuff. In was challenged by a higher manager, if I would do my job if it would not be necessary to earn money. That’s like living in the Star Trek universe. So I quit my job. I don’t think he is aware of what he caused by his question. I went to university to teach. I started to teach the kids to get well-paid developers. And I want to do the fun stuff.
For the last couple of years, I have seen many so-called “architecture” diagrams including those suffering from inconsistent notation, unclear depiction lack of information and ambiguity.
The worst scenario was in my last role, where I dealt with company-wide application integration. Each and every team had their own way to draw (or not to draw) security architectures. Guidelines? Nope. Nervous breakdowns n a daily base if something went wrong? Definitely.
So he/she who’s name is not known created a quite comprehensive PDF guideline which helps you to draw more precise security related architectural diagrams. Definitely worth a look.
Being inspired by the dev.to articles ( do cross-post some of my dev related articles here), I really liked the estimated reading time on top of each dev.to article. To me, it is very valuable, as most articles < 3 minutes I do read instantly, while larger posts I put on my reading list.
Eventually, I added this information also on every post on this blog to the convenvice of my readers. I hope this i as helpful to others as it is to me.
As Visual Studio Code became my main editor, I often have more than one VS Code window open. This gets confusing after some time. To keep track in which project you are currently working, I thought of using different color themes by project.
As usual, once you know the trick, this is quite easy. Navigate to File / Preferences / Settings and select the Workspace tab.
The setting for the Color Theme you choose here will be used whenever this particular folder is opened. That way you can easily distinguish between open Visual Studio Code windows.
Simon Brown -inventor of the C4 model – recently came up with a checklist about diagrams and notations.
A few people have asked me for this recently so … if you’re looking for my software architecture diagram notation checklist, you can find it here…
Although it seems obvious what is checked in this list, almost every single diagram I have encountered in my career did not provide all the information. Copy it, print it, as an architect (and software developer) carry it with you – and use it.