392 karma · joined November 13, 2019
[0] https://exposure.software [1] https://www.gentlemencoders.com/
I don't think it's too far off the mark for Australia. Mind you, that's gross. US$180 is about AU$280k. Of that, you'd pay around AU$100k in income tax (and then there's a 10% sales tax).
One of my kids basically sailed through his first 12 years of schooling on pure ability and zero effort. He's now learning the hard way that innate talent only gets you so far. His brother doesn't have the same innate academic ability, but is a natural grinder. He's finding the later years of schooling are easy to adapt to because he can pick things he's good at and knows how to put in the effort.
In terms of praise, we over-index on effort because it's a cross-cutting concern. This is especially true at younger ages where kids can't choose what they're studying. So if they get a C in French but maxed out all the effort criteria, I'm more than happy with that - and it's something for them to keep in mind when they're picking subjects later down the line.
In neurology at least, I think a lot of the problem is that everyone is hyper-specialized. Luckily for us, my wife's insurance company convinced a generalist neurologist to come out of retirement and examine her, which put us on the path to effective treatment. But yes, that whole experience completely soured me on blind trust in the medical profession
- When generating code, do not provide an explanation unless I ask you to.
- When generating code, prioritize brevity and performance.
- Do not apologize.
I find the responses much less sycophantic, even when not relating to code. I asked chatgpt about this:
> In general, your instructions guide me to provide responses that are succinct and focused on performance. They also signal your preference for direct communication without additional context or explanations unless specifically requested.
The main thing is that Joplin is still markdown, and I can trivially export if I want to switch to something else.
Having not used, but only read about graphql, this was the first thing that struck me. It seems great at minimizing data transferred to the client, but it doesn't (seem to) stop that data being fetched from the DB - it just post-filters it.
I'm imagining a scenario like a dashboard, where you're getting a small amount of data from a lot of places. With REST, we'd generally do that by having a dedicated endpoint for the whole dashboard that executes a single query, letting the DB do what it's good at (efficiently retrieving required data). My naive impression is that graphql would execute a bunch of queries, trim what's not needed and join it all together. With anything non-trivial that seems like a performance nightmare.
It seems no matter how much you know about vim, there's always more.
Parenting seems like an example of L.A. Paul's "vampire problem" - where you're such a different person after an event that it's not possible to evaluate it as the person you are before the event. But it's actually more complicated than that.
If I had to choose between being completely destitute and one of my kids' lives, it's not even a decision. But when considering if to have another child, comfort and affordability have a huge influence - even though, as a parent I already know that the moment the child is born, they would become incomprehensibly precious to me.
So I have the ability to bring into existence something would for certain massively increase the joy and purpose in my life, and yet I don't... for the same reasons that I criticized you for in a sibling comment.