aboutsummaryrefslogtreecommitdiff
path: root/build/being-efficient/index.html
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-06-08 13:43:37 -0400
committerBradley Taunt <bt@btxx.org>2024-06-08 13:43:37 -0400
commit16d28628aca9b2d356de31c319f5e7bc0f5b2b02 (patch)
tree11947abb71e38cbe75116871694a44c33d257763 /build/being-efficient/index.html
parentdcfb172704f3afb68a30425029ec834be2883274 (diff)
Remove incorrectly generated files, fix up markdown articles
Diffstat (limited to 'build/being-efficient/index.html')
-rw-r--r--build/being-efficient/index.html35
1 files changed, 5 insertions, 30 deletions
diff --git a/build/being-efficient/index.html b/build/being-efficient/index.html
index fb8f591..2ce66ec 100644
--- a/build/being-efficient/index.html
+++ b/build/being-efficient/index.html
@@ -3,11 +3,12 @@
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
+ <meta name="color-scheme" content="dark light">
<link rel="icon" href="data:,">
<title>Being More Efficient as a Designer and Developer</title>
<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
-<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
</head>
<nav>
@@ -16,31 +17,18 @@
<main>
<h1 id="being-more-efficient-as-a-designer-and-developer">Being More Efficient as a Designer and Developer</h1>
-
<p>2019-09-28</p>
-
<p><em>I recently began working on a small side project</em> (a marketing site &#47; blog for an upcoming UX book I&#8217;m writing, but I have nothing to promote yet - sorry) and found myself circling around different static site generators (SSG) in the initial design concepts. The thought of learning an entirely new blogging platform was inspiring and seemed like a good excuse to expand my skillset.</p>
-
<p>Although I&#8217;ve used 11ty and Hugo in the past for client work, this personal website runs on Jekyll. I&#8217;m very familiar with Jekyll and can push out a point-of-concept site in a flash with little-to-no effort. So, why was I looking to jump into a SSG I hadn&#8217;t used before? </p>
-
<p>And that got me thinking&#8230; <strong>Why am I moving away from being efficient?</strong></p>
-
<h2 id="before-we-begin">Before we begin&#8230;</h2>
-
<p>I should preface everything else I&#8217;m going to mention in this post with this: <em>learning new stuff is awesome</em>. You should expand your knowledge as much as you can, no matter what industry you find yourself in. I&#8217;ve found it to be a great catalyst for boosting my passion in design and development.</p>
-
<p>Okay, I&#8217;ve made it clear that learning is important to the growth of your career - so please keep that in mind before you read my next statement:</p>
-
<p><strong>Just use what you already know.</strong></p>
-
<p>By using your current experience (maybe even expertise) with a design system, CSS framework, blogging platform, programming language, etc. you can get something <em>built</em>. Not to mention you can get that thing built in a <em>fraction of the time</em>. After all, building things is kind of the point of being a designer (or developer), right?</p>
-
<p>My current side project may be a slight edge case in this regard. Since it&#8217;s a personal &#8220;dev&#8221; website, most of the tech stack choices comes down to personal preference - not client requirements. But I believe my point still remains: you shouldn&#8217;t reach for something new and shiny <em>just because</em> it&#8217;s new and shiny.</p>
-
<h2 id="some-vague-examples">Some vague examples</h2>
-
<p>It might be easier to understand what I mean by using some possible real-world examples:</p>
-
<table>
<thead>
<tr>
@@ -49,7 +37,6 @@
<th>Efficient Way</th>
</tr>
</thead>
-
<tbody>
<tr>
<td>A local bakery needs product and e-cart functionality</td>
@@ -68,40 +55,28 @@
</tr>
</tbody>
</table>
-
<p>I know all of this is very much &#8220;common sense&#8221;, but you would be surprised how often we reach out for the latest and greatest tools (we are creative problem-solvers, after-all). If a current project allots you the time to learn a new skillset alongside outputting a quality product - then more power to you. In my experience that&#8217;s a rare luxury, so my advice is to focus on shipping quality work (whether that&#8217;s code, design, analytics, content, etc) instead of getting caught up in the &#8220;new and shiny&#8221;.</p>
-
<h2 id="but-wait-how-when-do-i-learn-new-things">But wait, how &#47; when do I learn new things?</h2>
-
<p>It isn&#8217;t exactly ground breaking to state that you should keep things simple as a developer. There are probably hundreds of posts on the web advocating for the exact same thing - which is good. At the same time, we as designers and developers need to avoid stagnation - something that can happen all too easily.</p>
-
<p>So how do we learn new things? This is a hard thing to answer. Really, the best response would be: <strong>it depends on the designer &#47; developer</strong>. I know, <em>what a cop-out</em>. Unfortunately, it&#8217;s true. There is no one solution to learning anything new.</p>
-
<p>The best I can do is offer up some possible options:</p>
-
<ul>
-<li><p>Learn outside of work</p>
-
+<li>Learn outside of work
<ul>
<li>Reading &#47; listening to a technical book on your commute or before bed</li>
<li>Take an online course you can work on after hours</li>
</ul></li>
-<li><p>Contribute to an open source project that you aren&#8217;t familiar with but are interested in</p>
-
+<li>Contribute to an open source project that you aren&#8217;t familiar with but are interested in
<ul>
<li>Even tiny contributions go a long way, don&#8217;t doubt yourself so much</li>
</ul></li>
-<li><p>Ask your current company (if not a freelancer that is) to learn on their time</p>
-
+<li>Ask your current company (if not a freelancer that is) to learn on their time
<ul>
<li>It&#8217;s a valid argument that your company should have vested interest in you becoming a better developer &#47; designer</li>
</ul></li>
</ul>
-
<h2 id="easier-said-than-done">Easier said than done</h2>
-
<p>Sometimes, even the suggestions above don&#8217;t work for certain individuals. Life is hectic and other important things can pop-up taking precedence. Don&#8217;t let it get you down - there are more important things in life than mastering the newest framework that released 25 minutes ago.</p>
-
<p>My motto is to keep shipping quality products that you actually give a shit about. Otherwise it doesn&#8217;t matter how &#8220;new&#8221; it is.</p>
<footer role="contentinfo">
<h2>Menu Navigation</h2>