Feed

Reactions, reposts, notes, webmnetions
#linkedin

Agile clown show // Linkedin

The Agile coaching industry has become a parody of itself because of #agileclownshow, using buzzwords without actually providing any substantial value. It's as if they claim to know the solution to a problem but have no understanding of the problem itself. The issue with Agile coaching is not just the lack of expertise, but also the audience and those in charge. Just as a teacher must have experience in a subject to effectively teach it, an Agile coach must have experience in the business world. Simply put, they must have a track record of producing results, both positive or negative, before they can effectively coach anyone. If not then red nose and fancy hair should be the working suit.

Even more horrible is the fact that agileclowns make new agileclowns each show performed.

Link @ linkedin
#linux, #virtualbox, #kernel

How to sign VirtualBox kernel modules when you're on secure boot

When you’re installing VirtualBox on a system with Secure Boot enabled, the installation process requires kernel modules to be loaded that are not signed by the system’s Secure Boot key. In this situation, you have two options:

  1. Disable Secure Boot in BIOS: This option involves going into the system’s BIOS settings and disabling Secure Boot. This will allow the installation process to proceed without any further intervention.

  2. Sign the kernel modules: If you prefer to keep Secure Boot enabled, you can sign the required kernel modules with a key that is trusted by the system’s Secure Boot infrastructure. This involves generating a new key pair, importing the public key into the system’s key store, and using the private key to sign the kernel modules.

Create new key and enroll it with MOK

1
2
3
4

sudo mkdir -p /var/lib/shim-signed/mok
sudo openssl req -nodes -new -x509 -newkey rsa:2048 -outform DER -addext "extendedKeyUsage=codeSigning" -keyout /var/lib/shim-signed/mok/MOK.priv -out /var/lib/shim-signed/mok/MOK.der
sudo mokutil --import /var/lib/shim-signed/mok/MOK.der
sudo reboot

Sign modules with new Key

1
2
3
4
5
6
7

#!/bin/bash 
for modfile in $(dirname $(modinfo -n vboxdrv))/*.ko.xz; do
     echo "Signing $modfile"
     /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 \
             /root/signed-modules/MOK.priv \
             /root/signed-modules/MOK.der "$modfile"
done

The steps you’ve outlined above describe how to perform the second option. The script you’ve provided will sign all the VirtualBox kernel modules that are present on the system. Once the modules have been signed, they will be allowed to load by the system’s Secure Boot infrastructure.

It’s worth noting that signing kernel modules is a security-sensitive operation, and you should take appropriate precautions to protect the key material. Also, the exact steps for signing kernel modules may vary depending on the distribution and version of Linux you’re using.

Done.

#rant, #slack, #teams

Teams vs Slack

Slack has become the industry standard for modern developers’ communities, but Microsoft Teams has emerged as a challenger. However, what exactly does Teams offer, and why is it considered inferior?

The main reason is that Teams did not commit to conducting research on what is needed to facilitate effective communication in a rapidly growing environment. This lack of attention to detail is evident in certain elements of the interface.

Let’s start with the roster, which is a list of available chat entities and users. In Slack, it is streamlined and designed with use cases in mind, while in Teams, it is merely a simulacrum.

For instance:

  • In Slack, finding a chat only requires one click, while in Teams, you need to switch between group chats and private chats, which can be slow.
  • Slack has a well-designed interface for threads, making them easy to see and use. In contrast, Teams has a bloated and poorly functioning mechanism that is difficult to use.
  • In Slack, there is one roster for all chats, while in Teams, there are several different rosters for everything, which does not aid productivity.
  • The chat window and input area in Slack are simple yet sophisticated, while in Teams, they are overly complex and confusing.
  • Code pasting is impossible to do smoothly in Teams, whereas Slack allows for seamless pasting by simply inputting standard markdown backticks. Additionally, Teams do not differentiate between one backtick and triple backticks and does not change highlighting styles.
  • After pasting a message in Teams, the interface can cause the message to appear out of order and even before the previous message.

So why is Teams inferior to Slack? The main reason is that Teams has not invested enough in conducting research and designing an interface that is user-friendly and efficient. Slack, on the other hand, has a well-designed interface that is tailored to the needs of developers, making it the preferred choice in the industry.

Although I am not an advocate for Slack, I believe that Teams is a subpar platform that is not yet ready for production use. While it has many integrations and functionalities, it appears as though they were simply created to imitate Slack and give the impression that “Yes, we have that too.”

#rails, #dev

Rails 7 introduce default healthcheck controller

DHH introduce default HealthCheckController for Rails 7 ♦

Which is just this piece of code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

# frozen_string_literal: true

class Rails::HealthController < ActionController::Base # :nodoc:
  rescue_from(Exception) { render_down }

  def show
    render_up
  end

  private
    def render_up
      render html: html_status(color: "green")
    end

    def render_down
      render html: html_status(color: "red"), status: 500
    end

    def html_status(color:)
      %(<html><body style="background-color: #{color}"></body></html>).html_safe
    end
end

PR https://github.com/rails/rails/pull/46936

#blog

Change colorscheme for code blocks highlighting

Code here is highlighted with https://github.com/mzlogin/rouge-themes1, I changed scheme a bit, now it looks brighter.

Here is the Python method example

1
2

def python():
    puts("Python method example")

Thats for Javascript

1
2
3
4

function test() {
    let sh = 1;
    console.log(sh);
}

PHP

1
2
3
4
5

class Testing {
    function __constructor() {
        $this->a = date('r');
    }
}

Rust

1
2
3
4
5
6
7

fn main() {
    // Statements here are executed when the compiled binary is called

    // Print text to the console
    println!("Hello World!");
}
#persons, #cars

Ken Block(43) R.I.P.

Ken Block dies due to snowmobile incedent

Kenneth Paul Block (November 21, 1967 – January 2, 2023) was an American professional rally driver with the Hoonigan Racing Division, formerly known as the Monster World Rally Team. Block was also one of the co-founders of DC Shoes.[3] He also competed in many action sports events, including skateboarding, snowboarding, and motocross. After selling his ownership of DC Shoes, Block shifted his business focus to Hoonigan Industries, an apparel brand for auto enthusiasts. He was the co-owner and “Head Hoonigan In Charge” (HHIC) at the company before his death.[4]

He starting being widely famouse by this Gymkhana series and here is how to starts and progress:

There are many more on Hoonigans channel, take a look if you’re fan of Rally kind of staff.

More of him can be found on Wikipedia.

https://en.wikipedia.org/wiki/Ken_Block