thehappyfellow

15 ms·

1.
by thehappyfellow 21d ago
I'll take that.
2.
by thehappyfellow 21d ago
They are amazingly good at creating hype (non-derogatory) and getting users. Their docs say "Omarchy takes security very seriously" - I think that's straight up incorrect. Saying "go and use it, wanting: its prototype qu
3.
by thehappyfellow 21d ago
I dont just complain. I making the world a better place in ways which I believe are worth it. Improving Omarchy seems like a waste of time to me. Letting people know how insecure it likely is, given how little time it took, is much better b
4.
by thehappyfellow 21d ago
Appreciate it! Editorialised is fine but the post is mostly about the development practices leading to bugs & the lack of awareness of how dangerous that is, not about the current absolute number of security holes if that makes sense.
5.
by thehappyfellow 21d ago
Why would I do that? It's a crazy non-sequitur. My opinion is that the way Omarchy is developed leads to gigantic security holes. I wanted people to be aware of it. In my opinion, there are much better choices both for me and I'd
6.
by thehappyfellow 21d ago
Aww, thank you!
7.
by thehappyfellow 21d ago
How is my title a rage bait? The current submission title is terrible, "Omarchy development practices lead to predictable security issues" would be much closer.
8.
by thehappyfellow 21d ago
It wasn't supposed to be, I found it amusing. Also, the current title is not what I wanted people to take away from the post.
9.
by thehappyfellow 21d ago
> What kind of blogging is this? Happy to explain: it's personal blogging, for writing down what's on my mind. The fact that it was addressed swiftly doesn't affect the claims in the post at all: I'm worried about dev
10.
by thehappyfellow 21d ago
Yo, why is my blog post title editorialised? It should've said "Merchants of Insecurity". Rude!
11.
by thehappyfellow 21d ago
They point to two separate issues, what are you about?
12.
by thehappyfellow 21d ago
There's a difference between a few small bugs because software is new and a half dozen eval(untrusted_input) in version 4.0. Maybe this can get fixed, security teams won't make it worse. I worry they're mopping the floor and
13.
by thehappyfellow 5mo ago
That's what I had in mind! The whole post is a claim that evaluating knowledge work got more expensive because cheaper measures stopped correlating well with quality. If someone was already evaluating the work output using a metric clo
14.
Simulacrum of Knowledge Work(blog.happyfellow.dev)
213 points by thehappyfellow 5mo ago|84 comments
15.
The Subprime Technical Debt Crisis(blog.happyfellow.dev)
7 points by thehappyfellow 6mo ago|0 comments
16.
by thehappyfellow 7mo ago
Which means you can't select all on text which isn't editable - insane!
17.
by thehappyfellow 8mo ago
My blog is at https://blog.happyfellow.dev if you'd like to read it. I'm also the Head of The Institute for Type-Safe Memetic Research which website is https://typememetics.institute/
18.
FFmpeg-Rs Fundraising Initiative(typememetics.institute)
5 points by thehappyfellow 10mo ago|0 comments
19.
by thehappyfellow 1y ago
Author here. I wonder about that as well!
20.
by thehappyfellow 1y ago
Of course practitioners shouldn't expect to understand the bleeding edge without investing a lot in learning the subject. However providing people with software engineering background an easier on ramp for understanding PLT would be ni
21.
by thehappyfellow 1y ago
It's closely related to another truth: Unconstrained curiosity is a vice, not virtue.
22.
by thehappyfellow 1y ago
Thank you, this makes much more sense and it's a classic issue Matt Levine's readers will be familiar with. Allegedly being investigated is also quite far from "been manipulating markets", I appreciate the clarification.
23.
by thehappyfellow 1y ago
source?
24.
by thehappyfellow 1y ago
You’re right, there are downsides like turbine you mention! We mitigate it by running a hot backup we can switch to in seconds and a box in which we test restoring backups every 24h, that’s necessary! But it requires 3x the number of big ex
25.
by thehappyfellow 1y ago
It’s incredible how much Postgres can handle. At $WORK, we write ~100M rows per day and keep years of history, all in a single database. Sure, the box is big, but I have beautiful transactional workloads and no distributed systems to worry
26.
by thehappyfellow 1y ago
It really makes me happy to know that my writing struck a chord for at least one person - thank you!
27.
by thehappyfellow 1y ago
Yeah, I was angry when I was writing it, not denying it.
28.
by thehappyfellow 1y ago
Author here. I did not expect to see my post on HN! It was a rant, I was venting, it’s not supposed to be an objective statement about the state of tech. It’s shouting into the void about the things I find unfair and unbearable, I don’t thi
29.
by thehappyfellow 1y ago
Hah, thanks! I really wanted an optimisation rabbit hole and seems like this projective going to deliver on that :) I also tweet about the progress on @onehappyfellow if you’re interested
30.
by thehappyfellow 1y ago
Learning Rust by building a simple database using it. I’ve done my share of programming languages (PHP, C++, Python, Ruby, Haskell) and for the last 10 years I’ve been working in OCaml (which I love so much ) but Rust would be a nice addit

More ›