@@ -14,104 +14,115 @@ <h1>About Us</h1>
14
14
</ header >
15
15
16
16
< main >
17
- < h2 > Elixir</ h2 >
18
-
19
- < p >
20
- We have been building applications in Elixir since 2018, and have deployed over a dozen
21
- Elixir applications in that time. We have also published and maintain
22
- < a href ="https://github.com/synchronal " target ="_blank "> many open source libraries</ a > .
23
- </ p >
24
-
25
- < p >
26
- We have decades of test-driven development experience, which we have brought to Elixir
27
- in terms of building full Phoenix LiveView UI tests (that run in seconds), as well as open source
28
- libraries such as < a href ="https://hex.pm/packages/pages " target ="_blank "> Pages</ a > and
29
- < a href ="https://hex.pm/packages/html_query " target ="_blank "> HtmlQuery</ a > .
30
- </ p >
31
-
32
- < p >
33
- We have not only built UI-heavy applications, but also built multiple data processing
34
- applications. We have experience using libraries such as Broadway, GenStage, Flow, Membrane,
35
- and Oban, as well as high-volume and high-speed data processing applications using tools
36
- provided by the Erlang and Elixir standard libraries.
37
- </ p >
38
-
39
- < p >
40
- In these data pipelines, we have faced problems related to strict concurrency constraints,
41
- API interoperability with little, no, or incorrect documentation, and with the need for
42
- high reliability and high speed (for instance, reducing a 12-hour long process to under 2 minutes).
43
- </ p >
44
-
45
- < ul >
46
- < li > CSV imports and exports</ li >
47
- < li > Excel imports and exports</ li >
48
- < li > XML parsing and generation</ li >
49
- < li > Event sourcing of high-volume data pipelines</ li >
50
- < li > Streaming data</ li >
51
- </ ul >
52
-
53
- < h2 > Rust</ h2 >
54
-
55
- < p >
56
- We have built CLIs and terminal UIs in Rust, that we and teams we've work with use every day.
57
- We have also used Rust at the core of Elixir NIFs for high speed data processing, as well as
58
- for interoperability with
59
- < a href ="https://github.com/synchronal/specter " target ="_blank "> Rust libraries such as webrtc-rs</ a > .
60
- </ p >
61
-
62
- < p >
63
- Our experience has focused on using Elixir as a main orchestrator for server operations, but
64
- we'd love to work more with Rust in terms of implementing core application logic shareable
65
- between multiple languages, such as Elixir and Swift.
66
- </ p >
67
-
68
- < ul >
69
- < li > CLIs</ li >
70
- < li > TUIs</ li >
71
- < li > Language interoperablity</ li >
72
- </ ul >
73
-
74
- < h2 > Developer workflow and tooling</ h2 >
75
-
76
- < p >
77
- We care a lot about developer workflow, and believe that team members should be able to
78
- onboard onto new projects within minutes. New hires should be able to ship code on their
79
- first day, with a safety harness of tooling to ensure they are able to do so confidently
80
- while reducing annoyances.
81
- </ p >
82
-
83
- < ul >
84
- < li > < a href ="https://github.com/synchronal/dyd " target ="_blank "> Daily Diff</ a > </ li >
85
- < li > < a href ="https://github.com/synchronal/medic-rs " target ="_blank "> Medic</ a > </ li >
86
- < li > < a href ="https://github.com/synchronal/medic-ex " target ="_blank "> Elixir Medic</ a > </ li >
87
- </ ul >
88
-
89
- < h2 > Open source</ h2 >
90
-
91
- < p >
92
- We care a lot about open source. We use open source as a part of every day that we spend
93
- programming, whether it's the languages and frameworks that we use, or libraries that we
94
- integrate into our applications.
95
- </ p >
96
-
97
- < p >
98
- As a part of developing applications for ourselves, we build and extract libraries to
99
- release code that other people might find useful. We do this under the name
100
- < a href ="https://github.com/synchronal " target ="_blank "> Synchronal</ a > , to keep them
101
- separate from any intellectual property owned by any for-profit entity. In the long term
102
- we hope to expand that organization into a larger co-operative of human-centric developers.
103
- </ p >
104
-
105
- < p >
106
- Code that we build for our clients may be proprietary, but if possible we would love to
107
- release and maintain open source libraries for the parts that are not.
108
- </ p >
109
-
110
- < h2 > Want to talk about working together?</ h2 >
111
-
112
- < p >
113
- Email us at < a href ="mailto:contact@reflective.dev "> contact@reflective.dev</ a > .
114
- </ p >
17
+ < section >
18
+ < h2 > Elixir</ h2 >
19
+
20
+ < p >
21
+ We have been building applications in Elixir since 2018, and have deployed over a dozen
22
+ Elixir applications in that time. We have also published and maintain
23
+ < a href ="https://github.com/synchronal " target ="_blank "> many open source libraries</ a > .
24
+ </ p >
25
+
26
+ < p >
27
+ We have decades of test-driven development experience, which we have brought to Elixir
28
+ in terms of building full Phoenix LiveView UI tests (that run in seconds), as well as open source
29
+ libraries such as < a href ="https://hex.pm/packages/pages " target ="_blank "> Pages</ a > and
30
+ < a href ="https://hex.pm/packages/html_query " target ="_blank "> HtmlQuery</ a > .
31
+ </ p >
32
+
33
+ < p >
34
+ We have not only built UI-heavy applications, but also built multiple data processing
35
+ applications. We have experience using libraries such as Broadway, GenStage, Flow, Membrane,
36
+ and Oban, as well as high-volume and high-speed data processing applications using tools
37
+ provided by the Erlang and Elixir standard libraries.
38
+ </ p >
39
+
40
+ < p >
41
+ In these data pipelines, we have faced problems related to strict concurrency constraints,
42
+ API interoperability with little, no, or incorrect documentation, and with the need for
43
+ high reliability and high speed (for instance, reducing a 12-hour long process to under 2 minutes).
44
+ </ p >
45
+
46
+ < ul >
47
+ < li > CSV imports and exports</ li >
48
+ < li > Excel imports and exports</ li >
49
+ < li > XML parsing and generation</ li >
50
+ < li > Event sourcing of high-volume data pipelines</ li >
51
+ < li > Streaming data</ li >
52
+ </ ul >
53
+ </ section >
54
+
55
+ < section >
56
+ < h2 > Rust</ h2 >
57
+
58
+ < p >
59
+ We have built CLIs and terminal UIs in Rust, that we and teams we've work with use every day.
60
+ We have also used Rust at the core of Elixir NIFs for high speed data processing, as well as
61
+ for interoperability with
62
+ < a href ="https://github.com/synchronal/specter " target ="_blank "> Rust libraries such as webrtc-rs</ a > .
63
+ </ p >
64
+
65
+ < p >
66
+ Our experience has focused on using Elixir as a main orchestrator for server operations, but
67
+ we'd love to work more with Rust in terms of implementing core application logic shareable
68
+ between multiple languages, such as Elixir and Swift.
69
+ </ p >
70
+
71
+ < ul >
72
+ < li > CLIs</ li >
73
+ < li > TUIs</ li >
74
+ < li > Language interoperablity</ li >
75
+ </ ul >
76
+ </ section >
77
+
78
+ < section >
79
+ < h2 > Developer workflow and tooling</ h2 >
80
+
81
+ < p >
82
+ We care a lot about developer workflow, and believe that team members should be able to
83
+ onboard onto new projects within minutes. New hires should be able to ship code on their
84
+ first day, with a safety harness of tooling to ensure they are able to do so confidently
85
+ while reducing annoyances.
86
+ </ p >
87
+
88
+ < ul >
89
+ < li > < a href ="https://github.com/synchronal/dyd " target ="_blank "> Daily Diff</ a > </ li >
90
+ < li > < a href ="https://github.com/synchronal/medic-rs " target ="_blank "> Medic</ a > </ li >
91
+ < li > < a href ="https://github.com/synchronal/medic-ex " target ="_blank "> Elixir Medic</ a > </ li >
92
+ </ ul >
93
+ </ section >
94
+
95
+ < section >
96
+ < h2 > Open source</ h2 >
97
+
98
+ < p >
99
+ We care a lot about open source. We use open source as a part of every day that we spend
100
+ programming, whether it's the languages and frameworks that we use, or libraries that we
101
+ integrate into our applications.
102
+ </ p >
103
+
104
+ < p >
105
+ As a part of developing applications for ourselves, we build and extract libraries to
106
+ release code that other people might find useful. We do this under the name
107
+ < a href ="https://github.com/synchronal " target ="_blank "> Synchronal</ a > , to keep them
108
+ separate from any intellectual property owned by any for-profit entity. In the long term
109
+ we hope to expand that organization into a larger co-operative of human-centric developers.
110
+ </ p >
111
+
112
+ < p >
113
+ Code that we build for our clients may be proprietary, but if possible we would love to
114
+ release and maintain open source libraries for the parts that are not.
115
+ </ p >
116
+
117
+ </ section >
118
+
119
+ < section >
120
+ < h2 > Want to talk about working together?</ h2 >
121
+
122
+ < p >
123
+ Email us at < a href ="mailto:contact@reflective.dev "> contact@reflective.dev</ a > .
124
+ </ p >
125
+ </ section >
115
126
</ main >
116
127
117
128
< footer id ="footer ">
@@ -126,5 +137,5 @@ <h2>Want to talk about working together?</h2>
126
137
127
138
< script src ="assets/js/main.js "> </ script >
128
139
</ body >
129
- </ html >
130
140
141
+ </ html >
0 commit comments