<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Entrepreneurship on Adam Koszek - Personal Website</title>
    <link>https://www.koszek.com/tags/entrepreneurship/</link>
    <description>Recent content in Entrepreneurship on Adam Koszek - Personal Website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>adam@koszek.com (Adam Koszek)</managingEditor>
    <webMaster>adam@koszek.com (Adam Koszek)</webMaster>
    <lastBuildDate>Mon, 16 Nov 2015 00:00:00 +0000</lastBuildDate><atom:link href="https://www.koszek.com/tags/entrepreneurship/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Computer History from Giants Themselves</title>
      <link>https://www.koszek.com/blog/2015/11/16/computer-history-from-giants-themselves/</link>
      <pubDate>Mon, 16 Nov 2015 00:00:00 +0000</pubDate>
      <author>adam@koszek.com (Adam Koszek)</author>
      <guid>https://www.koszek.com/blog/2015/11/16/computer-history-from-giants-themselves/</guid>
      <description>&lt;p&gt;I was an idol driven kid and I’ve always had somebody I admired when
growing up. From the earliest recollections I could trace back in my
memory the very first person was probably my grandfather, the master
tailor. And through him I got to know
&lt;a href=&#34;https://en.wikipedia.org/wiki/MacGyver&#34;&gt;MacGyver&lt;/a&gt;. I was allowed to
watch MacGyver, since my grandfather believed it would teach me
creativity and also because I loved pocket knifes. Till this day each
time you say something bad about MacGyver, you’ll have an enemy in me,
since it was such an integral part of my growing up and becoming
creative. Same applies to &lt;a href=&#34;https://en.wikipedia.org/wiki/John_%22Hannibal%22_Smith&#34;&gt;John Hannibal
Smith&lt;/a&gt; and
probably &lt;a href=&#34;https://en.wikipedia.org/wiki/Emmett_Brown&#34;&gt;Dr Emmet Brown&lt;/a&gt;.
The older I got, the more my idols shifted from the fictional characters
to real-world people, and this stayed with me till my adult life.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Why it&#39;s not about self-driving</title>
      <link>https://www.koszek.com/blog/2015/09/23/why-its-not-about-self-driving/</link>
      <pubDate>Wed, 23 Sep 2015 00:00:00 +0000</pubDate>
      <author>adam@koszek.com (Adam Koszek)</author>
      <guid>https://www.koszek.com/blog/2015/09/23/why-its-not-about-self-driving/</guid>
      <description>&lt;p&gt;In “How to be Rich” Jean Paul Getty expressed his excitement about
enormous advances in science and technology at the beginning of the
20th century. The 21st century seemed to start in an equally exciting
way, for example the self-driving car is attracting a great deal of
attention lately. When I was about 14 years old a friend of mine told me
that if &lt;a href=&#34;https://en.wikipedia.org/wiki/KITT&#34;&gt;KITT&lt;/a&gt; had existed, she’d
have bought one. I wasn’t surprised - every kid in my neighborhood
wanted KITT and everybody wanted to be
&lt;a href=&#34;https://en.wikipedia.org/wiki/David_Hasselhoff&#34;&gt;Hasselhoff&lt;/a&gt;. Moving
to the US meant dealing with everything supersized; the smallest car at
the airport car rental was bigger than anything I’d ever driven. I
really wanted a CarOS: a software featuring a button which would get me
from A to B with no hassle. I promised myself that when a self-driving
vehicle like this becomes available, I would become an early adopter as
soon as my wallet would let me.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>How do you evaluate new technologies?</title>
      <link>https://www.koszek.com/blog/2015/08/26/how-do-you-evaluate-new-technologies/</link>
      <pubDate>Wed, 26 Aug 2015 00:00:00 +0000</pubDate>
      <author>adam@koszek.com (Adam Koszek)</author>
      <guid>https://www.koszek.com/blog/2015/08/26/how-do-you-evaluate-new-technologies/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.google.com/search?num=100&amp;amp;espv=2&amp;amp;q=how&amp;#43;do&amp;#43;i&amp;#43;get&amp;#43;started&amp;#43;with&amp;amp;oq=how&amp;#43;do&amp;#43;i&amp;#43;get&amp;#43;started&amp;#43;with&amp;amp;gs_l=serp.3..0l10.2369.4525.0.4799.11.6.3.2.2.0.120.574.3j3.6.0....0...1c.1.64.serp..3.8.404.yCvToyxF6AE&#34;&gt;“How do I get started with X”&lt;/a&gt;
is probably one of the most frequently asked questions on technical
forums. With 2.8 billion results from Google, somehow technical “AWS”
manages to top the search results page:&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;2015-08-26-how-do-you-evaluate-new-technologies/image05.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;As a software crowd, we all start to use new technologies at some point.
While many technologies are fairly self-explanatory (having no
“democratize” or “disruptive” in their name), many of them aren’t, or
simply have no feature that distinguishes them from other available
options. How do &lt;strong&gt;you&lt;/strong&gt; select new components for your newest product?&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Non-continuous innovation = dangerous or “Amazon Ad Platform Cleanups”</title>
      <link>https://www.koszek.com/blog/2015/08/10/non-continuous-innovation-is-dangerous/</link>
      <pubDate>Mon, 10 Aug 2015 00:00:00 +0000</pubDate>
      <author>adam@koszek.com (Adam Koszek)</author>
      <guid>https://www.koszek.com/blog/2015/08/10/non-continuous-innovation-is-dangerous/</guid>
      <description>&lt;p&gt;I received an email from Amazon two months ago, but I didn’t really pay
attention to it,letting it stew in my mailbox for a while, until I
visited the &lt;a href=&#34;https://www.koszek.com/reading/&#34;&gt;&lt;em&gt;reading section of my
website&lt;/em&gt;&lt;/a&gt; in the hope of referring to
&lt;a href=&#34;https://www.koszek.com/books/2012/12/07/book-the-old-new-thing/&#34;&gt;&lt;em&gt;the book I read a while
ago&lt;/em&gt;&lt;/a&gt;,
and all I saw instead of a nice picture was this:&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;2015-08-10-non-continuous-innovation-is-dangerous/image02.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;The cause is good, but the place is bad. So I went back and I dug up the
email:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Optimize for the Developer’s Time, Not the Machine’s</title>
      <link>https://www.koszek.com/blog/2015/07/28/optimize-for-developers-time/</link>
      <pubDate>Tue, 28 Jul 2015 00:00:00 +0000</pubDate>
      <author>adam@koszek.com (Adam Koszek)</author>
      <guid>https://www.koszek.com/blog/2015/07/28/optimize-for-developers-time/</guid>
      <description>&lt;p&gt;It is sometimes easy to forget how computer engineers in the early days
struggled just to make things work. In ’70s and ’80s, computing
resources like memory were scarce; CPUs were slow, and disk space was
limited. There was little or no networking, and communication with the
computer was primitive. Heck, even Norton Commander on a 12” was
suboptimal. Right now, I could probably achieve this:&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;2015-07-19-optimize-for-developers-time/image02.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;And do it in a single Terminal window, which would make ’70s engineers’
eyeballs go red with jealousy. Have you ever wondered what the world was
like without Vim or Emacs? Yet these are fairly recent accomplishments.
To summarize: It’s easy to forget all these things and keep asking
questions such as &lt;a href=&#34;https://www.joelonsoftware.com/items/2008/02/19.html&#34;&gt;&lt;em&gt;why are Microsoft Office file formats so
complicated&lt;/em&gt;&lt;/a&gt;,
unless you understand the heritage of certain decisions and computers in
general.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
