The project where I realized I wanted to go from chemist to pro dev.

I built a flow-chemistry spectrometer with monitoring backend in Haskell.

Spectroscopy is where you add a reagent to a glass tube, it changes color, and by measuring the exact color it tells you how much of something (for example, a toxin) is present in the sample.

I had to do that a lot on factory samples, writing down measurements using pen & paper.

I'm lazy so I decided to do the logical thing: Automate it. I bought a second hand spectrometer, stripped the casing, did a shitload of glassblowing and hooked up tubes to the production pipelines, so I could get samples, mixing them in the correct ratio with reagents in continuous flows using valves.

I ended up using 2 home-crafted arduino-like boards (etching PCBs is fun!).

One to calibrate the mixture against known samples and control solenoid valves to continuously cycle through various reagents and deionized flushing water, the other to record the measurements and send them to a server running a Haskell/Yesod API.

The server collected the information into InfluxDB (A time series database), displaying all data on a graphite dashboard.

Eventually I wrote Haskell plugins for most of the chemistry processes, from pH & temperature measurements to polymer property and pigment tests (they made a lot of printer ink).

Then I was fired because they didn't need chemists anymore, and the code "could be maintained by the intern" (poor guy)...

But I did find out that I loved functional programming, chemistry automation projects, and crafting my own electronics during that time.

I've tried so many ways for that at night or during walk spark of bug solving ideas:

- fluorescent ink on regular paper
- florescent mini whiteboards
- "alexa remind me.."
- writing down in my phone
- recording on my phone
-..

But all of those due to my short term memory made me forget half the things by the time I opened the fucking phone/app, found where to grab the pen or the whole dance for alexa, to remember the exact phrase I have to spell out, when it should remind me, what time,..

Earlier today I remembered how I had a little tape voice recorder I used to use a ton, thankfully that tech advanced by now and found myself a stereo mic setup little voice recorder that can also act as an mp3 player!

Went for a walk today, while listening to some podcasts, then it hit me as usual on how to fix and implement some things that were awkward at best on paper when I left home, pressed the record button, recorded it and went straight back to music mode, which remembered where I left off!

I'm so indescribably happy, I ordered quite a bunch of the same to just throw around everywhere, at the bed, in the bathroom, kitchen, for walking outside, everywhere haha

Not a part of the test, but the test itself.

Imagine having to write in a language you don't really know with a pen and paper.

Glad I didn't get the job there because holy moly was that a pain in the ass.

So I was thinking about SSL and trying to understand it (random thought that just came up while eating lunch). I came up with this analogy, not sure if maybe I've heard it before... Is this understanding correctly?

A and B want to send letters but make sure no one other than them can get in on the conversation or impersonate them.

Each is able to create a pen and glasses that must be used to see the ink.

So when they first connect, they exchange the pens.

So even if a middle man can duplicate the pen he can't actually read what anyone is saying. And if he tried to write something, the receiver will know it's not sent by the other since it makes no sense. So they then write a new letter and agree to send each other new pens and use new glasses?