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.

Not so much screaming as staring in disbelief, mumbling profanity in his direction...

When my department lead said "I don't think this unit testing hype or code reviews make much sense, it's more efficient to just make a checklist and test the application yourself"

This was the QA department of an aerospace company, we wrote NDT software to do image recognition on xrays of alloy welds and micrometer laser measurements on fuel tank surfaces. Software which is quite mission critical, a single misrecognized welding fault could literally cost up to half a billion dollars — not to mention that it's a very sabotage & espionage sensitive industry.

After raising some hell he was replaced though.

Sales Advisor: "4GB is more on a mac.. they use different measurements.."... at that point I gave up trying to get some info out of him

Fuck the imperial system. For centuries everyone used meters and kilograms to measure shit so why the FUCK did the U.S decide to use pounds and inches. Like i see most articles and videos comfortably using the metric system, EVERYTHING uses the metric system. then i stumble on an idiot who makes me go to a converter so I can understand his pound-inch-based lingo. FUCK YOU

Why are Americans so stupid?

Date format: MM/dd/YY => what is this? It‘s not even in order

Length Units: Inch, Feet, Yard, Mile => good luck trying to convert in in a hurry without a calculator

Cooking recipes: cups, tablespoons, pinches => land of the freedom, especially for measurement errors

Temperature: Fahrenheit. => some dude who thought, „oh this is really hot, lets mark it 100“ and the other day „oh this is really cold, I got the 0 mark, sciene“

Weight: ounces ~ 28.34952 g, ton ~ maybe 907.xx kg, it depends

Time: Americans think the week starts on sunday, so they assume it does so for everyone else (f*** you american developer, designer, I mean you)

Football is football. Everywhere. In. The. World.

Politics: Trump, Weapons, health system, worker rights, ...

God, I hate America and their bs.

Me: "Concierge, I have noticed this issue with live potential on ground a couple of months ago, just a friendly reminder that this still hasn't been fixed."
Concierge: "Well yeah this building is certified (god I hate that word) so whatever measurements you've taken, it doesn't mean anything when it isn't done by the electricians."
M: "Aha, back to that piece of paper huh.. taking measurements requires a piece of paper these days, doesn't it."
C: "Glad you're quick on the uptake."
M: "Well I have the brains in my head to do a proper measurement without dying, and the numbers don't lie."
C: "What do you think that the landlord is going to say? I'm sure you still remember that email "DON'T TOUCH THE ELECTRICITY!""
C: "And remember that she'll probably rather file a complaint against you than to let an electrician come check it, because the latter costs money for something that's already certified."
M: "Well that sucks..."
C: "The certified electricians certified this building. Your hands are pretty much tied."
M: …

*walks off in frustration*

Now, as for the rant. *inhales deeply*

YOU KNOW WHERE YOU CAN SHOVE THAT PIECE OF PAPER?! DOWN YOUR FUCKING ASS! WHAT DOES A FUCKING PIECE OF PAPER MEAN TO JUSTIFY WRONGDOING?! WHAT DOES IT FUCKING MEAN WHEN IT ISN'T BACKED BY A FUCKING BRAIN?!

Yet I apparently can't do anything, because I refuse to certify myself. Now you know why I fucking hate certified enganeers, and why I use that word. The piece of paper doesn't mean shit when you can't back it with an actual fucking brain. And requiring a certificate to do stupid shit, even for changing a fucking light bulb, or a switch or an outlet or whatever. Certified enganeers, because fuckers like that don't deserve to be called engineers. You know what, certified motherfuckers? FUCK YOU!! I can change it myself and I don't (shouldn't) need a bloody fucking certificate for that!!

So I just received this second DSP5005 DC-DC programmable power supply. Time to make an enclosure for the thing!! 3 power supplies totaling at around 1kW, and 2 variables connected to the 50V 10A one, through external banana wires (I want all of this to be modular). No biggie, take measurements for the AC-DC supplies, add in the variables on the front, and cut it out.

So, I went and did just that. Now my 500W (50V 10A) supply is a bit larger than the others, and it's got a fan. So I figured, well then probably my 24V 8.3A (200W) and 12V 15A (180W) supplies could use some cooling as well. But how am I going to achieve passive cooling without a spacing between the supplies?! So I thought of some spacer design. It had to be out of wood, and I had some 4mm MDF and some IKEA parts around. So, 4mm MDF for the plate and 8mm wood spacers from IKEA for the spacing. And some super glue to hold it all together.

Weighing my power supplies against a 1l bottle of milk, it seems like my power supplies are ~500g. Great, so the top spacer would take 500g and the bottom one 1kg + the weight of the top spacer.

I ended up building one plate with 6 spacers in it yesterday, until I got too tired. Then I placed my entire weight against it, 20kg at least. It didn't budge. Pretty good for something that's only designed to withstand a 1kg load!!

So, I made something good with only a 10x18cm piece of MDF, some garbage from IKEA, and most importantly a bit of a brain. Something that can handle 20x its designed load no problem. Manufacturers, is it really right to produce shit when I can beat your manufacturing processes big time without an assembly line?!

I’m pretty terrible at soldiering and small electronics in general, but I’m kind of okay with how this turned out.

Back story:
That helmet is my sister-in-law’s, she drives a polaris slingshot. (It’s technically a motorcycle here in the US because it has three wheels.) and she hooked up some EL wire to her helmet and the larger black rectangle in the picture is what the battery pack looked like before. (It takes two AA batteries.) and doesn’t have anyway to recharge them natively.

I did some research and found a neat little charging board (TP4056) and got her a small single cell li-ion battery for it. Now it’s not only less than half the length of the original, but it has a rechargeable battery and a charging circuit built in. The battery is 500mAh and lasts about 65-70mins on a charge. Personally, I feel like that’s not a good enough battery life on a charge, but my sis-in-law says that her and her slingshot friends usually only run with the EL lights on for 30 minute stretches at time so they should be able to get two to three uses before needing a recharge. Which btw, only takes about 35-40 minutes from completely dead.

The box looks like shit cause I literally hacked away at the original casing with a pocket knife and then crammed all the pieces back in and hot-glued the casing together. But I took measurements of the final-ish design and will try to find a small electronics box that will be able to house everything internally. (L: 1-3/4” W: 1-1/4” H: 1-1/4”)

So there's this developer I work with. Let's call him Kevin.

I am a UX designer, former Developer from IBM - but I really love design, so I made the switch. My background however, usually makes working with Developers easy.

But not this guy! I provided a clickable prototype complete with code to easily inspect with Dev tools for measurements. I provided mobile references for some screens but not all.

Kevin submits screenshots for me to review the design. Looks nothing like the prototype, so I get out my Wacom tablet and basically draw redlines over the screenshot. "No border here, 22px should be 20px, etc."

His response was:

"I need you to say exactly what you one (want?) each pages and mobile pages to look like, text size of the font, etc.

You did a lot of red marking, so I am asking for clarification."

So basically asking for red line specs. I asked a month ago if he wanted all the mobile screens, or if what I provided was enough along with the style guide. He agreed. So now I'm majorly pissed off.

Maybe it's also the fact that one of the other developers has to hold his hand, because everything he does is bad. 😡 And his lack of ability to articulate a damn sentence effectively drives me crazy. Cherry on top, I suppose.

Would love to bring this up with my boss. ♥️ And suggestions. 😍

Received screen designs for a new website in Adobe Illustrator format with all the measurements in centimetres.

I think that two criterias are important:

- don't block my productivity
- author should have his userbase in mind

1) Some simple anti examples:

- Windows popping up a big fat blue screen screaming for updates. Like... Go suck some donkey balls you stupid shit that's totally irritating you arsehole.
- Graphical tools having no UI concept. E.g. Adobes PDF reader - which was minimalized in it's UI and it became just unbearable pain. When the concept is to castrate the user in it's abilities and call the concept intuitive, it's not a concept it's shit. Other examples are e.g. GEdit - which was severely massacred in Gnome 3 if I remember correctly (never touched Gnome ever again. I was really put off because their concept just alienated me)
- Having an UI concept but no consistency. Eg. looking at a lot of large web apps, especially Atlassian software.
Too many times I had e.g. a simple HTML form. In menu 1 you could use enter. In menu 2 Enter does not work. in another menu Enter works, but it doesn't submit the form it instead submits the whole page... Which can end in clusterfuck.
Yaaayyyy.
- Keyboard usage not possible at all.
It becomes a sad majority.... Pressing tab, not switching between form fields. Looking for keyboard shortcuts, not finding any. Yes, it's a graphical interface. But the charm of 16 bit interfaces (YES. I'm praising DOS interfaces) was that once you memorized the necessary keyboard strokes... You were faster than lightning. Ever seen e.g. a good pharmacist, receptionist or warehouse clerk... most of the software is completely based on short keyboard strokes, eg. for a receptionist at a doctor for the ICD code / pharmaceutical search et cetera.
- don't poop rainbows. I mean it.
I love colors. When they make sense. but when I use some software, e.g. netdata, I think an epilepsy warning would be fair. Too. Many. Neon. Colors. -.-

2) It should be obvious... But it's become a burden.

E.g. when asked for a release as there were some fixes... Don't point to the install from master script. Maybe you like it rolling release style - but don't enforce it please. It's hard to use SHA256 hash as a version number and shortening the hash might be a bad idea.

Don't start experiments. If it works - don't throw everything over board without good reasons. E.g. my previous example of GEdit: Turning a valuable text editor into a minimalistic unusable piece of crap and calling it a genius idea for the sake of simplicity... Nope. You murdered a successful product.
Gnome 3 felt like a complete experiment and judging from the last years of changes in the news it was an rather unsuccessful one... As they gave up quite a few of their ideas.

When doing design stuff or other big changes make it a community event or at least put a poll up on the github page. Even If it's an small user base, listen to them instead of just randomly fucking them over.
--
One of my favorite projects is a texteditor called Kate from KDE.

It has a ton of features, could even be seen as a small IDE. The reason I love it because one of the original authors still cares for his creation and ... It never failed me. I use Kate since over 20 years now I think... Oo

Another example is the git cli. It's simple and yet powerful. git add -i is e.g. a thing I really really really love. (memorize the keyboard shortcuts and you'll chunk up large commits faster than flash.

Curl. Yes. The (http) download tool. It's author still cares. It's another tool I use since 20 years. And it has given me a deep insight of how HTTP worked, new protocols and again. It never failed me. It is such a fucking versatile thing. TLS debugging / performance measurements / what the frigging fuck is going on here. Take curl. Find it out.

My worst enemies....

Git based clients. I just hate them. Mostly because they fill the niche of explaining things (good) but completely nuke the learning of git (very bad). You can do any git action without understanding what you do and even worse... They encourage bad workflows.
I've seen great devs completely fucking up git and crying because they had really no fucking clue what git actually does. The UI lead them on the worst and darkest path imaginable. :(

Atlassian products. On the one hand... They're not total shit. But the mass of bugs and the complete lack of interest of Atlassian towards their customers and the cloud movement.... Ouch. Just ouch.

I had to deal with a lot of completely borked up instances and could trace it back to a bug tracking entry / atlassian, 2 - 3 years old with the comment: vote for this, we'll work on a Bugfix. Go fuck yourself you pisswads.

Microsoft Office / Windows. Oh boy.
I could fill entire days of monologues.
It's bad, hmkay?

XEN.
This is not bad.
This is more like kill it before it lays eggs.
The deeper I got into XEN, the more I wanted to lay in a bathtub full of acid to scrub of the feelings of shame... How could anyone call this good?!?????

Absolutely not dev-related.

Blah, blah, weird conversation and shit. I'm too tired and lazy to write this crap again, but let's do it.

The guy is a dev I randomly found on some chatting service, he was interesting to talk with until this conversation. I'll write this out of memory, so yeah.

Him: So by the way I wrote an app that you give your penis size to to get measurements and stuff about it.
Me, thinking it was dev humor: That's hilarious. Tell me more, I'm interested.
Him: So the idea behind all of this was to gather some big data style info about people's penis size and habits and all that stuff.
Me: Man that's awesome. Can I see the source?
Him: No, it's proprietary. You can buy a license though.
Me: You went that far for a joke?
Him: What joke?
Me: The whole software you just told me about.
Him: That's not a joke, I'm being very serious about it.
Me: Oh well. What did you get from the stats?
Him: I got some tips from people's habits! I never thought that shaving it could make it look bigger, but that's awesome!
Me: Do you really care about it that much?
Him: Studies have proven that size correlated with confidence. Since I started doing it, I've been more confident than ever!
Me: Great.
Him: I'm a bit disappointed to see that I'm in the lower percentiles though.
Me: Well of course you are.
Him: Why would you say that?
Me: Well since people with a big dick tend to go more willingly into the subject and might even buy a fucking app for it, of course you'd have the higher average in your stats.
Him: You're only saying that because you have a small cock.
Me: Why the fuck would you say that? You're the one that's concerned about it, not me.
Him: Go on, what's your size?
Me, because I don't care about discussing that stuff: *Tells him*
Him: [stats, comparisons and stuff]
Me: Well I never gave a fuck and your stats won't make me change my mind.
[ ... Some other shit about my size compared to his ... ]
Him: Would you want to work with me for the database maintenance?
Me: You must be joking?
Him: I'm serious.
Me: *Deletes account*

Seriously, fuck that guy. I rewrote that quickly so you only had the best, but it was a whole fucking conversation.

I fucking hate people who report somebody else's work as their own successes so much.

I've written a fair amount of perf tests for our project so far (actually I'm like the only person doing that). Some fucker from another team asks me if I could write one more. I agree, because why not. I spend a few hours, making sure to cover all cases and commit the test. Then the same fucker runs it and reports it as HIS PERFORMANCE MEASUREMENTS.

0 credit given to me. Fuck you, I just wanted to be helpful and you used this.

I'm still quite young and tend to fall for shit like this, but getting more and more grumpy because of those people.

Most successful project at work: NodeJS utility for storing loads of measurements from an application running on various other systems and providing fast ways of getting at that data. No DB, just CSV files broken into time periods. Also has a search function written in C that can very quickly find all user sessions matching the criteria. It's not perfect, but it does the job pretty well and I can tweak the storage engine as much as needed for our use case since its all custom written.

Outside of work: Incomplete right now but I soldered some wires onto an old sound card and managed to get an Arduino to configure it and play some notes on its FM synthesis chip. Still quite a newbie to electronics so this was quite an achievement for me personally.

iPhone > Settings > [bluetooth-speaker] > Device Type > “Speaker”

Why?

Because “Specifying the type of device can ensure your Headphone Audio Level measurements are accurate.”

Alright, fair enough.

But, BUT!

Headphone Safety doesn’t fucking care for the chosen device type. It still reduces the sound if turned ON.

It’s good that I can have accurate measurements but what the fuck is this bullshit?!

To iPhone,

If you can accurately measure the audio by respecting the device types, why the fuck can Headphone Safety not respect the same types? Why the fuck does it have to treat every bluetooth device as a headphone?

Is this actual bullshit or am I missing something?

You think americans are weird with their imperialistic units [inch, ounce, yard, pound, mile, ...]?

You think canadians are weird with their mixture of imperialistic and metric units [miles, liters, ...]?

Well I think we are all weird with our am/pm nomenclature when we start counting at 12 and end with 11 [12pm, 1pm, 2pm, ..., 11pm, 12-fucking-AM]

good luck making sense of that one!
"please run this command at 12pm sharp" -- is that noon or midnight? Did the chap writing this know which is which?

TIL that our creative design team that produces our web designs/layouts are all print designers. They were stumped when I gave them a wireframe mock up as the base for a website design for the first time, with no defined pixel measurements.

Why can’t Headphone Safety in iPhone just fucking respect the Type of my Bluetooth Device?!

Why the fuck does it HAVE to reduce the sound of my Bluetooth speaker even though the Device Type is set as fucking speaker!!

Do whatever the fuck with “accurate measurements” of audio levels but just don’t fucking treat my headphones and speaker as same when I explicitly set them differently!

For Andromeda’s sake!

I'm really pissed. The kitchen builder doesn't trust my measurements, which is fine. Appointment with their specialist was an hour ago. Architect is on vacation and it was discussed last week that we can enter the construction side and the kitchen. No builder wanted to open the door for us! Even after talking to them. I had to phone the architect, this took so long. The measure specialist didn't want to wait, which I understand. I hate people, they always make things complicated. I really hate people! Sorry that this is none dev related

God damn the last few days:

JUST give me some modular-ish code that is a bit more explicit and doesn't measure every fucking thing over and over.

Like I get how taking a couple .lenght and a bunch of other variables adds up to "Make a meat lovers pizza".

But fuck man when the code goes all over the place just give me a block of code that measures all that shit in ONE PLACE a god damn pizzType variable that I can use elsewhere and just fucking know what is going on.

Every damn corner becomes this maze of measurements that you cant be sure is exactly the same unless you fucking watch every damn variable, I get how that happens but god damn.

Just happened 4 days ago.
I was writing a thesis and at the same time creating a tool which automates my measurements.
It was written in Python and everything worked very well.
Of course I left it to my advisor for further measurement, telling him that if he want to measure multiple times he just need to loop over the measure-function.
I left him an example-file which looked a little like this:

example.py:
"""
import measurement_class

# Parameters

if __name__ "__main__":
m_class = measurement_class.coordinator(#Parameters)
m_class.measure(#someotherparameters)
"""
So after a few weeks I came back to my advisor (four days ago) to see this:

loop_over.py:
"""
import os

for _ in range(0,100):
os.system("python3 example.py")
"""

I'm not sure how I should feel about it...

Guys, what is the worst thing that could happen if you don't take measurements against big tech companies spying about what you are doing?

This awesome moment when you‘re late into your thesis, find a possible improvement that would require new measurements, but then find out that this improvement can‘t be done with your constraints and there is nothing to do❤️

When you receive a psd file with a million layers, when all you really need from it is the colour values and what font/size they've used and some measurements. You'll just do it all properly with CSS. Better off with a flat png or 2 with transparency and some original vectors.

"There are too many elements on most web pages to affix or align each one to the baseline grid. Doing so would require a mathematical rigor that, if it can be achieved, might produce rationally exact measurements and placements but will most likely be something less than elegant. The result would be a design driven by math, rather than a design that uses math to create an elegant product." - Khoi Vinh

Watched UFO 2018.
Movie mostly about guy trying to solve math problem but nice.
Learned about fine-structure constant and that all base SI units were redefined in 2019 lol.

I don’t remember anyone mentioned that scientists changed all of standardized measurements.

Overall nice movie if you like those about solving imaginary problem without special effects etc...

Looks like nobody cares how much kilogram weights.

I was working on a bug in a parser for the response from an api which returns 'n/a' when a certain measurement isn't available. The code was "if ($value == 'n/a')" and when this was true the value was rejected (language is php).
Some of you may instantly understand the problem here. I didn't. Some of the measurements were 0 which is ok, but for some reason it didn't accept them.
Then I discovered the bitter truth:
0 == 'n/a' is true!
Apparently php tries to convert the string to a number to compare it and if it fails it returns false, so false == 0

😞

A workout platform, which isn't focused on "hard" facts like hr or distance, rather using "soft" measurements like: Was the workout mentally demanding? How was your sleep? Etc.

Then combine this with some "hard" facts and see what makes your training more effective.

The api is more or less finished. Now the apps have to be developed.

Adobe Illustrator worst program ever!, Need to get measurements from a webdesign and it takes for ever to load, missing images and fonts fuck this shit.