Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fizlebit
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
fizlebit
2y ago
:) yes. I saw that error and wondered whether someone would point it out. I think the author fails to acknowledge that the use of variables like "verb" just make the code much harder to understand than a string that reads mostly l
32.
▲
by
fizlebit
2y ago
I think people already knew how to write good quality code even in the 80s, e.g. https://www.amazon.com/Large-Scale-Software-Design-John-Lako...
33.
▲
by
fizlebit
2y ago
The post is right in that the example code is terrible, Uncle Bob's changes make it much worse, but also the suggested fix is also bad. I think this is better, but the whole thing is silly. Obviously you'd want to write a comment
34.
▲
by
fizlebit
2y ago
How many other classes of such bugs exist. Without a public COE one can't know that it was systemically fixed. One can't know whether security boundaries were by-passed by the bug. One can't know what sorts of extra protectio
35.
▲
by
fizlebit
2y ago
Somewhere in Australia (with Australian accents): "Hey terraform just output a wall of text, it wants to know whether or not to proceed." "That's what it does mate. Let it do its thing, she'll be right."
36.
▲
by
fizlebit
2y ago
Even if it was operator error some sort of public COE would help others avoid the pitfall by design, e.g. restricting the permissions of terraform so that it can only affect resources for the system and availability zone (or better still ce
37.
▲
by
fizlebit
2y ago
I don't understand how this isn't a bigger deal. No public COE (correction of errors) for what happened on the google side? Without a public COE from Google I don't understand how anyone could use GCE for a serious production
38.
▲
by
fizlebit
3y ago
What are the chances this is the first such attack, not just the first one discovered. Presumably every library or service running as root is open to attack and maybe also some running in userspace. The attack surface is massive. Time for b
39.
▲
by
fizlebit
3y ago
I like the idea of smalltalk, but it suffers from a modularity problem. As I understand it classes just use other classes in the image and it is very difficult to track dependencies. It is a topic revisited often in the Pharo community. Str