technimad
technimad on Hacker News
I own an emotiscope[1]. Crafted by a solo developer that went on to do other things. This device seems to have implemented the hard part pretty well. Different algorithms with minimal delay.
1. https://github.com/Lixie-Labs/Emotiscope
Posted by
technimad on Thursday April 02, 2026 @12:34PM
from the github.com dept.
Posted by
technimad on Thursday February 05, 2026 @03:49PM
from the ip-geolocation.apple.com dept.
As a user I don’t get why Apple allows this user hostile behavior in an app they distribute in their app store.The platform has alternatives. iOS has a sharing sheet. iOS has a default browser setting (in EU).
Passkeys are what you describe here.
FTA: A chat bot can handle expected, middle-of-the-road queries (as in, for a bank, “what’s my balance” and so on) – but customers can get those answers already from the app or website.
This is where the author misses the point. Chat bots will be te main interface in the future. Especially for these mundane middle of the road queries. Integrated into voice controlled ai buddies.
Honest question: why are you vaccinating while you also identify as low risk?
Why sample otel spans and miss out on the important ones?
In my career I got quite some technical certifications. Any cert shows you are taking your job seriously and you are willing to learn.
The following three certs helped to show I know my field really well and these separated me from others that just say they know it. Cisco CCNA/CCNP, Linux institute LPI and Agile Alliance certified Scrum master.
Later on I used certifications to quickly pivot into a niche, sometimes when already practicing the role. Architecture (togaf) and product management.
https://erwinvrolijk.nl
Static site hosted on gitlab pages. Build with the zola static site generator using gitlab cicd.
Posted by
technimad on Monday March 21, 2022 @05:38PM
from the grumpy.website dept.
Many moons ago I created all graphs in the LPIC2 exam prep book [1] using graphviz. The book is open sourced now, and all dot files are preserved in the accompanying repo [2].
One thing I learned creating these graphs was that with some tinkering you have quite a lot of control on how the result will look, without littering the semantic in the source file with a lot of markup.
I choose graphviz because the dot notation can easily be checked into source control. It is also easy to create reproducible results using a makefile.
[1] https://lpic2book.github.io/src/
[2] https://github.com/lpic2book/src/tree/main/docs/images
I’ve fixed production bugs by removing code copied verbatim from the PHP manual. It looked like the clueless previous developer had copy pasted code from all over the place until the code sort of did what it was supposed to do. The code snippets by itself were ok, the composition created numerous bugs.
"A backup not restored is a backup not made." Should be on the wall in every IT department. Together with "Snapshots are NOT backups".
Probably none. Why should telemetry data sent from Mars be encrypted? Encryption makes the system more complex and requires more computations and power on Mars.
Some retailers already use RFID to track items around the store.
They track the full journey of items around the store. Which items go into the fitting room together, which will be eventually bought, etc. Not to combat theft, but to optimize store display and advise given by store clerks.
This tracking also allows for accurate inventory display online. A store is in effect a warehouse for the on-line channel.
As a user I really don't like sites disabling autofill. In this case, you make me type my address, because you want to use one address field.
A better solution would be to detect safari, and present multiple fields, which will be autofilled. You can then concatenate these fields in the backend to whatever you like.
The future of iPhone charging is wireless. The current iPhone12 with MagSafe is the first of the new system. I predict future iPhones will have no physical ports at all, 100% wireless.
This script is too much boilerplate and opiniated for me. I maintain a snippet with the most important settings for safe and robust shell script execution:
https://gitlab.com/-/snippets/1968838 I'm now thinking of adding the trap cleanup boilerplate to my snippet as well, as it tends to get overlooked too often.
A trace should answer why a query is fast or slow. It should provide enough information to a dba (which I’m not) to determine in which domain the most likely optimization is possible. I.e. the query itself, db configuration and tuning or underlying infra.
I don’t like the devaluation of the word observability. A chart like this used to be called something like ‘tools to monitor and understand postgres’.
Observability is the ability to derive the internal state of a system from the outside. Usually done through traces.
It would be great if Postgres could emit a trace per query, showing in real-time which internal components were hit by this query. A sort of continuous query explain service.
Combine these traces to database clients and other front end services and you’ll be able to point to the front end service version which causes cache misses deep inside postgres.
Did you notice you can hold and slide to change volume? You don’t need to hit the volume slider where it appears. Same with brightness.
Totally undiscoverable gesture.
Indeed, ECMP uses some kind of hashing (dependant on the implementation) to do the distribution and doesn't take different line speeds into account at all.
Great improvement if this project does take this into account.