949 karma · joined October 14, 2014
[ my public key: https://keybase.io/wrigby; my proof: https://keybase.io/wrigby/sigs/MdiYCR9-ieNbkrRSq38cl5kTsYb0FPgkJhNFC0C0ZWA ]
See also: https://en.wikipedia.org/wiki/Celebratory_gunfire#Injuries
“Roderick Beck worked as a sales contractor for Hibernia Atlantic and helps buyers procure capacity and providers make sales.”
In the terrestrial real-estate analogy, this seems to me like missing out on potential returns because you built the wrong type of building on the land you own.
The thing that struck me is that they operated more like real-estate investors than tech companies. Geostationary satellite technology had remained largely unchanged for a couple decades, so these companies were engaged in the business of:
- Obtaining real estate (an orbital slot) - Putting a big, expensive, largely commoditized[1] asset on that real estate - Operating that asset as efficiently as possible to achieve a good ROI
This meant that the executives were often stronger at things like financing hundred-million dollar purchasing projects (a huge skill on its own) and running a skeleton technical operations staff (to keep OpEx down), but lacked the foresight to see what the Internet meant for their product relevance.
1: Of course something as technically complex as a spacecraft isn't a commodity, but there was largely no differentiator in what it _did_: receiving, shifting, and re-transmitting analog RF signals, almost always in 36 MHz and 72 MHz wide chunks. You could buy one from Thales, Lockheed, Boeing, etc., but to the operator's customers, they all basically looked the same.
It’s definitely better to have the bag with me, and just typing this out made me realize I can keep one or two in my backpack at all times.
Tangentially, this isn't really new - ground-pointed RADAR system combined with a good terrain dataset can also be used.
1: ADuM1201 - https://www.digikey.com/en/products/base-product/analog-devi...
QLab was the least painful part of getting sound and lighting integrated. If the lighting system we used (Madrix) was half as easy to work with as QLab, I’d get dozens of hours of my life back.
These are used in disaster response and other scenarios that demand rapid deployment of satellite terminals.
Ka-band (18-30 GHz) used to be the new frontier for satcom - it was what everyone was excited about the last time I worked in the industry (2014). The advances in mm-wave devices over the last decade are mind boggling.
-Werror=format-securityFrom what I remember, it wasn’t intended as a long-term position, but was used in stop-gap circumstances (manager quits, tech lead temporarily takes on some people management duties) or for when an engineer was considering transitioning to the management track.
Recently, I needed to ramp up quickly on an embedded C project (without any past MCU programming experience), and turned to a book for the first time in ~15 years. It was a refreshing experience - it was a short book, and I read it cover to cover over a weekend, but it really enabled me to be successful in the project I had to take on.
I like to think of real-world experience as building a sponge: you fill in the areas that you need to as you go, creating a sparse structure of knowledge. This complements formal training (whether a book or a class) - I think of these more "complete" approaches as pouring water into the sponge. Having hands-on experience lets you take more advantage of a class or book, and the class or book fills in the gaps that you simply didn't have to learn as you built things.