Compare commits
2 Commits
main
...
neil-patch
| Author | SHA1 | Date | |
|---|---|---|---|
| 74fd433dde | |||
| 4287c88bf2 |
1
.gitignore
vendored
1
.gitignore
vendored
@ -1,4 +1,3 @@
|
||||
public/
|
||||
resources/
|
||||
pages.git/
|
||||
.hugo_build.lock
|
||||
|
||||
2
.gitmodules
vendored
2
.gitmodules
vendored
@ -1,3 +1,3 @@
|
||||
[submodule "themes/hugo-sustain"]
|
||||
path = themes/hugo-sustain
|
||||
url = https://git.shrug.pw/neil/hugo-sustain.git
|
||||
url = https://git.shrug.pw/neil/hugo-sustain
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
//$primary-color: #ABC9E3;
|
||||
$primary-color: #115c9e;
|
||||
$primary-color: #ABC9E3;
|
||||
$hover-color: #5E7191;
|
||||
|
||||
|
||||
html, body {
|
||||
border-top-color: $primary-color;
|
||||
}
|
||||
@ -58,14 +56,6 @@ figure > img {
|
||||
width: 90%;
|
||||
}
|
||||
|
||||
h2, h3 {
|
||||
clear: both;
|
||||
}
|
||||
|
||||
h5 {
|
||||
font-weight: bold
|
||||
}
|
||||
|
||||
.clearfix {
|
||||
overflow: auto;
|
||||
}
|
||||
@ -74,58 +64,3 @@ h5 {
|
||||
clear: both;
|
||||
display: table;
|
||||
}
|
||||
|
||||
/* Projects page styling */
|
||||
.project-card {
|
||||
background: #fff;
|
||||
border: 1px solid #e8e8e8;
|
||||
border-radius: 8px;
|
||||
padding: 1.5rem;
|
||||
height: 100%;
|
||||
transition: box-shadow 0.3s ease, transform 0.2s ease;
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
}
|
||||
|
||||
.project-card:hover {
|
||||
box-shadow: 0 4px 12px rgba(0,0,0,0.1);
|
||||
transform: translateY(-2px);
|
||||
}
|
||||
|
||||
.project-header {
|
||||
display: flex;
|
||||
align-items: center;
|
||||
margin-bottom: 1rem;
|
||||
}
|
||||
|
||||
.project-icon {
|
||||
font-size: 1.8rem;
|
||||
color: $primary-color;
|
||||
margin-right: 1rem;
|
||||
min-width: 2rem;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.project-title {
|
||||
margin: 0;
|
||||
flex: 1;
|
||||
}
|
||||
|
||||
.project-title a {
|
||||
color: $primary-color;
|
||||
text-decoration: none;
|
||||
font-weight: 600;
|
||||
}
|
||||
|
||||
.project-title a:hover {
|
||||
color: $hover-color;
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
.project-description {
|
||||
color: #666;
|
||||
line-height: 1.6;
|
||||
margin: 0;
|
||||
flex: 1;
|
||||
text-align: left;
|
||||
}
|
||||
|
||||
@ -5,7 +5,7 @@ title = "Neil Hanlon"
|
||||
# Enable comments by entering your Disqus shortname
|
||||
disqusShortname = ""
|
||||
# Enable Google Analytics by entering your tracking code
|
||||
# googleAnalytics = ""
|
||||
googleAnalytics = ""
|
||||
theme = "hugo-sustain"
|
||||
|
||||
[permalinks]
|
||||
@ -23,11 +23,9 @@ theme = "hugo-sustain"
|
||||
|
||||
[params.social]
|
||||
Github = "NeilHanlon"
|
||||
Email = "neil@shrug.pw"
|
||||
Bluesky = "@shrug.pw"
|
||||
Email = "neil@shrug.pw.com"
|
||||
Twitter = "NeilHanlon"
|
||||
LinkedIn = "hanlonneil"
|
||||
Signal = "hScowCEn-H1GKkCrare0m_xOEPqTWxt51pW9SI2bU5TlXrMW9QFD6qHBLqG1jDq9"
|
||||
Keybase = "nhanlon"
|
||||
#Stackoverflow = "username"
|
||||
#Medium = "hanlon.neil"
|
||||
Instagram = "noellathekitty"
|
||||
@ -1,57 +0,0 @@
|
||||
---
|
||||
title: 'Joining ResolveX as a Technical Advisor: Infrastructure and Crisis Response'
|
||||
description: "I've joined ResolveX as a technical advisor to help scale their crisis response software. Working on infrastructure, security, and scaling decisions for 988 suicide prevention lines and mental health crisis centers."
|
||||
date: 2025-08-08T10:17:20-04:00
|
||||
draft: false
|
||||
categories: ['consulting', 'social-impact']
|
||||
tags: ['crisis-response', 'mental-health', 'infrastructure', 'advisory', 'resolvex', '988']
|
||||
---
|
||||
|
||||
I'm excited to share that I've joined [ResolveX](https://resolvex.com) as a technical advisor. ResolveX
|
||||
builds software and data solutions for crisis call centers—988 suicide
|
||||
prevention lines, domestic violence hotlines, and other critical mental health
|
||||
resources.
|
||||
|
||||
## Why This Matters
|
||||
|
||||
Mental health crisis response has significant gaps that technology can help address. ResolveX builds tools to make crisis counselors more effective and help researchers understand patterns that could prevent crises.
|
||||
|
||||
They serve 988 operators—resource-constrained nonprofits handling life-or-death situations. The technical requirements are unique: rock-solid reliability, security for sensitive mental health data, and cost-effectiveness for organizations that measure impact in lives saved.
|
||||
|
||||
## The Technical Challenge
|
||||
|
||||
ResolveX is hitting the classic startup infrastructure inflection point—scaling from scrappy solutions to supporting a primary mental health data warehouse without over-engineering.
|
||||
|
||||
My role: provide neutral perspective on infrastructure, security, and scaling decisions. Lightweight advisory rather than hands-on implementation, helping spot issues early and suggest practical solutions within their budget and mission.
|
||||
|
||||
## What I'm Doing
|
||||
|
||||
The immediate priorities are pretty straightforward:
|
||||
|
||||
- **Infrastructure & Security Audit**: Review current hosting, architecture, and configurations. Light security testing and access review.
|
||||
|
||||
- **Ongoing Advisory**: Lightweight consultation (~5 hours/week) for feedback and neutral oversight on scaling decisions.
|
||||
|
||||
- **Content Collaboration**: Educational content that benefits both crisis response and broader tech communities.
|
||||
|
||||
## The Bigger Picture
|
||||
|
||||
This isn't just consulting work—I've been getting into emergency response volunteering (CERT, amateur radio) and care deeply about how we handle mental health crises. ResolveX has potential to become an open-source-friendly, public-impact organization changing mental health data collection and analysis.
|
||||
|
||||
## Technical Philosophy
|
||||
|
||||
The constraints make this engaging: high reliability and security requirements, minimal budget, maximum impact. Every architectural decision must justify real value to crisis counselors and those they help.
|
||||
|
||||
This requires "appropriate technology"—sophisticated enough for requirements but simple enough to maintain and afford. Systems engineering with purpose, not hope-based engineering.
|
||||
|
||||
## Looking Forward
|
||||
|
||||
I'll write follow-ups about specific technical challenges as this develops. Infrastructure engineering for social impact deserves more attention.
|
||||
|
||||
If you're working on mission-driven technology or considering how your skills could have broader social impact, reach out. **There's more of this work that needs doing.**
|
||||
|
||||
---
|
||||
|
||||
If you're interested in similar advisory or consulting work, you can reach me
|
||||
through [my consulting practice](https://shrugpw.com) or find me on the usual places around the
|
||||
internet.
|
||||
@ -32,16 +32,6 @@ using an [ESP32](https://www.espressif.com/en/products/socs/esp32) and
|
||||
visualize your soldering statistics, to automatically turn on an exhaust fan
|
||||
when you start working.
|
||||
|
||||
### Acknowledgements
|
||||
|
||||
- [Ben Brown (Ralim)](https://github.com/ralim) - Maintainer and developer of IronOS for Pinecil and Miniware Irons
|
||||
- Support them on [Ko-fi](https://ko-fi.com/ralim)
|
||||
- [Gamiee (Gamelaster)](https://github.com/gamelaster) - Developer and maintainer of pine64_updater, IronOS
|
||||
- [River-Mochi](https://github.com/river-mochi) for reviewing this article and their excellent organization and documentation work for Pine64 and the Pinecil.
|
||||
- [TomW1605](https://github.com/TomW1605) & [ithinkido](https://github.com/ithinkido) for their work on the implementation of the Pinecil ESP32 integration
|
||||
- [Builder555](https://github.com/builder555) - PineSAM maintainer and developer
|
||||
- [Joric](https://github.com/joric) - Developer of original BLE GATT application for Pinecil
|
||||
|
||||
## The Pinecil
|
||||
|
||||
The [Pinecil](https://www.pine64.org/pinecil/) is an open-source soldering iron
|
||||
@ -67,8 +57,6 @@ a genuine Pinecil, and how to avoid fakes.
|
||||
tricks, as well as up to date purchasing and troubleshooting information.
|
||||
- Shout out to River-Mochi for their _awesome_ work on keeping this up to date
|
||||
and useful
|
||||
- [Pine64 Updater](https://github.com/pine64/pine64_updater) - v1 Pinecil updater tool
|
||||
- [Pinecil Development Projects](https://wiki.pine64.org/wiki/Pinecil#Development_Projects) - Updated links to all community projects
|
||||
|
||||
## Blisp
|
||||
|
||||
@ -104,40 +92,25 @@ instructions in the repository.
|
||||
|
||||
1. Find the latest sucessful actions run on the ironos repo
|
||||
[here](https://github.com/Ralim/IronOS/actions/workflows/push.yml?query=branch%3Adev+event%3Apush).
|
||||
2. Download the `Pinecilv2` zip file for that run, and unzip it
|
||||
2. Download the `Pinecilv2_multi-lang` binary for that run, and unzip it
|
||||
3. Plug your Pinecil into your computer while holding down the 'Minus' (-)
|
||||
button. The screen should **not** turn on. If on Linux, `dmesg` should report
|
||||
seeing the BL706 as a serial device.
|
||||
4. Run the following command to flash the firmware to your Pinecil:
|
||||
```
|
||||
blisp write -c bl70x --reset /path/to/Pinecilv2_extracted/Pinecilv2_EN.bin
|
||||
blisp write -c bl70x --reset /path/to/Pinecilv2_multi-lang/Pinecilv2_EN.bin
|
||||
```
|
||||
5. Un-plug and plug the Pinecil back in to boot the new firmware
|
||||
|
||||
NOTE: You may ignore the .dfu and .hex files provided in the .zip file.
|
||||
### Pineflash
|
||||
|
||||
##### Pinecilv2 vs Pinecilv2_multi-lang
|
||||
|
||||
Two variants of firmwares for Pinecil are provided: combined mutli-language binaries, and individual per-language binaries. The per-language binaries are much smaller, and while the Pinecilv2 has more flash available to store the mutli-language images, for general usage, you will have an easier time with the language-specific binary rather than the multi-lang binaries.
|
||||
|
||||
Multi-lang provides three bundles of languages:
|
||||
|
||||
1. Chinese and Japanese
|
||||
2. Russian, Ukranian, Serbian, and Bulgarian
|
||||
3. European (All not mentioned above)
|
||||
|
||||
Ultimately, it is up to you which you decide to use
|
||||
|
||||
#### Pineflash
|
||||
|
||||
[Spagett1](https://github.com/Spagett1) updated their Pineflash tool which allows
|
||||
for a non-command-line experience for flashing new versions of IronOS on the Pinecil V1 and V2, similar to the Pine64 updater (add link) utility for the v1 Pinecil. You can find
|
||||
[Spagett1](https://github.com/Spagett1) is working on a new tool which allows
|
||||
for a non-command-line experience for flashing new versions of IronOS on the
|
||||
Pinecil, similar to the Pine64 updater utility for the v1 Pinecil. You can find
|
||||
more information on the PineFlash
|
||||
[GitHub repo](https://github.com/Spagett1/PineFlash). Feel free to check it out
|
||||
and give them feedback!
|
||||
|
||||
Pineflash supports Linux and MacOS at this time (2023-04-03), and support for Windows is a work in progress. If you would like to help test, please join the chat and make yourself known.
|
||||
|
||||
## Bluetooth Low Energy
|
||||
|
||||
Bluetooth Low Energy (BLE) is a wireless communication protocol that is designed
|
||||
@ -145,9 +118,7 @@ to consume less energy than classic Bluetooth. There is upcoming support in
|
||||
browser APIs to allow access to BLE devices, and so there are a handful of
|
||||
options for how to get your Pinecil talking to your computer.
|
||||
|
||||
## Interacting with your Pinecil over Bluetooth
|
||||
|
||||
### PineSAM by [Builder555](https://github.com/builder555)
|
||||
## PineSAM and Joric's UI
|
||||
|
||||
PineSAM (Pinecil Settings and Menus) started out as an in-browser way to see and
|
||||
change settings. It's served a multitude of uses from helping people with
|
||||
@ -155,33 +126,10 @@ cracked or non-functional screens, all the way to adding really helpful
|
||||
accessibility features to those who struggle to read the small screen on the
|
||||
Pinecil. It's is a Python and Vue-based application that has to have a server
|
||||
component running locally--along with a machine that has bluetooth. You can find
|
||||
the source code for PineSAM on [GitHub](https://github.com/builder555/PineSAM/), but read on below for how to grab precompiled versions of the application.
|
||||
the source code for PineSAM on [GitHub](https://github.com/builder555/PineSAM/).
|
||||
|
||||
{{< figure src="pinesam.png" alt="PineSAM UI" class="inline" >}}
|
||||
|
||||
PineSAM allows the user to not only see the live temperature, wattage, and
|
||||
voltage of their device but change the settings and temperatures at a click.
|
||||
Uniquely, it allows users to set temperature presets for one-click changes
|
||||
between temperatures--for example to switch between leaded and unleaded solder.
|
||||
|
||||
You can access PineSAM from your mobile device once it's running on your computer to have a touch-capable way of controlling your settings. On your phone, flip the screen to portait mode in order to see the graph as on desktop.
|
||||
|
||||
{{< figure src="pinesam-mobile.png" alt="Screenshot of PineSAM UI on Mobile device" class="inline-40 left" >}}
|
||||
|
||||
The PineSAM project is working to integrate a "Work" screen which takes
|
||||
inspiration from Joric's UI. Due to this, it's likely these two projects will
|
||||
end up combining into one, in my opinion, despite their distinct mechanisms for
|
||||
retrieving BLE data from the Pinecil.
|
||||
|
||||
#### Setting up PineSAM
|
||||
|
||||
See the
|
||||
[project readme](https://github.com/builder555/PineSAM#i-using-pre-made-binaries)
|
||||
for the most up-to-date instructions. If you run into any trouble, come find us
|
||||
in the #pinecil channel on Pine64's Discord or Telegram chat.
|
||||
|
||||
### [Joric](https://github.com/joric/)'s BLE API
|
||||
|
||||
Another project is a more simple web UI that uses in-browser Bluetooth support
|
||||
(currently only really well supported in Chromium/Firefox, and even then it's
|
||||
not universal or without bugs. This UI shows a nice graph of your Pinecil's
|
||||
@ -192,7 +140,26 @@ device. You can also find the source code for Joric UI on
|
||||
|
||||
{{< figure src="joric-ui.png" alt="Joric's UI" class="inline-60 right" >}}
|
||||
|
||||
#### Setting up Joric's UI
|
||||
PineSAM allows the user to not only see the live temperature, wattage, and
|
||||
voltage of their device but change the settings and temperatures at a click.
|
||||
Uniquely, it allows users to set temperature presets for one-click changes
|
||||
between temperatures--for example to switch between leaded and unleaded solder.
|
||||
|
||||
{{< figure src="pinesam-mobile.png" alt="Screenshot of PineSAM UI on Mobile device" class="inline-40 left" >}}
|
||||
|
||||
The PineSAM project is working to integrate a "Work" screen which takes
|
||||
inspiration from Joric's UI. Due to this, it's likely these two projects will
|
||||
end up combining into one, in my opinion, despite their distinct mechanisms for
|
||||
retrieving BLE data from the Pinecil.
|
||||
|
||||
### Setting up PineSAM
|
||||
|
||||
See the
|
||||
[project readme](https://github.com/builder555/PineSAM#i-using-pre-made-binaries)
|
||||
for the most up-to-date instructions. If you run into any trouble, come find us
|
||||
in the #pinecil channel on Pine64's Discord or Telegram chat.
|
||||
|
||||
### Setting up Joric's UI
|
||||
|
||||
No setup needed! Just browse to
|
||||
[https://joric.github.io/pinecil/](https://joric.github.io/pinecil/) in a
|
||||
@ -218,7 +185,7 @@ soldering iron using Pinecil with Home Assistant and ESPHome.
|
||||
{{< figure src="hass-soldering.png" alt="Home Assistant Soldering UI" class="inline" >}}
|
||||
|
||||
To make this work, we'll use an
|
||||
[ESPHome configuration file](https://github.com/TomW1605/esphome_pinecilv2_ble/blob/main/esphome_pinecilv2_ble.yaml)
|
||||
[ESPHome configuration file]((https://github.com/TomW1605/esphome_pinecilv2_ble/blob/main/esphome_pinecilv2_ble.yaml))
|
||||
put together by Pine64 community member TomW1605. Thank you again, Tom!
|
||||
|
||||
## Requirements
|
||||
|
||||
@ -3,5 +3,4 @@ categories: ["projects"]
|
||||
date: "2016-10-02T22:55:05-04:00"
|
||||
tags: ["projects"]
|
||||
title: "Projects"
|
||||
layout: "projects"
|
||||
---
|
||||
|
||||
@ -1,30 +1,6 @@
|
||||
name: Projects
|
||||
source:
|
||||
- icon: fa-solid fa-building
|
||||
name: Rocky Enterprise Software Foundation
|
||||
description: Board member for the non-profit foundation behind Rocky Linux. Focus on strategic governance, financial oversight, and advancing the mission of community-driven enterprise Linux distribution development.
|
||||
url: https://rockylinux.org/about
|
||||
- icon: fa-brands fa-github
|
||||
- icon: fa fa-github
|
||||
name: Rocky Linux
|
||||
description: Infrastructure architect and core team member for Rocky Linux. Built and maintain all infrastructure from bare metal to cloud services, including CI/CD pipelines, build systems, and supply chain security. Work closely with Release Engineering on next-generation build automation and ensuring security throughout the software supply chain.
|
||||
description: All the infrastructure for Rocky Linux, from soup to nuts. Work with a team of professionals to architect, design, and implement secure systems and proceudres to write Infrastructure as Code to provide systems for the various teams within the Rocky Enterprise Software Foundation, especially Rocky Linux as it gets off the ground. Also work closely with Release Engineering on building next generation Build Automation pipeline tools and ensuring reliability and security in the supply chain.
|
||||
url: https://github.com/rocky-linux/
|
||||
- icon: fa-solid fa-code-branch
|
||||
name: OpenELA
|
||||
description: Technical Steering Committee member for OpenELA, the Open Enterprise Linux Association. Help guide technical strategy and governance for collaborative development of enterprise Linux distributions, focusing on open source supply chain transparency and community collaboration.
|
||||
url: https://openela.org/
|
||||
- icon: fa-solid fa-heart
|
||||
name: ResolveX
|
||||
description: Board member and technical advisor for ResolveX, building software and data solutions for crisis call centers including 988 suicide prevention lines and mental health resources. Provide strategic guidance on scaling infrastructure and technology decisions for mission-critical systems.
|
||||
url: https://resolvex.com/
|
||||
- icon: fa-solid fa-handshake
|
||||
name: Shrug PW Consulting
|
||||
description: Founder and Principal Consultant providing infrastructure architecture, DevOps automation, and technical advisory services. Specialize in scaling systems for mission-driven organizations, supply chain security, and building reliable infrastructure on constrained budgets.
|
||||
url: https://shrugpw.com/
|
||||
- icon: fa-brands fa-fedora
|
||||
name: Fedora Project
|
||||
description: Active contributor to Fedora RISC-V SIG and Community Operations (CommOps). Work on infrastructure, packaging ecosystem, build systems, and community tooling. Focus on RISC-V architecture support and community infrastructure reliability.
|
||||
url: https://fedoraproject.org/
|
||||
- icon: fa-solid fa-cloud
|
||||
name: OpenStack
|
||||
description: Core reviewer for OpenStack-Ansible and contributor to OpenStack-Kolla projects. Support OpenStack integration with Rocky Linux and work in CentOS NFV and Cloud SIGs. Focus on deployment automation, bare metal provisioning, and enterprise Linux integration.
|
||||
url: https://openstack.org/
|
||||
|
||||
@ -19,8 +19,6 @@ hanlon.ninja
|
||||
thepotato.tech
|
||||
EOF
|
||||
|
||||
cp .woodpecker.yml pages.git/
|
||||
|
||||
cd pages.git
|
||||
|
||||
set -x
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
{{ define "main" }}
|
||||
<!-- Header -->
|
||||
{{ partial "header" . }}
|
||||
|
||||
<div class="container">
|
||||
<section id="projects">
|
||||
<h4 class="my-5">{{ .Site.Data.projects.name }}</h4>
|
||||
<div class="row">
|
||||
{{ range $el := .Site.Data.projects.source }}
|
||||
<div class="col-md-6 mb-4">
|
||||
<div class="project-card">
|
||||
<div class="project-header">
|
||||
<i class="{{ .icon }} project-icon"></i>
|
||||
<h5 class="project-title">
|
||||
<a href="{{ .url }}" target="_blank">{{ $el.name }}</a>
|
||||
</h5>
|
||||
</div>
|
||||
<p class="project-description">{{ $el.description }}</p>
|
||||
</div>
|
||||
</div>
|
||||
{{ end }}
|
||||
</div>
|
||||
</section>
|
||||
</div>
|
||||
{{ end }}
|
||||
@ -1 +1 @@
|
||||
Subproject commit 4331b32265105a584dc387a349e92d3eabca7606
|
||||
Subproject commit 3f1d648b038fc93be501e0cac8101bd57b51039c
|
||||
Loading…
x
Reference in New Issue
Block a user