henrebotha
henrebotha on Hacker News
Location: Haarlem, Netherlands
Remote: Yes, if company has a legal presence in the Netherlands
Willing to relocate: No (willing to work in Amsterdam)
Technologies: Java, Typescript, Docker, k8s
Résumé/CV: https://www.linkedin.com/in/henrebotha/
Email: My HN username at gmail
I am a back end developer with 11 years of experience. I have worked everywhere from 3-person bedroom startups to one of the biggest tech companies in the world. I am very attuned to developer experience and will always strive to make it easier for people to get work done. I'm proficient at piloting coding agents to get quality work done fast.
I am on a "highly skilled migrant" visa and will require my employer to sponsor that.
That's a bummer. I was just wondering where my HD 280s went (did I sell them when I emigrated?).
So stoked to see the movement on this project. Once lofts are possible, it'll be so over for FreeCAD
I mean yeah, there are tools to automate it. I think you may have a point if both of the following hold true:
1. You very frequently have to install your setup from scratch.
2. Preconfiguring something that aids in installing from scratch is not viable or sensible. (Perhaps you work in an environment where you're not allowed access to your personal dotfiles repo, for example.)
But I think most people will fail at least one of these checks.
I don't think setup time is a fair comparison here. Any dev who cares to use CLI tools has a dotfiles repo that sets up everything in "under a minute".
dnsmasq on an RPi Zero 2W is the backbone of my self-hosted setup. Combined with Tailscale, it gives me access from anywhere to arbitrary domains I define myself, with full HTTPS thanks to Caddy.
It's a tough one. Lately I've been doing `rg -u` every single time because too many things get ignored and I can't be bothered to figure out how to configure it more cleanly to do what I want by default.
My QMK Tmux "layer" is still one of my favourite customisations. Prepends Ctrl-B to everything I type.
Oh my god, immediately worth installing just for this
I guess I don't understand the difference between semantic and syntax-aware, but I've been trying out difftastic which is a bit of an odd beast but does a great job at narrowing down diffs to the actual meaningful parts.
> this might become something like the em-dash—where artists start tweaking their work to look less like the AI’s that are copying them.
Literally how art has always worked
An opaque layer of transformation.
The former shows you things people (hopefully) have written.
The latter shows you a made-up string of text "inspired by" things people have written.
Yeah I've been running EndeavourOS on my 2015 Air (4 GB) and it is so incredibly snappy and efficient now. Makes macOS look like a lurching zombie of an OS.
There actually is no agreed-upon definition of "ultra-processed foods", and it's much murkier than you make it out to be. Not to mention that "can't be made at home" and "is bad for you" are entirely orthogonal qualities.
It's like food: Virtually all food is "processed food" because all food requires some kind of process before you can eat it. Perhaps that process is "picking the fruit from the tree", or "peeling". But it's all processed in one way or another.
This doesn't require anything fancy. I haven't used my sound engineering qualification in 14 years and I could do it by hand. You can visually scan through the recorded waveform and look for shapes that stand out. Simple audio processing techniques like using a noise gate to shut off the volume whenever the input level is below some configured threshold can make this even easier.
That's true, and it's why we're all using it. But those different renderers all support different ill-defined interpretations of Markdown. You can forget about all of them accepting raw HTML.
There are real limitations to this: You can't arbitrarily mix and match HTML and Markdown. As soon as you introduce an HTML block, you're locked out of Markdown syntax.
AsciiDoc lets you mix and match however you want. Or, put differently: AsciiDoc's superiority over Markdown extends even to being better at shelling out to HTML.
I couldn't find the PR in question. Do you have a link?
Beets crashes with a Musicbrainz connection error more than half the time, on my machine. How does anyone use it productively?
Oh my god, I had completely forgotten about that one until now.
> migrating all the doc that's strewn all over random SaaSes that people dropped it
I would love to be able to share our internal "all the things that are wrong with our approach to documentation" wiki page. It's longer than you could possibly imagine, probably more than 15 years old at this point, and filled to the brim with sarcasm and despair. It's so fucking funny. The table of contents is several pages long.
I would argue that the DataHand/Svalboard counts.
If you're going to do this, might as well go with AsciiDoc instead. It's vastly superior as a syntax. Markdown breaks down at the mere mention of something as trivial as a nested list item containing a table of blockquotes.
If I were sipping coffee when I read this, I would have had a lot of coffee on my desk right now.
Genuinely, I am trying to improve things. Making documentation more readable has a real cascading positive effect. Of course, most of these PRs are tiny — just a word or two — but that means it takes me almost no time to submit them, so the ROI is still positive.
One of the most enraging things to me is when a text search of documentation fails because the word I'm searching for has been misspelled in a key place. That's one of the things I'm trying to solve for.
I'm also just a stickler for good style. It bums me out when people misuse heading levels. Heading level is not a font size markup!
Of course doing this does generate activity on my GH, but I think all of us have probably moved on from caring much about the optics of little green squares.
Also like someone else said, it's just fun. I like typing and making Git do a thing and using my nice keyboard.
Don't let them win. Stand proud with your "–" and your "—" and your "…" and your "×".
I don't love emojis for this purely because they're graphically inconsistent; I can't style them with my terminal font or colour scheme. But I'm a huge fan of using various (single-width) unicode chars with colour to make terminal output a lot easier to parse, visually. Colour and iconography are extremely useful.