|
|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
|
<html lang="en">
|
|
|
|
|
|
<head>
|
|
|
|
|
|
<meta charset="UTF-8">
|
|
|
|
|
|
<title>New Company | tait.tech</title>
|
|
|
|
|
|
<link rel="stylesheet" href="/assets/css/style.css">
|
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
|
|
|
|
<meta name="author" content="Tait Hoyem">
|
|
|
|
|
|
<meta name="keywords" content="">
|
|
|
|
|
|
<meta name="description" content="">
|
|
|
|
|
|
</head>
|
|
|
|
|
|
<body>
|
|
|
|
|
|
<div id="wrapper">
|
|
|
|
|
|
<header>
|
|
|
|
|
|
<h1>tait.tech</h1>
|
|
|
|
|
|
|
|
|
|
|
|
<nav>
|
|
|
|
|
|
|
|
|
|
|
|
<a href="/" class="nav-link" >Home</a>
|
|
|
|
|
|
|
|
|
|
|
|
<a href="/blog/" class="nav-link" >Blog</a>
|
|
|
|
|
|
|
|
|
|
|
|
<a href="/ideas/" class="nav-link" >Ideas</a>
|
|
|
|
|
|
|
|
|
|
|
|
<a href="/links/" class="nav-link" >Links</a>
|
|
|
|
|
|
|
|
|
|
|
|
<a href="https://github.com/TTWNO/" class="nav-link" target="_blank" rel="noopener noreferrer" >Github</a>
|
|
|
|
|
|
|
|
|
|
|
|
</nav>
|
|
|
|
|
|
|
|
|
|
|
|
</header>
|
|
|
|
|
|
<main>
|
|
|
|
|
|
<article>
|
|
|
|
|
|
<header>
|
|
|
|
|
|
<h1 class="post-title">New Company</h1>
|
|
|
|
|
|
<time datetime="21-11-30" class="post-date">Tuesday, November 30 2021</time>
|
|
|
|
|
|
</header>
|
|
|
|
|
|
<hr>
|
|
|
|
|
|
|
|
|
|
|
|
<p>In my accidental quest to create accessible diagrams to a computer science student I have been contracting for,
|
|
|
|
|
|
I found in the post-secondary field a massive lack of care given to the topic of accessible diagrams,
|
|
|
|
|
|
even when they are relatively easy to create.
|
|
|
|
|
|
For example, a binary tree, or any tree structure actually has <a href="https://www.w3.org/WAI/GL/wiki/Using_ARIA_trees">native <code class="language-plaintext highlighter-rouge">aria-role</code> attributes</a> to alert a screen reader to the presence of a tree object.
|
|
|
|
|
|
A tree is only a list of lists after all.</p>
|
|
|
|
|
|
|
|
|
|
|
|
<h2 id="what-im-doing-now">What I’m Doing Now</h2>
|
|
|
|
|
|
|
|
|
|
|
|
<p>Although I sort of thought my career was going in a different direction after starting a full-time job in August,
|
|
|
|
|
|
I think I’m the right guy to create a good system for this.
|
|
|
|
|
|
I will be using my existing company <a href="https://bytetools.ca/">Bytetools</a> to create and sell these tools to universities.
|
|
|
|
|
|
It will be all open-source (GPLv3), but access to a website that I maintain for an institution will cost a bunch of money that only a university can afford.</p>
|
|
|
|
|
|
|
|
|
|
|
|
<p>Side note: This is how to make money with open source:
|
|
|
|
|
|
Create the software (free and libre), then host the software for a monthly fee.
|
|
|
|
|
|
<a href="https://www.invoiceninja.com/">Invoice Ninja</a> uses this strategy, and I think it strikes the appropriate balance between the need to live off of something you care about and creating free and open-source software.
|
|
|
|
|
|
For the <em>vast</em> majority of people it makes more sense for them to purchase a subscription to your site than to find someone who can setup a website for them alone.</p>
|
|
|
|
|
|
|
|
|
|
|
|
<p>So, here goes nothing…</p>
|
|
|
|
|
|
|
|
|
|
|
|
</article>
|
|
|
|
|
|
|
|
|
|
|
|
</main>
|
|
|
|
|
|
<hr>
|
|
|
|
|
|
<footer>
|
|
|
|
|
|
This page will be mirrored on <a href="https://beta.tait.tech/2021/11/30/new-company/">beta.tait.tech</a>.
|
|
|
|
|
|
|
|
|
|
|
|
</footer>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</body>
|
|
|
|
|
|
</html>
|
