Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
BillyTheKing
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
BillyTheKing
1y ago
The reasoning might not sound crazy, but the result is that a founder based in Hong Kong, opening a holding in Singapore, and creates a subsidiary in Germany is much much better off than a founder running the same business out of Germany -
2.
▲
by
BillyTheKing
1y ago
how did you do it? My co-founder is in a similar situation, and his tax-lawyer said the only way was via a trust - they also have a German holding. Do you have to declare that somewhere? or how does this work? Thanks!
3.
▲
by
BillyTheKing
1y ago
This means the person has to move to a country with 0% income tax for this to make any economic sense, so that's either Monaco or the UAE then. Very difficult for me to understand why someone is supposed to pay this tax in the first pl
4.
▲
by
BillyTheKing
1y ago
apart from those weird file attach issues I actually think they've got a much better UI than anthropic as well - much much snappier even with extremely long chats (in addition to much higher limits obviously, totally different league).
5.
▲
by
BillyTheKing
2y ago
just a question for understanding - if we say 'it learns', does it mean it actually learns this as part of its training data? or does this mean it's stored in a vector DB and it retrieves information based on vector search an
6.
▲
by
BillyTheKing
2y ago
yes, it's a form of double-entry bookkeeping - that's the base. If it weren't double-entry then indeed it would be a pretty poor choice. This design enforces double-entry at a fundamental level, it's never possible to cr
7.
▲
by
BillyTheKing
2y ago
you simple create two records linked by one 'transaction', the source in both cases is the same account, while the destination for one of those postings is the fee account and the other destination is a merchant or similar account
8.
▲
by
BillyTheKing
2y ago
yes, agree, I think a 'source' 'destination' model is significantly more straight-forward. Just record the 'source' account and the destination account and you essentially end up with a ledger as a directed gra
9.
▲
by
BillyTheKing
2y ago
absolutely not true btw - the largest use-case for stable-coins atm are people evading capital controls in emerging markets, including China, India, Nigeria, and similar, and in many latin American countries.
10.
▲
by
BillyTheKing
2y ago
or just use bun? used to also face all these issues - but with bun it's mostly gone for now (and for newer projects) - hope it stays that way!
11.
▲
by
BillyTheKing
2y ago
Would recommend to try out anthropic sonnet 3.5 for this one - usually generates decent unit tests for reasonably sized functions
12.
▲
by
BillyTheKing
2y ago
this is the thing with JS and TS - the types and stuff, it's all good until you realise that all integers are basically int 52 (represented as float 64, with 52 bits for the fraction). Yes, it's nice and flexible - but also introd
13.
▲
by
BillyTheKing
2y ago
People just have less tolerance for errors using apple products.. that doesn't mean that other LLM companies sell snake-oil, people just have a higher error tolerance for them and are learning to work 'with' those LLMs
14.
▲
by
BillyTheKing
2y ago
Yes, all true - apart from treating errors as values and including them function signatures... That should simply be something every modern language should ship with
15.
▲
by
BillyTheKing
2y ago
shipped extra fast!
16.
▲
by
BillyTheKing
2y ago
We've been building a source/destination ledger at nxos (and I've worked with similar systems in the past). The relationship between debits and credits in such a ledger wasn't always clear to me. However, writing this po
17.
▲
Modeling Debits and Credits on a Source/Destination Ledger
(blog.nxos.io)
1 points
by
BillyTheKing
2y ago
|
1 comments
18.
▲
by
BillyTheKing
2y ago
Hey everyone! I wrote a blog post about building a simple double-entry ledger using just simple SQL. It covers implementing a ledger with source and destination accounts, using a simple table structure and straight-forward SQL queries for b
19.
▲
A simple double-entry ledger with source and destination accounts in SQL
(blog.nxos.io)
6 points
by
BillyTheKing
2y ago
|
1 comments
20.
▲
by
BillyTheKing
2y ago
maybe that's really where the business here is.. working through a whole bunch of custom data-sets and trying to generalise from there. It'll be hard to generalise all of it, but I'm sure there'll be pockets of functiona
21.
▲
by
BillyTheKing
2y ago
and once again - another year with a great iPad Hardware wise but essentially unusable for coding tasks software wise.. Would love a reason to buy one and use as a travel coding machine but without local support it remains a non-starter
22.
▲
by
BillyTheKing
2y ago
GraphQL basically only really works with monoliths that share the same access-pattern (either everyone logged in, or everyone logged out), it's otherwise a pain to merge multiple different graphql-schemas into a single one (or at least
23.
▲
by
BillyTheKing
2y ago
I can spend more times at my friend's place, maybe have a beer or two without having to worry about driving back - so I think it encourages socialisation
24.
▲
by
BillyTheKing
2y ago
yes - and writing code also doesn't solve a technical problem, a computer runs fine with 0s and 1s, no need for code, in fact code produces a performance overhead - but it solves a human abilities problem, namely that 0s and 1s aren&#x
25.
▲
by
BillyTheKing
2y ago
for Fintechs who're using Stripe as a way to allow users to purchase stock/remittances/e-wallet balances etc. instant payouts are very important since in most cases people who load with stripe also consume those funds on the
26.
▲
by
BillyTheKing
2y ago
what's wrong with Remix's fundamental architecture? I mean.. I generally also think that the overall state of the JS ecosystem is broken, but that's due to JS tooling modules vs commonJS etc (hope bun fixes all that). But as
27.
▲
by
BillyTheKing
2y ago
exactly.. yes, I understand why ? is neat from a type POV since you specifically have to unwrap an optional type whereas in Go you can ignore a returned error (although linters catch that) - so at the end of the day it's just the same
28.
▲
by
BillyTheKing
2y ago
I agree, I don't really understand everyone's issue with err != nil.. it's explicit, and linters catch uncaught errors. Yes the ? operator in Rust is neat, but you end up with a similar issue of just matching errors throughou
29.
▲
by
BillyTheKing
2y ago
yes, the whole world runs on nestjs
30.
▲
by
BillyTheKing
2y ago
for internally consumed APIs I somewhat agree, but if you wanna expose APIs to external developers it usually does pay off to spend a bit of time on the API design itself, what APIs would you expect to see if you were the user of the your o
More ›