bvrmn

25 ms·

151.
by bvrmn 2y ago
> A 400 if you send mangled JSON, but a 200 if the request was valid but does not pass business validation rules. What about empty required field in JSON? Is it still mangled or it's already BL?
152.
by bvrmn 2y ago
It's quite unclear what's your point. HTTP APIs should have minimal status code set. Parent described it perfectly. It's simple, practical (especially from monitoring perspective) and doesn't intervenes with a service do
153.
by bvrmn 2y ago
It's ironic how js-experts could not make examples work on the article page.
154.
by bvrmn 2y ago
I fill your pain. For example bitbucket has a total garbage instead of proper markdown renderer. No TOC, no stable header links, no navigation to anchors on first page visit, no image scaling. But if you control documentation render process
155.
by bvrmn 2y ago
I did not object against ORMs. Please reread thread. I also have issues with SQLc, and please note it's Go library. Java is out of context.
156.
by bvrmn 2y ago
What's hql? If it's something related to hybernate than your comment is slightly out of context.
157.
by bvrmn 2y ago
How about "produced date"? I want to know how many preservatives a thing has.
158.
by bvrmn 2y ago
I did a quick look at GORM. And it's a way easier and safer to use for simple cases.
159.
by bvrmn 2y ago
I guess you talk from only a Go perspective where you don't know any good ORM libraries. Other languages have quite convenient ORMs. Some allows even auto migrations, creating migration SQL for your.
160.
by bvrmn 2y ago
How SQLc would solve following issue. For example I have original query: SELECT * from users where following_count > $1 and followers_count < $2; Then some refactoring later it becomes: SELECT * from users where enabled
161.
by bvrmn 2y ago
It became raw since query builders started to try to mimic SQL. Quite long ago.
162.
by bvrmn 2y ago
The issue with templates they could handle only simple cases or very specific complex static queries. Simple ones are a way easier with ORM/query builder. Highly depends from ORM though. And a big NO-NO for me templates force you to re
163.
by bvrmn 2y ago
Static templates for SQL becomes a chore to express dynamic queries. A dynamic query depends from incoming request. For example search filters should add or delete conditional expressions for a query. I have a little research[1] on dynamic
164.
by bvrmn 2y ago
Numbered parameters become fragile quite fast for even simple queries. Basically you couldn't safely use query until carefully revising a template. A template change could potentially break existing queries. It's kinda scary. If l
165.
by bvrmn 2y ago
Markdown supports TOC. Some flavors at least.
166.
by bvrmn 2y ago
> Imagine how many ideas are held back because their authors don’t have the right tools to express them. IMHO article would be much better while not exploring new ideas and use simple text and web-native controls instead of inconvenient
167.
by bvrmn 2y ago
As a retail customer who wants to by beans blindly in an unknown roastery you could safely choose kenya. Often it would have higher quality when others.
168.
by bvrmn 2y ago
By the end of 2024 Kenya is still best "safe" option to buy beans from unknown roastery. In my opinion of course.
169.
by bvrmn 2y ago
I think you missed the fact my model is equivalent to double entry as it understood by financial organisations. The only change is a direction (debit or credit) bit replaced with a sign bit. All other info including accounts to correctly tr
170.
by bvrmn 2y ago
Single entry is not easier. Every time it makes things horribly complex really fast. I don't understand your point.
171.
by bvrmn 2y ago
As I understand parent comment it assumes following transaction records: (source_account, dest_account, amount). I argue it complicates things. You talk more about how to make db data simultaneously a representation of final reports. I beli
172.
by bvrmn 2y ago
Actually it's backwards. Git gives ability to manage and navigate commit graph on quite low level using a pair of commands: checkout and reset and fulfill any wild desires. While in other VCSs it's a separate command per case. Not
173.
by bvrmn 2y ago
The funny thing with debit/credit wall: only long dead Italian merchchants knew its purpose.
174.
by bvrmn 2y ago
Source/destination seems fail on actual DB implementation. How to sum all entries for a particular account? It could be on either side. It complicates queries and could trigger unoptimal query plans.
175.
by bvrmn 2y ago
I don't understand what the difference in modeling between: Entry(account, direction, non-negative amount), direction is debit or credit. vs Entry(account, signed amount), + is debit, - is credit (for example). It's a two way mapp
176.
by bvrmn 2y ago
You transaction includes multiple entries. Your schema is multi-entry by definition :P It's funny how many commentators here confuse debit/credit with double-entry.
177.
by bvrmn 2y ago
But signed amounts (instead of debit/credit) formula is a way easier. Sum of entries of assets/liabilities accounts = Equity. Moreover assets and liabilities become one type.
178.
by bvrmn 2y ago
Thank you for an example. But I don't see how it explains why debit/credit should be used instead of simple signed amount. Like how Transaction(from, to) where `from` and `to` are Entry(account, credit|debit, unsigned amount) make
179.
by bvrmn 2y ago
> I've started caring about semantics a lot more than syntax, which is why I also haven't looked at Zig, Nim, Odin, etc: I am no longer interested in "a better C". A strange take. Zig, Nim and Odin are about fixing se
180.
by bvrmn 2y ago
It's interesting to know about what state machines you talk. From my experience most of the time it's an entity with state property with finger countable cardinality. And state is assumed to be changed directly. And it's not

More ›