Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
_acco
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
AWS us-west-2 connectivity issues affecting multiple services
(health.aws.amazon.com)
19 points
by
_acco
2mo ago
|
1 comments
2.
▲
by
_acco
9mo ago
So cool. Would love to hear more - What app do you use? How often do you clear your inbox and how long does it take?
3.
▲
by
_acco
9mo ago
My best guess for the sparse icons in older MacOS versions: icons only for frequently-used menu items.
4.
▲
by
_acco
11mo ago
I disagree. I started with Elixir and its OTP resources are really good. Books like Elixir in Action do a great job. I read Programming Erlang later, but it was just for fun, and I knew most things already at that point.
5.
▲
by
_acco
1y ago
False, payroll taxes are split. And Texas is famous for its property taxes.
6.
▲
by
_acco
1y ago
You think they don’t pay payroll tax, sales tax, or property tax? Operating a business means consuming and producing things, which involves paying taxes.
7.
▲
by
_acco
1y ago
Clickbait title. First, this is narrowly about federal income tax. SpaceX presumably pays plenty of other taxes. Second, using the projected profits in the article, SpaceX will have exhausted its NOL pool by the end of this year, and so wil
8.
▲
by
_acco
1y ago
I consider myself expert-level at Elixir and did not learn Erlang first. Couldn't write a single line of Erlang today unaided if I tried. I picked up Joe's Erlang book years after out of pure joy/curiosity. Especially with LL
9.
▲
by
_acco
1y ago
It doesn't matter as much as you think. I believe this is in part due to how assertive most Elixir code tends to be. [1] These assertions not only aid the LSP and can cause compiler warnings/errors, they also help LLMs just like t
10.
▲
by
_acco
1y ago
This is a good way of framing that we don't understand human creativity. And that we can't hope to build it until we do. i.e. AGI is a philosophical problem, not a scaling problem. Though we understand them little, we know the def
11.
▲
by
_acco
1y ago
Your unique advantage is you know Vitess super well. Your unique disadvantage is you know Vitess super well! Second system syndrome is real. Using as much Vitess as possible could help you guard against it. Excited to follow your progress :
12.
▲
by
_acco
1y ago
This is so cool. A key benefit is that it's not embedding the C Lua runtime and compiler, but rather implements Lua in the host language (Elixir/Erlang). When sandboxing user code in another runtime, you need to serialize the data
13.
▲
We Built Mini-Elixir
(blog.sequinstream.com)
6 points
by
_acco
1y ago
|
0 comments
14.
▲
Building a fast sandbox for user code
(blog.sequinstream.com)
3 points
by
_acco
1y ago
|
0 comments
15.
▲
by
_acco
1y ago
Why do we use hotkeys and snippets? There is a lot of tedium in software development and these tools help alleviate it.
16.
▲
by
_acco
2y ago
Sequin | Platform Engineer | San Francisco | ONSITE We're building the world's fastest change data capture (CDC) platform for Postgres. CDC is a proven pattern that enables real-time use cases like triggering side effects, fanning
17.
▲
by
_acco
2y ago
Sequin engineer here. We'll publish our benchmark repo soon! Indeed, we're still doing a lot of fiddling with Debezium ourselves to make sure we cover different configurations, deployments, etc. The main thing we want to communica
18.
▲
by
_acco
2y ago
Sequin | Platform Engineer | San Francisco | ONSITE We're building the world's fastest change data capture (CDC) platform for Postgres. CDC is a proven pattern that enables real-time use cases like triggering side effects, fanning
19.
▲
Using watermarks to coordinate change data capture in Postgres
(blog.sequinstream.com)
1 points
by
_acco
2y ago
|
0 comments
20.
▲
by
_acco
2y ago
AFAIK, the reason for these changes is basically "prevent AWS from eating our business". Is that right? If so, are these trends harmful to open source? Are we not choosing between: 1. A world where all revenue in OSS infrastructur
21.
▲
We fixed our documentation with the Diátaxis framework
(blog.sequinstream.com)
61 points
by
_acco
2y ago
|
15 comments
22.
▲
by
_acco
2y ago
Very fun – I wasn't aware, thank you!
23.
▲
by
_acco
2y ago
Aye, thanks! That's very helpful to hear. I just cut back our use of the acronym a ton: https://github.com/sequinstream/sequin/commit/28bfba603da6d2...
24.
▲
by
_acco
2y ago
We just applied this framework to the Sequin [1] docs two weeks ago. It has felt so nice to have a framework. I think our docs flow really well now, and it's been easier for us to add and maintain docs because we know where to put
25.
▲
Time-based retention strategies in Postgres
(blog.sequinstream.com)
1 points
by
_acco
2y ago
|
0 comments
26.
▲
Request-Reply in Postgres
(blog.sequinstream.com)
2 points
by
_acco
2y ago
|
0 comments
27.
▲
by
_acco
2y ago
Aye, good catch! Honest mistake. Fixed.
28.
▲
by
_acco
2y ago
That 2011 snapshot actually makes the opposite point: the WordPress logo is prominently displayed next to the "WP Engine" title on the screenshot! It does look like they fixed just a few months later, though: https://we
29.
▲
Patterns for forms in LiveView and LiveSvelte
(blog.sequinstream.com)
3 points
by
_acco
2y ago
|
0 comments
30.
▲
by
_acco
2y ago
Stoked you watched, thanks. (Sorry the example isn't the greatest/lacks context. The first video was better, but the mic gain was too high.) You summed up the workflow accurately. Except, I read your first paragraph in a positive
More ›