Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
anton_gogolev
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
by
anton_gogolev
3mo ago
Care to elaborate on what would make C# a bad language?
2.
▲
by
anton_gogolev
4mo ago
I remember being mocked slightly when I was headbangin' and footstompin' to the soundtrack.
3.
▲
by
anton_gogolev
6y ago
That’s not called “deleting old code”. This is now “breaking backwards compatibility”.
4.
▲
by
anton_gogolev
7y ago
So you're not welcoming guests with Android phones? Will you be placing their mobile phones in a Faraday cage? Or will not not be visiting anyone who has a Homepod/Echo at home?
5.
▲
by
anton_gogolev
7y ago
> The Law of Leaky Abstractions is a lie; abstract airtightly This one... Our entire computing world is a pie of terrible abstractions held together by duct-tape and billions of man-hours spent working fixing those leaks.
6.
▲
by
anton_gogolev
7y ago
> ...the better your code style, guidelines, linting, infrastructure, error reporting and tests Doesn't TypeScript kind of solves (at least partially) those issues?
7.
▲
by
anton_gogolev
7y ago
Keeping track is one thing. Actually _running_ the Lernaean Hydra of an application in production is a whole another story. The amount of "housekeeping" you have to do to keep the thing afloat is astounding: cascading failures, di
8.
▲
by
anton_gogolev
7y ago
You can experience the same, if not worse, levels of pain and suffering with a monolithic application designed by the same Enterprise Architects.
9.
▲
by
anton_gogolev
7y ago
This is some Java-level explicitness. Maybe, drop the `_seconds` suffix and replace it with something like `retry_window_after_first_call = '60s'`?
10.
▲
by
anton_gogolev
7y ago
Not to undermine author’s efforts, but I feel we as an industry took a wrong turn somewhere. An entire book on what essentially is a single Git command is just insane.
11.
▲
by
anton_gogolev
7y ago
> ...weird design choices (e.g. branching is bad) What bothers you in particular?
12.
▲
by
anton_gogolev
7y ago
> There's nothing wrong with having zillions of them... There's nothing wrong until something goes wrong an now you're royally screwed. With zillion dependencies you are at a mercy of zillion maintainers, and none of them
13.
▲
by
anton_gogolev
7y ago
The whole "...we don’t want duplicated subscriber lists" is a very arbitrary requirement. What's more, all this could have been avoided if a proper relational database structure (not even denormalized, GordonS) was there in t
14.
▲
by
anton_gogolev
8y ago
I've been using HJSON lately and it's been a joy.
15.
▲
by
anton_gogolev
8y ago
The patented "Shlemiel the painter’s algorithm" [1]. 1: https://www.joelonsoftware.com/2001/12/11/back-to-basics/
16.
▲
Microsoft Azure (North Europe) has been down for 4 hours
(azure.microsoft.com)
11 points
by
anton_gogolev
8y ago
|
0 comments
17.
▲
by
anton_gogolev
8y ago
How could foreign keys ever be a "hassle"?
18.
▲
by
anton_gogolev
9y ago
The legalese is astonishing: ...in consideration of the foregoing and the mutual covenants and agreements herein contained, and intending to be legally bound hereby, Parent, Merger Sub and the Company hereby agree as follows...
19.
▲
by
anton_gogolev
9y ago
If by "designed" you mean "picking a content-addressable DAG as an underlying data structure", then yes, it is really beautiful. If you mean "provide a sane level of abstraction over said data structure", then
20.
▲
by
anton_gogolev
9y ago
And nothing from Apple yet, right? Apparently, engineers are hard at work releasing a fix, so there should be known workarounds. Or at least it’s known to them what is actually causing the issue. Instead, we have hordes of people resetting
21.
▲
by
anton_gogolev
9y ago
NewHash is a terrible name - on par with Xbox One [X] and iPad New. Googling stuff will be hard, and good luck explaining to less technical-savvy users what is this all about. Plus, in 100 years, when SHA-256 is compromised, what would be t
22.
▲
by
anton_gogolev
9y ago
Check out http://www.craftinginterpreters.com for something more in-depth.
23.
▲
by
anton_gogolev
9y ago
Where are all the unit/integration tests for the APIs that this damned button is calling? Hindsight being 20/20, but I cannot imagine not asserting that a newly created/re-enabled root user has a non-empty password.
24.
▲
by
anton_gogolev
9y ago
Immediately after you are tasked to maintain said overly-clever and overly-terse code.
25.
▲
by
anton_gogolev
9y ago
> ...every single quote... And then you come across \u0027 and you're screwed.
26.
▲
by
anton_gogolev
9y ago
With that central place being?
27.
▲
by
anton_gogolev
9y ago
You can never properly escape user input, so this escape_literal() is a ticking timebomb.
28.
▲
by
anton_gogolev
9y ago
Well, "companies" is a string, isnt't it? Ultimately, there will be strings down there. Working with pure AST is a huge pain. One can trivially construct something that can not realistically be represented in an SQL dialect o
29.
▲
by
anton_gogolev
9y ago
I highly doubt that placeholders are interpolated into the SQL statement. Doing so will defeat the purpose of having them in the first place. Rather, they are tranferred out-of-band to the SQL "engine", as it were, and are used as
30.
▲
by
anton_gogolev
9y ago
Absolutely: https://www.postgresql.org/docs/8.3/static/indexes-bitmap-sc...
More ›