I have been repeating this sentence more often than I’d like recently. But if the COID-19 time has taught me one thing very impressively, it is:
Rule 1: Forget rules which you cannot control or enforce
(Alternatively: “Do not hope for the sanity of your colleagues / fellows / …”)
Many of the COVID measures would certainly not have been necessary if “we all” had behaved reasonably. One could discuss the term “reasonable” right away. But “reasonable” unfortunately depends on personal goals. If the personal goals diverge, the opinion about “reasonable behavior” diverges as well. And suddenly “we all” do not have a common sense of what “reasonable behaviour” is. This discrepancy is then what is called a “conflict.”
So, if you are responsible for a system (the system does not even have to be technical – the “health care system” e.g.), you can hope for the sanity of the involved participants (users) and not impose any constraints / rules … This will most likely lead to a conflict. If the conflict has to be solved, you will generally be confronted with utmost gratitude and boundless cooperation (this was ironic, by the way).
No problem: just set up some rules … But rules only do make sense if you can control and enforce compliance with the rules. Because … honestly whenever we discover an inconvenient rule, we want to circumvent it. And we are creative 🙂
Rule 2: Only make rules whose compliance you can enforce and control.
If you find yourself in a position where you can detect a violation of a rule but cannot (anymore) react (or only with enormous effort). You are on lost ground and can do nothing but watch.
Rule 3: It should be clear to everyone how the enforcement will be done.
Rule 2.5: This is transparency.
The 3 rules sound trivial … but can also be very unpleasant if you have to write them down and communicate them. On the other side, you will have certain displeasure right away, but not later (or at least less because the rules were clear from the beginning). A user, on the other hand knows what (s)he is (not) allowed to do. And if there is the transparency about the consequences, the user can also decide for him-/herself whether to break a rule or not – but one cannot complain.
Many companies and executives thought COVID-19 and 100% HomeOffice would be a real challenge. Phew seems a lot of companies survived the Home-Office challenge! Companies have learnt that the business can continue. Employees have learnt that HomeOffice can work.
This was challenge 1: the technical challenge.
But now as companies slowly do not have to do HomeOffice anymore … now we will see what our bosses, executives and companies really think. How much they have really learned. How much trust there really is.
Now comes challenge 2: the people challenge.
The challenge might now be to keep people when a leader (or worse: a company culture) values presence (a.k.a counting sheep) over results – but employees don’t …
I’ll just stay at home and stay productive.
“Every employee should feel encouraged to give feedback and contribute ideas for improvement!” Who has heard this before? Probably everyone!
My (slightly provocative) opinion: “The effect was probably close to zero. So Forget it and don’t do such a shout out!”. Unless you want nothing or barely anything to change. Then do a big shout-out and send people back to work! Great show – with no effect! Of course, I made the mistake myself and didn’t notice for quite a while (years, actually). Every now and then an idea or suggestion came along (or I had one myself) and we were proud of the improvement. At some point between Retros and PostMortems I got the point: “It needs the right framework!”
Why are there retros for projects / sprints / teams / …? Why are there PostMortems? What’s the justification to do them? Not because of the “new fancy agile stuff” where you “just do it that way”, but because it pays off – it works. Because it provides a framework for discussion. Because time is explicitly reserved for the questions: “What can we do better?”, “Why did […] happen?”, “How can we prevent […] from happening again?”
And within this “frame” – that reserved time – people really find the time and opportunity to express ideas. Or just explain some tedious tasks that should be improved because they are … tedious. In this reserved time, there might come more ideas than in the days and weeks before. Than in the time where people are permanently confronted with the problems – where one actually could already come to the conclusion that there is potential for improvement. And maybe also more complex ideas, which people just can’t “simply do” besides regular work. Complex ideas which need a little time to be explained, discussed and understood.
If you want something to run better, the call for improvement is a step. But only one step. So the next step is: Okay, get all people together that are concerned and willing to contribute. Let’s have a look at the bugs/whatever… of the last weeks. Where are do issues pile up? Where do we ALWAYS do the same thing over and over again (“Toil” in SRE Speak)? What’s annoying? Do we have data with which to raise an assumption to a fact (that makes prioritization ways easier)?
And then the essential points: Derive actions, evaluate and implement! And do it on time! Otherwise, any motivation is not only gone, but it is immediately learned that nothing happens anyway.
All this is time-consuming, tedious, inconvenient and also annoying when you have to prioritize the actions against other tasks … But … it brings value. – So if you want to improv: Don’t just ask for feedback.
Deleting folders with a huge amount of files can be tedious in Windows Explorer: You might end up in watching a progress bar preparing and deleting a lot of files. Even if you don’t want the files to be moved to trash.
If the files should just be deleted, this can be done easier with the command line:
DEL /F/Q/S *.* > NUL
RMDIR /Q/S foldername
A lot of explanation / evaluation and even a Context-Menu-Shortcut can be found at this Ghacks article.
When you own both a Samsung Soundbar (HW-[something]) and a Samsung Smart-TV, you would assume that they work in nice harmony. Which they usually do! Just once in a (seldom) while, the both just don’t connect any more and it seems there is no way to connect them again.
Recently we ran into the same trouble. It required a lot of forum reading, searching, reading support pages. Especially as it requires sound-resetting both devices and does not require hard-resetting the TV (loosing channel list, favourites et. al). As it was a real pain to figure it out, I wrote down my process.
The following steps worked for me the last time I had to try it.
- Soundbar (maybe this is not required?)
- turn off
- press (and hold) the stop button until the soundbar displays “init, ok”
- Remove soundbar from the config:
Menu > System > Device manager > Soundshare > remove Soundbar
- turn off the TV
- disconnect from power
- wait ~3 min
- reconnect & power on
- Power on
- switch to TV mode and wait for connection
- MAYBE reset soundbar: press & hold “play” until it displays “reset”
Hope this helps! Leave a comment if it helped you or if there’s a faster way to reconnect both devices.
I’ve been waisting some hours by hunting a stupid “bug”:
I am using Android Studio and was following the “Maps SDK for Android > Getting Started” guide. Of course I also ran into the issue of a wrong API key. But this was all solved by Googling and StackOverflow.
The map still showed up in the Emulator but NOT if deployed as stable release into the (beta) release channel to the PlayStore! LogCat was also silent … After a while I realized thetiny hint in AndroidStudio:
The light grey “(debug)” tells us that AndroidStudio placed the XML in “src/debug/res/values/” instead of “src/main/…”. Simply moving the file did the trick …
RaspberryPi mini computers are great for all kinds of home automation, media centers, home servers. Yet it should be known that the draw back for permanent operation can be the SD-card. Especially when applications on the RasperrbyPi cause excessive read/writes or if it is used outsides where temperatures can reach the SD-Card operating limits, IO errors should be expected that can just f* up the operating system.
Continue reading Space effective backups of Raspberry Pi SD-cards
Tvheadend is a TV streaming server and recorder for Linux. It also offers a great possibility to combine a SAT-recorder with KODI mediacenter on a Raspberry Pi (I would recommend a raspberry Pi 3 due to RAM requirements).
Installing Tvheadend by compiling from source was not so easy, so it is definately easier to install via precompiled packages. In order to do so, the following steps are required:
Continue reading How to install TvHeadend on a Raspberry Pi
Using HTTPS on Tomcat with a let’s encrypt certificate is quite easy – as soon as you know how to do it (as usual). acme.sh provides a quite convenient way of getting and renewing certificates. This is extremely important as the certificates have a lifetime of just 60 days.
So get and “install” acme.sh first! And make sure Tomcat is running on port 80. Then start getting your certificate:
Continue reading Let’s Encrypt with Tomcat 7
A standard Tomcat installation starts the webserver on port 8080 – which is usually not the desired behavior. In order to change the server to port 80 there are two options which I outline in the following:
Continue reading How to run Tomcat on Port 80