<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/">
  <channel>
    <title>Opinion</title>
    <link>https://www.linuxjournal.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Lessons in Vendor Lock-in: Shaving</title>
  <link>https://www.linuxjournal.com/content/lessons-vendor-lock-shaving</link>
  <description>  &lt;div data-history-node-id="1340204" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;Learn how to embrace open standards while you remove stubble.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Freedom is powerful. When you start using free software, a whole world opens up
to you, and you start viewing everything in a different light. You start
noticing when vendors don't release their code or when they try to lock you
in to their products with proprietary protocols. These vendor lock-in techniques
aren't new or even unique to software. Companies long have tried to force
customer loyalty with incompatible proprietary products that make you stay on an
upgrade treadmill. Often you can apply these free software principles outside
the software world, so in this article, I describe my own object
lesson in vendor lock-in from the shaving industry.
&lt;/p&gt;

&lt;p&gt;
When I first started shaving, I was pretty intimidated with the notion of a
sharp blade against my face so I picked the easiest and least-intimidating
route: electric razors. Of course, electric razors have a large up-front cost,
and after some time, you have to buy replacement blades. Still, the shaves were
acceptable as far as I knew, so I didn't mind much.
&lt;/p&gt;

&lt;p&gt;
At some point in my shaving journey, Gillette released the Mach 3 disposable
razor. For some reason, this design appealed to a lot of geeks, and I ended up
hearing about it on geek-focused blogs like Slashdot back in the day. I decided
to try it out, and after I got over the initial intimidation, I realized it
really wasn't all that hard to shave with it, and due to the multiple blades and
lubricating strip along the top, I got a much closer shave.
&lt;/p&gt;

&lt;p&gt;
I was a convert. I ditched my electric razor and went all in with the Mach 3.
Of course, those disposable blades had the tendency to wear out pretty quickly,
along with that blue lubricating strip, so I'd find myself dropping a few
bucks per blade to get refills after a few shaves. Then again, Gillette was
famous for the concept of giving away the razor and making its money on the
blade, so this wasn't too surprising.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
We're Going to Four Blades!&lt;/span&gt;

&lt;p&gt;
The tide started turning for me a few years later when Gillette decided to
deprecate the Mach 3 in favor of a new design—this time with four blades, a
lubricating strip &lt;em&gt;and&lt;/em&gt; a rubber strip along the bottom! Everyone was supposed to
switch over to this new and more expensive design, but I was perfectly happy
with what I was using, and the new blades were incompatible with my Mach 3
razor,
so I didn't pay it much attention.
&lt;/p&gt;

&lt;p&gt;
The problem was that with this new design, replacement Mach 3 blades became
harder and harder to come by, and all of the blades started creeping up in
price. Eventually, I couldn't buy Mach 3 blades in bulk at my local warehouse
store, and finally I gave up and bought one of the even more expensive new
Gillette razors. What else could I do?
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/lessons-vendor-lock-shaving" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 12 Dec 2018 12:30:00 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1340204 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Thinking and Working Outside the Platform</title>
  <link>https://www.linuxjournal.com/content/thinking-and-working-outside-platform</link>
  <description>  &lt;div data-history-node-id="1339757" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
On the one hand, &lt;a href="https://news.google.com/news/search/section/q/facebook?ned=us&amp;gl=US&amp;hl=en"&gt;Facebook is on fire&lt;/a&gt;, and soon the whole surveillance economy will start burning down too (&lt;a href="http://blogs.harvard.edu/doc/2018/03/23/nothing/"&gt;including publishers who depend on that economy no less than Facebook does&lt;/a&gt;).
&lt;/p&gt;

&lt;p&gt;
On the same hand, lots of Linux wizards work in that economy, which is a lot larger than Facebook alone.
&lt;/p&gt;

&lt;p&gt;
Also on the same hand, lots of wizards and muggles alike are wondering out loud how we can come up with &lt;a href="https://www.google.com/search?&amp;q=alternatives+to+facebook"&gt;alternatives to Facebook&lt;/a&gt; and other "social" platforms: ones that don't depend on surveillance-based advertising.
&lt;/p&gt;

&lt;p&gt;
On the other hand, we can move beyond platforms. Let me explain.
&lt;/p&gt;

&lt;p&gt;
See these guys?
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/core/misc/icons/e32700/error.svg" alt="Image removed." title="This image has been removed. For security reasons, only images from the local domain are allowed." class="imagecache-large-550px-centered filter-image-invalid" height="16" width="16" /&gt;&lt;p&gt;
Those are carpenters who worked for &lt;a href="https://en.wikipedia.org/wiki/D._W._Griffith"&gt;DW Griffith&lt;/a&gt;, the silent film maker, back around 1908. The head carpenter is the guy on the bottom right: &lt;a href="https://www.flickr.com/photos/docsearls/sets/72157648235867352"&gt;George W. Searls&lt;/a&gt;, my grandfather.
&lt;/p&gt;

&lt;p&gt;
In the early years of silent film, here’s what they built:
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/core/misc/icons/e32700/error.svg" alt="Image removed." title="This image has been removed. For security reasons, only images from the local domain are allowed." class="imagecache-large-550px-centered filter-image-invalid" height="16" width="16" /&gt;&lt;p&gt;
Theaters. With stage sets.
&lt;/p&gt;

&lt;p&gt;
That’s because film makers in those days thought and filmed inside the box they knew, which was theater. They'd set up a camera pointed at a stage, where actors performed just like they did in theaters.
&lt;/p&gt;

&lt;p&gt;
Griffith’s biggest pioneering move was to take the camera outside the theater, into streets and homes of Fort Lee, New Jersey, across the river from New York (that's where the shots above took place)—and then out to Hollywood and a West that was still wild. Look up &lt;a href="https://www.youtube.com/results?search_query=dw+griffith+silent+shorts"&gt;DW Griffith silent shorts&lt;/a&gt;, and somewhere among the films that come up will be the steps on which Grandpa and his carpenters sat.
&lt;/p&gt;

&lt;p&gt;
Those carpenters were the hackers that helped Griffith, and the whole film industry, think and build outside the theater.
&lt;/p&gt;

&lt;p&gt;
In a similar way, we need the Linux geeks and allied wizards to help the tech industry think and work outside the platform.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/thinking-and-working-outside-platform" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 27 Mar 2018 17:50:50 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1339757 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Learning IT Fundamentals</title>
  <link>https://www.linuxjournal.com/content/learning-it-fundamentals</link>
  <description>  &lt;div data-history-node-id="1339670" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
&lt;em&gt;Where do IT fundamentals fit in our modern, cloud- and abstraction-driven
engineering culture?&lt;/em&gt;
&lt;/p&gt;

&lt;p&gt;
I was recently discussing the Sysadmin/DevOps/IT industry with a colleague,
and we started marveling at just how few of the skills we learned when we
were starting out are actually needed today. It seems like every year a
tool, abstraction layer or service makes it so you no longer need to know
how this or that technology works. Why compile from source when all of the
software you could want is prepackaged, tested and ready to install? Why
figure out how a database works when you can just point to a pre-configured
database service? Why troubleshoot a malfunctioning Linux server when you
can nuke it from orbit and spawn a new one and hope the problem goes away?
&lt;/p&gt;

&lt;p&gt;
This is not to say that automation is bad or that abstractions are bad. When
you automate repetitive tasks and make complex tasks easier, you end up
being able to accomplish more with a smaller and more junior team. I'm
perfectly happy to take a tested and validated upstream kernel from my
distribution instead of spending hours making the same thing and hoping I
remembered to include all of the right modules. Have you ever compiled a
modern web browser? It's not fun. It's handy being able to automate myself
out of jobs using centralized configuration management tools.
&lt;/p&gt;

&lt;p&gt;
As my colleague and I were discussing the good old days, what worried us
wasn't that modern technology made things easier or that past methods
obsolete—learning new things is what drew us to this career in the first
place—but that in many ways, modern technology has obscured so much of
what's going on under the hood, we found ourselves struggling to think
of how we'd advise someone new to the industry to approach a modern
career in IT. The kind of opportunities for on-the-job training that taught
us the fundamentals of how computers, networks and Linux worked are
becoming rarer and rarer, if they exist at all.
&lt;/p&gt;

&lt;p&gt;
My story into IT mirrors many of my colleagues who started their careers
somewhere between the mid-1990s and early 2000s. I started out in a kind of
hybrid IT and sysadmin jack-of-all-trades position for a small business. I
did everything from installing and troubleshooting Windows desktops to
setting up
Linux file and web servers to running and crimping network wires. I also ran a
Linux desktop, and in those days, it hid very little of the underpinnings from
you, so you were instantly exposed to networking, software and hardware
fundamentals whether you wanted them or not.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/learning-it-fundamentals" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Sat, 17 Feb 2018 14:42:08 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1339670 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
