Paolo Amoroso's Journal

Tech projects, hobby programming, and geeky thoughts of Paolo Amoroso

I made a poll on Mastodon asking what's the preferred delivery format for online courses. Although having a mix of formats and material is a good thing, I advised those taking the poll to select the format that best matches their learning style and needs, the one they'd prefer to get the majority of the content in given a choice.

Of the 33 polled users, 55% said they prefer text, 39% video, and 6% audio. Although the sample is tiny, there are a couple of interesting takeaways.

Video is the default format, with many creators and course platforms focusing on or requiring this medium. But I strongly prefer text, to the point video is a deal breaker for me. I suspected I may not be alone, hence the idea of the poll.

The majority of the users who took the poll prefer text like me. This is unexpected, I didn't think there may be so many. Another interesting takeaway is there's a small but significant preference for audio, possibly related to the popularity of podcasts.

I hope this bit of insight will help course creators, who seem to take video for granted.

#misc

Discuss... Email | Reply @amoroso@fosstodon.org

As a geek, I’m excited about the cool tech of the Google Assistant. As a user, I’m frustrated and disappointed.

Localizing Assistant products and features is significantly more complex than translating user interface text and documentation. It requires major development work on core functionality relying on language processing and machine learning. This delays the release of new products and features to countries outside of USA or languages other than English.

By the time an Assistant feature rolls out to Italy where I live, years later and often incomplete, I long forgot about it and don't give it a try.

Even when Assistant features do arrive in Italy, using them is frustrating. My Google Home Mini smart speaker may not understand me or can't do what I want, which happens sufficiently often to discourage further use. Also, potentially useful voice commands have little or no discoverability.

I end up rarely using the Assistant, and only for trivial tasks such as setting alarms or getting weather forecasts.

#Google

Discuss... Email | Reply @amoroso@fosstodon.org

The more I journal with Write.as here, the more I consider abandoning my Blogger blog. Blogger introduces friction, is inflexible, has a stale design, and Google isn't likely to develop it further.

#blogging

Discuss... Email | Reply @amoroso@fosstodon.org

Leanpub announced changes to pricing plans and features, including a membership plan similar to Kindle Unlimited. I'm not sure I like these changes, I need to study them in more depth.

Leanpub is a self-publishing platform focusing on technical and in progress works.

#publishing

Discuss... Email | Reply @amoroso@fosstodon.org

Chrome OS 101 was supposed to prompt to upgrade Crostini, its Linux container subsystem, from Debian Buster to Bullseye. A 9to5Google article on Chrome OS 101 noted:

Linux on Chrome OS now uses Debian 11 (Bullseye) with upgrade prompts available in the Settings app for those on Debian 10 (Buster). You also now get an upgrade log that’s saved in the Downloads folder.

However, when Chrome OS Stable 101.0.4951.59 landed on my ASUS Chromebox 3 with Crostini running Buster, I got no such prompt. A comment by the user Mr. Smith on an About Chromebooks post about upgrading to Bullseye clarified the prompt is hidden behind a flag.

I went through the upgrade process Mr. Smith outlined and it worked, sort of. Here are the steps I took:

  1. enable the flag chrome://flags#crostini-bullseye-upgrade
  2. reboot Chrome OS
  3. accept the prompt to upgrade to Bullseye
  4. open the Terminal app
  5. run the following shell commands:

    $ sudo apt update
    $ sudo apt full-upgrade -y
    $ sudo apt -y autoremove
    

Sure enough, after rebooting the system I got the upgrade prompt, accepted it, and watched a dialog reporting on the upgrade progress. A dozen minutes later the process ended with the following errors:

Failed to connect to bus: No data available
Failed to connect to bus: No data available
invoke-rc.d: initscript sudo, action "restart" failed.
Failed to connect to bus: No data available
dpkg: error processing package sudo (--configure):
 installed sudo package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 sudo
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm not sure what triggered the errors. But a few quick checks of Crostini suggested the installed apps work and nothing major seems broken. Therefore, I'm leaving the container upgraded to Bullseye 11.3 as is and monitor it.

#chromeOS #Linux

Discuss... Email | Reply @amoroso@fosstodon.org

We love their success stories.

They are the creators who made it. The major tech sites, blogs, and podcasts feature these creators as case studies and invite them as guests. Their products make millions of Dollars; their books sell tens of thousands of copies; their newsletters have tens of thousands subscribers; they have huge and engaged social followings.

We sincerely admire these creators, buy their products, share their stories, and genuinely cheer up the success they deserve. But are they inspiring? Is there anything we can learn from them and apply to our creative journeys?

Not for me.

These successful creators feel distant and hopelessly unreachable. They seem closer to the fictional heroes of the movies and novels I love than to actual people.

My impression is these creators have something I don’t and can’t have. They are outliers, unicorns. Experienced professionals with unique skills and high-demand products that nail a niche, as well as massive, existing audiences with “buy first, think later” raving fans.

These creators discuss how they designed their landing pages and dissect the growth hacks they implemented. But my impression is they are so talented, charismatic, and well known they could have launched their products any other way with the same outcome.

They could throw anything at the wall and it’d still stick. Yes, they started from zero. But their talent blasted them to where they are.

Instead, the stories that inspire me most are those of the underdogs.

The lesser known, ordinary folks at the other end of the spectrum. The creators who sell a few hundred copies of a book; make a few hundred bucks or so per month off their creative work; publish newsletters with a couple hundred subscribers; and have fewer than a few thousand Twitter followers. Those who earn enough to pay a bill or two or buy a new laptop.

These underdogs show the way to realistic, rewarding goals within reach with reasonable effort in the short to medium term. Not in a lifetime of sweat, creative drive, and luck.

#misc

Discuss... Email | Reply @amoroso@fosstodon.org

Although Linux had been my daily driver for almost two decades, when I switched to Chrome OS I regarded the Crostini Chrome OS Linux container mostly as a curiosity.

Sure, I was eager to have some fun with Linux on my Chromebox. But I already lived fully in the cloud and web apps met all my computing needs. I assumed the main use cases for Crostini were advanced development or DevOps.

To check out Crostini, I installed some astronomical image visualization and processing software for Linux. Next, I used Python preinstalled on Crostini to test the code I was writing with Repl.it and make sure it ran on a different system.

When I began working on Suite8080, a suite of Intel 8080 Assembly cross-development tools in Python, I needed some CP/M emulators and 8080 tools to test the Python programs I was developing, as well as my Assembly code. Again, installing and running such Linux software on Crostini worked well.

I came to love Crostini, now a key component of my Chrome OS toolset. It lets me run all sorts of niche applications and specialized software for my hobby projects and geeky interests.

#chromeOS #Linux

Discuss... Email | Reply @amoroso@fosstodon.org

I'm among those who think the best camera is the one I carry with me.

There's no grand scheme motivating my choice not to get a traditional camera, using instead my smartphone for on the go and travel photography. It's hard to beat a compact and light device I always have handy.

In my trip to Florida to view a rocket launch from Kennedy Space Center, I took photos with my current smartphone, a Google Pixel 4 XL. Its camera recorded the two rocket launches I ended up viewing, the space facilities and museums I visited, and general travel photography.

How did the 4 XL camera fare?

Distant subjects and rocket launches

Despite having been released almost three years ago, the 4 XL still holds up well.

The camera works best when the subjects fill most of the frame. But my daylight photos at Kennedy Space Center show also good detail of distant vehicles, such as the Crew-4 Falcon 9 rocket at launch complex 39A and the SLS rocket at 39B. The photos bring out also enough detail of the daylight Starlink 4-14 launch, despite the dynamic action and the high tonal range difference between the rocket structure and the bright exhausts.

The 2X optical zoom helped make distant subjects large enough to reveal detail better. However, I wish I had a latest generation flagship device with a more powerful optical zoom to enlarge those subjects a bit more.

Night launches

Where the 4 XL camera fell short is with night photography of dynamic events.

My photos of the Crew-4 night launch didn't record much light to reveal the complex detail and delicate tones of the exhaust plume of the ascending rocket. At that point, the booster was too far and not lit enough to show any detail.

As for the launch itself, from when the rocket engines ignited to when the booster cleared the tower and began ascending, the performance of the 4 XL was similar to that of the newer generation devices the friends who traveled with me used. In my photos, the ascending rocket looks like a saturated blob of light. The tonal range was so high, with the black background of the night sky contrasting with the blinding rocket exhausts, that not even recent smartphones may adequately capture and present it.

Wide-field photography

This travel experience with the 4 XL camera made me change my mind on lenses.

I thought a wide-angle lens wouldn't be useful to me, as I don't do much landscape or people photography, and preferred a lens with optical zoom.

However, by shooting photos at Kennedy Space Center, I realized that, without a wide field of view, it's hard to frame large and close objects in full — or nearly in full — without cropping. A wide field lens would have come in handy, for example, to shoot the Atlantis Space Shuttle or the Saturn V. You can come very close to these vehicles, which is a challenging observation point for framing.

#Android #space

Discuss... Email | Reply @amoroso@fosstodon.org

From April 18 to 28, 2022 I traveled from Italy to the Space Coast, Florida, to view the launch of the Crew-4 space flight from Kennedy Space Center. I was with a group of good friends the Crew-4 crew member and ESA astronaut Samantha Cristoforetti invited as her guests.

Rocket Garden at the Kennedy Space Center Visitor Complex

The odds of this once in a lifetime trip were against me.

A few weeks prior to the departure, my old mom was hospitalized and her condition raised some concerns. Also, the Crew-4 launch date kept slipping due to the delays of the higher priority mission Axiom-1, which made the margin of our stay grow increasingly thinner.

But we made it.

Not only did I join the trip and viewed Samantha's launch, but also made incredible experiences, visited great space facilities and places, took lots of photos, and met wonderful people.

Thinking back to the trip, once more I want to go over the major things I saw and experienced.

The Crew-4 launch

Samantha's spectacular night launch on April 27 was the highlight of the trip.

The Falcon 9 rocket blasted off on a clear starry night. At the Banana Creek viewing site we managed to follow the booster in the sky through the second stage burn, and spotted the eerie reentry burn of the first stage heading for a landing on a droneship in the Atlantic ocean.

Meeting Samantha

A few days earlier, on April 21, we had a lot of fun meeting Samantha and her crew less than half a chilometer away from her Falcon 9 rocket on the pad, at launch complex 39A of the Kennedy Space Center. It's the same historic pad where the Apollo missions left for the Moon.

NASA calls the experience “wave across the ditch”.

It's a traditional, intimate outdoor event where the astronauts meet the joyful crowd of their families and friends a few days prior to the launch. The quarantined astronauts remain half a dozen meters away from the guests.

Kennedy Space Center

Touring Kennedy Space Center gave many opportunities to us space geeks.

In those days of April of 2022, the giant SLS rocket of the Artemis I lunar mission was on the pad at launch complex 39B for a wet dress rehearsal test. Our closest view was from pad 39A at the wave across event.

Speaking of giant space stuff, at the Kennedy Space Center Visitor Complex and nearby area we came up close with the Space Shuttle Atlantis orbiter, a Saturn V rocket, a crawler-transporter vehicle in motion, and the Vertical Assembly Building (VAB) we viewed from the press site.

Prior to Samantha's launch, on April 21, we were lucky enough to score a bonus launch. We viewed the daylight launch from complex 40 of a Falcon 9 carrying the 4-14 batch of SpaceX Starlink satellites.

On April 24, the recovered first stage of that Falcon 9 booster was back at Port Canaveral where it had been hoisted by a crane. The following day we had great views of the recovered booster, the payload fairings, the droneship, and a support ship from both the ground and a helicopter ride. Amazing sights.

The Endeavour Dragon capsule of Axiom-1 finally splashed down in the Atlantic ocean on April 25, thus clearing Crew-4 for launch, and was carried to Port Canaveral aboard a support ship. The same day we went to the port for a quick look at the capsule and the ship.

More space places

There were other geeky space places we visited both at Kennedy Space Center, such as the Rocket Garden and the Heroes and Legends museum, and elsewhere. For example, we spent a lot of time at the American Space Museum in Titusville, and briefly peeked at a site near Cocoa where SpaceX did early assembly work on Starship prototypes.

The people

The human side of the trip was as unique and rewarding as the space-related experiences.

We met Samantha and her family at private events; geeked out with other ESA and NASA astronauts; cheered with Samantha's guests at the launch; watched on TV with them and Samantha's family her arrival on the International Space Station; shared meals with friends who live in the area and work in the space program or are space enthusiasts.

Down to earth

Although the trip was unforgettable, we had a poor air travel experience. But we were incredibly lucky and ejoyed a fine weather despite the full Florida spring.

When in October of 2007 I viewed the STS-120 Space Shuttle launch at Kennedy Space Center, as a guest of the crew member and ESA astronaut Paolo Nespoli, I hoped I would live a similar experience again.

Fifteen years later, mission accomplished.

#space

Discuss... Email | Reply @amoroso@fosstodon.org

What I anticipated and planned for is happening.

After the great momentum of the initial work on Suite8080, I set it aside for a couple of months. Now I'm about to resume work on the project and wonder how hard it'll be to dive back into the Python code and continue development.

I tried to prepare for this by documenting the system and commenting the code. I also took many notes on to-do items, features I'd like to add, and ways to implement them. At a few thousand lines, the code base is small and I hope it won't be too difficult to understand and change.

Still, I'm a Python beginner and my code is tightly coupled, fragile, not modular, and hard to extend.

Suite8080 is a suite of Intel 8080 Assembly cross-development tools I'm writing in Python.

#Python #Suite8080

Discuss... Email | Reply @amoroso@fosstodon.org

Enter your email to subscribe to updates.