Skip to content

Commit 666b4fb

Browse files
eahansonsax
eahanson
and
sax
committed
rearrange site to focus on software, open source, and consulting
Co-Authored-By: Eric Saxby <77073+sax@users.noreply.github.com>
1 parent 0745ee3 commit 666b4fb

File tree

10 files changed

+1791
-1487
lines changed

10 files changed

+1791
-1487
lines changed

‎about.html‎

Lines changed: 4 additions & 153 deletions
Original file line numberDiff line numberDiff line change
@@ -1,159 +1,10 @@
11
<html>
2-
32
<head>
4-
<meta charset="utf-8" />
5-
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
6-
<link rel="stylesheet" href="assets/css/content.css" />
7-
<title>About Reflective</title>
8-
9-
<meta name="description" content="Application development and workflow automation consulting, specializing in Elixir, Phoenix, Rust, and Swift." />
10-
<meta name="og:description" property="og:description" content="Application development and workflow automation consulting, specializing in Elixir, Phoenix, Rust, and Swift." />
11-
<meta name="og:image" property="og:image" content="https://www.reflective.dev/images/logo.png" />
12-
<meta name="og:title" property="og:title" content="Reflective Software" />
13-
<meta name="og:url" property="og:url" content="https://www.reflective.dev/" />
3+
<meta http-equiv="refresh" content="0;URL='/consulting'" />
4+
<meta name="robots" content="noindex" />
5+
<title>Page Moved</title>
146
</head>
15-
167
<body>
17-
<nav>
18-
<a href="/" class="logo"><img src="images/logo.svg" width="32" height="37" /></a>
19-
<div class="links">
20-
<a href="/">home</a>
21-
about
22-
<a href="/recent-work">recent work</a>
23-
<a href="/software">software</a>
24-
</div>
25-
</nav>
26-
27-
<header id="header">
28-
<h1>About Us</h1>
29-
</header>
30-
31-
<main>
32-
<section>
33-
<h2>Elixir</h2>
34-
35-
<p>
36-
We have been building applications in Elixir since 2018, and have deployed over a dozen
37-
Elixir applications in that time. We have also published and maintain
38-
<a href="https://github.com/synchronal" target="_blank">many open source libraries</a>.
39-
</p>
40-
41-
<p>
42-
We have decades of test-driven development experience, which we have brought to Elixir
43-
in terms of building full Phoenix LiveView UI tests (that run in seconds), as well as test-related open source
44-
libraries such as
45-
<a href="https://hex.pm/packages/pages" target="_blank">Pages</a>,
46-
<a href="https://hex.pm/packages/html_query" target="_blank">HtmlQuery</a>,
47-
<a href="https://hex.pm/packages/xml_query" target="_blank">XmlQuery</a>, and
48-
<a href="https://hex.pm/packages/schema_assertions" target="_blank">Schema Assertions</a>.
49-
</p>
50-
51-
<p>
52-
We have not only built UI-heavy applications, but also built multiple data processing
53-
applications. We have experience using libraries such as Broadway, GenStage, Flow, Membrane,
54-
and Oban, as well as high-volume and high-speed data processing applications using tools
55-
provided by the Erlang and Elixir standard libraries.
56-
</p>
57-
58-
<p>
59-
In these data pipelines, we have faced problems related to strict concurrency constraints,
60-
API interoperability with little, no, or incorrect documentation, and with the need for
61-
high reliability and high speed (for instance, reducing a 12-hour long process to under 2 minutes).
62-
</p>
63-
64-
<ul>
65-
<li>CSV imports and exports</li>
66-
<li>Excel imports and exports</li>
67-
<li>XML parsing and generation</li>
68-
<li>Event sourcing of high-volume data pipelines</li>
69-
<li>Streaming data</li>
70-
</ul>
71-
</section>
72-
73-
<section>
74-
<h2>Rust</h2>
75-
76-
<p>
77-
We have built CLIs and terminal UIs in Rust, that we and teams we've worked with use every day.
78-
We have also used Rust at the core of Elixir NIFs for high speed data processing, as well as
79-
for interoperability with
80-
<a href="https://github.com/synchronal/specter" target="_blank">Rust libraries such as webrtc-rs</a>.
81-
</p>
82-
83-
<p>
84-
Our experience has focused on using Elixir as a main orchestrator for server operations, but
85-
we'd love to work more with Rust in terms of implementing core application logic shareable
86-
between multiple languages, such as Elixir and Swift.
87-
</p>
88-
89-
<ul>
90-
<li>CLIs</li>
91-
<li>TUIs</li>
92-
<li>Language interoperablity</li>
93-
</ul>
94-
</section>
95-
96-
<section>
97-
<h2>Developer workflow and tooling</h2>
98-
99-
<p>
100-
We care a lot about developer workflow, and believe that team members should be able to
101-
onboard onto new projects within minutes. New hires should be able to ship code on their
102-
first day, with a safety harness of tooling to ensure they are able to do so confidently
103-
while reducing annoyances.
104-
</p>
105-
106-
<ul>
107-
<li><a href="https://github.com/synchronal/dyd" target="_blank">Daily Diff</a></li>
108-
<li><a href="https://github.com/synchronal/medic-rs" target="_blank">Medic</a></li>
109-
<li><a href="https://github.com/synchronal/medic-ex" target="_blank">Elixir Medic</a></li>
110-
</ul>
111-
</section>
112-
113-
<section>
114-
<h2>Open source</h2>
115-
116-
<p>
117-
We care a lot about open source. We use open source as a part of every day that we spend
118-
programming, whether it's the languages and frameworks that we use, or libraries that we
119-
integrate into our applications.
120-
</p>
121-
122-
<p>
123-
As a part of developing applications for ourselves, we build and extract libraries to
124-
release code that other people might find useful. We do this under the name
125-
<a href="https://github.com/synchronal" target="_blank">Synchronal</a>, to keep them
126-
separate from any intellectual property owned by any for-profit entity. In the long term
127-
we hope to expand that organization into a larger co-operative of human-centric developers.
128-
</p>
129-
130-
<p>
131-
Code that we build for our clients may be proprietary, but if possible we would love to
132-
release and maintain open source libraries for the parts that are not.
133-
</p>
134-
135-
</section>
136-
137-
<section>
138-
<h2>Want to talk about working together?</h2>
139-
140-
<p>
141-
Email us at <a href="mailto:contact@reflective.dev">contact@reflective.dev</a>.
142-
</p>
143-
</section>
144-
</main>
145-
146-
<footer id="footer">
147-
<ul class="icons">
148-
<li><a href="https://github.com/reflective-dev" class="icon fa-github"><span class="label">GitHub</span></a></li>
149-
<li><a href="https://www.linkedin.com/company/reflective-software" class="icon fa-linkedin"><span class="label">LinkedIn</span></a></li>
150-
</ul>
151-
<ul class="copyright">
152-
<li>&copy; 2024 Reflective Software, LLC</li>
153-
</ul>
154-
</footer>
155-
156-
<script src="assets/js/main.js"></script>
8+
This page has moved. Please go to <a href="/consulting">this page</a> instead.
1579
</body>
158-
15910
</html>

0 commit comments

Comments
 (0)