Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
throwaway7783
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
throwaway7783
2mo ago
.. by hiring the right humans - which is not always a given
32.
▲
by
throwaway7783
2mo ago
Lots of downvotes and one condescending remark, but no knowledge shared :(
33.
▲
by
throwaway7783
2mo ago
Does anyone think here shortselling should be banned?
34.
▲
by
throwaway7783
2mo ago
Very cool! Adding a client geo would be nice (even if its not very accurate)
35.
▲
by
throwaway7783
2mo ago
No one is in denial. The parent post is just explaining why, and not that the problem doesn't exist. The biggest issue we have is the mindset of the common (wo)man, regardless of why it is the way it is.
36.
▲
by
throwaway7783
2mo ago
Right after the Islamic and British invasions
37.
▲
by
throwaway7783
2mo ago
This has been my experience as well. Something happened 2-3 months ago with Claude Code. It got slower, starting spinning and getting stuck more and more. I gave codex another shot out of my Claude frustrations, and have never looked back a
38.
▲
by
throwaway7783
2mo ago
A dirt yard is sufficient if it was to show off land. Grass is not required
39.
▲
Property Graphs in PostgreSQL
(postgresql.org)
1 points
by
throwaway7783
2mo ago
|
0 comments
40.
▲
by
throwaway7783
3mo ago
In SaaS quality is one of the problems that cause churn. Value,price and politics also play a big role - now matter how good or bad the product quality is
41.
▲
by
throwaway7783
3mo ago
Re: bad design decisions - This can be said about any technology.
42.
▲
by
throwaway7783
3mo ago
..and HA
43.
▲
by
throwaway7783
3mo ago
In most half-decent codebases, including LLM generated ones, adding new features almost never requires a refactoring in my experience. It is almost always when you are fixing bugs, improving performance or changing core behavior.
44.
▲
by
throwaway7783
3mo ago
I think we have to wait and see if long term maintainability will be any different from human coded software. Every single long surviving human written codebase I have worked with, has significant amounts of tech debt and large pieces had t
45.
▲
by
throwaway7783
3mo ago
How does this work in a production setup? Can this be set up like a server, or is it mostly for individual users to play around with data?
46.
▲
by
throwaway7783
3mo ago
This. I hate VSCode as an IDE and is the reason why I have not used Cursor. I wish Jetbrains actually had some brains to build a better coding agent inside their IDEs (which I think are one of the best out there), but for now Im stuck with
47.
▲
by
throwaway7783
3mo ago
"We only need to consult the database for the user's secret..." , which kinda defeats the purpose.
48.
▲
by
throwaway7783
3mo ago
LinkedIn doesn't have any redressal mechanisms for anything. Someone I knew went through a lot of abuse by a LI user and kept making new accounts to harass. LinkedIn's response - "We did not find anything that violates our To
49.
▲
by
throwaway7783
3mo ago
a.k.a the vaunted "Ideal Customer Profile". This is really critical for many many things in business and life.
50.
▲
by
throwaway7783
3mo ago
Can you please elaborate on the differences? They are practically interchangeable, but conceptually there might be another layer on top of entities and relationships for somewhat richer semantics (like describing a relation, or additional a
51.
▲
by
throwaway7783
3mo ago
Yeah, but now this is implicit information (no price == marker row) and duplicate the entire row. And it is baking in "price" as the special field. This may not be just one field for another temporal entity
52.
▲
by
throwaway7783
3mo ago
Works when there is always an active price. Having an explicit end date allows certain rows to be inactive automatically after validity period. Think of seasonal categories/products etc which dont exist after a specific period
53.
▲
by
throwaway7783
3mo ago
It is at the org level
54.
▲
by
throwaway7783
3mo ago
True, it is the only objective signal, but as you have observed as well, it is also a very poor one.
55.
▲
by
throwaway7783
3mo ago
I said it in another thread. Yes, of course we cannot match the local store interactivity. What I mean is coast to coast RTT is 65-80ms. And the server can be optimized to return back basic operations (adding a comment, a new ticket, readin
56.
▲
by
throwaway7783
3mo ago
Based on all the comments above, it is very debatable if it is a better product all said and done
57.
▲
by
throwaway7783
3mo ago
100% agree. A traditional CRUD app (like Linear) can be made pretty low latency without local-first. The complexity is not worth it.
58.
▲
by
throwaway7783
3mo ago
Writing an eventually consistent database is hard, it maybe fine for Linear's use cases, but not knowing if my updates made it to the server (aka my team),is problematic. The sync lags have created untold problems in other projects I h
59.
▲
by
throwaway7783
3mo ago
Even if we forget "rockstar", there are certainly different levels of engineers. More experience doesn't automatically mean better either. That is not to say experience doesn't matter. It matters quite a bit. Sure , good
60.
▲
by
throwaway7783
3mo ago
Sure, but the context here is only about code.
More ›