cel1ne

Nice work!

If you want to get the site-size down, like the top-comment suggested, you can switch from React to preact.

> Can't we just let stuff work? I'm no fan of MySQL, but can't we admit that a ubiquitous and battle-tested piece of technology, applied to a canonical use case, on tiny data under near-ideal circumstances, is probably going to work just fine?

I call that "separation of error-domains", meaning trying to find interfaces where you can separate off parts of your application, so debugging gets easier:

Is the bug in the database, or in our code?

There is just some kind of internal resistance increasing the major-version for a breaking change, especially when that change is just tiny.

I have published a library myself and experienced it, going from 2.x to 3.x to 4.x.

After you just do it for the sake of semver though, the resistance vanished for me.

And the second thing: Never use 0.x.x versions, I think those should have been omitted from semver completely, as they circumvent the entire concept.

> They recognize very subtle deviations in frequency. I have had a person tell me "It's too sharp" when I was only off by 3 cents according to the tuner.

Ok, but THAT I have. I don't have absolute pitch, but I was always able to tune my cello more precisely than my teacher. (and other instruments too, not limited to one person)

I am the same, I learned it using a piano.

The question is: If you can remember what C1 or whatever sounds like and then deduce from that, is it not just a way of more learning to be able to remember the other ones too?

Is there really a fundamental, functional difference between absolute pitch and "normal" hearing?

Yes, just put a + in front of the double-quotes and you get what you want.

Open a pdf in preview. Select pages, press Copy, then Cmd + N.

You get a new PDF with the pages you copied.

> In some of the fancier fonts on macOS, the characters actually change slightly if there are other characters nearby.

Do you mean kerning and ligature or something else?

Shift + Command + 4, then space-bar -> capture windows.

Side-channel attacks are an inherent property of computing hardware. You can never fully "disguise" a computation as a different one or as no computation.

You can just lower the signal to noise ratio by various means, so you gain some time until better statistical methods or clever tricks filter out the signal again.

When I copy a command to paste in the terminal I always start the selection from the end and move left to the start. That way I won't accidentally copy a newline.

Version the API and switch to Java-time everywhere. Or forward everything to another class.

Yes, and the main culprit of JavaScript is excessive GC, because of excessive object-creation.

Developers are careless because JS is so fast, but they forget the hundreds of milliseconds of GC-pauses that occur because they never think about the memory they are allocating and throwing away each second.

I know this from Android, but not from iOS.

Math with time (and space/memory)... You just found the difference between computer science and math. And the reason proof-of-work in blockchains is possible.

Just a tip, if you want this to become internationally used:

"Klo" means "toilet" in german.

Very subjective, but HNs comment culture went down in the last 1 or 2 years or so. (Reddit-style discussions, jokes etc. seem to be more common now)

I have worked for many years as a software-developer and found that more than 5 effective hours per day are impossible or at least not sustainable.

30-32 hours per week is perfect. More is just useless.

I have heard that this seems to be true for most intellectual work that requires concentration (5 hours daily max). No sources on that, though.

"Strong opinions, weakly held" makes sense in exactly one situation: When you are definitely an expert in a topic you should have your strong opinions about it.

But since everybody is sometimes wrong about something, and that should be very seldom in the expert case, you should be able to let go of one of your opinions, in case you get counter-arguments.

This is not an IT specific problem.

For most jobs they don't do themselves people tend to understand the time it takes.

If you have a mac, look into GitUp. It's a great git-client and it creates a timelined snapshot-backup after every action, so you can undo whatever you did.

Did you read parent poster? What good are noise-cancelling headphones if you can't listen to music because it's distracting?

The following is simplified.

Managers are people who enjoy being around groups of people more than they enjoy being around “things”.

ICs tend to reserve more time thinking and working alone and enjoy talks with individuals more than navigating group-dynamics.

Enjoyment in groups leads to experience in group dynamics. Experience in group dynamics and having many relationships gets you more chances to climb up the salary ladder.

Reminds me of “rm -Rf” meaning “read mail really fast” ;)

Kotlin, gradle, closure and tachyons.css.

I wrote a short buildscript for that setup that i copy.

I'm really happy to hear that. All the best.

It is a fine line, yes, but if you abstain from any accusations in the rest of the text, then my formulation is generally received as empathy. This is supported by the fact, that there are no lies there. OP _is_ sorry that things went as they went. And it also is objectively “unfortunate” in the sense that with a little luck there might have been a different situation.

The general point is that OPs partner is in a corner. Empathy is needed to allow him to be cooperative and understanding of his own mistakes.

Without any accusations, tell him the path where you‘re heading in written form. You can add potential remedies and the end, but in essence, describe what will or might happen. A good phrase in these kind of messages is

“Unfortunately you didn’t have time to look into XYZ. I’m truly sorry that we now face ABC. But if we do EFG we might still have a chance in fixing this”

In general: use written form, avoid any phrases that put the blame on him, describe accurately what happened and the consequences and end on a hopeful note or idea.

If I had to give one Tipp about front-end development: transition the buildsystem to gradle and call webpack from there. Also npm can be managed with it.

Then you can slowly introduce kotlin code, which is way more productive.

In the end I found that writing everything in kotlin, using tachyons for CSS, the kotlin-minifier for code minification and closure-compiler for optimization is the most stable way to go.

JavaScript isn't a productive language. Having build-tools in JS just complicates everything.

Humans feature meta-cognition. I suspect you felt better and more relaxed due to the mechanism, and that in turn gave you another big boost by showing you that you are still capable to feel and act different.