Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
danieltanfh95
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
91.
▲
by
danieltanfh95
8mo ago
> overly-tight coupling, poor design, and poor planning yeah imagine if you could foresee the future five years in advance. People overestimate their ability to use type systems correctly, as shown in your reply here.
92.
▲
by
danieltanfh95
8mo ago
Hot take: Static typing is often touted as the end all be all, and all you need to do is "parse, don't validate" at the edge of your program and everything is fine and dandy. In practice, I find that staunch static typing pro
93.
▲
by
danieltanfh95
9mo ago
The most useful thing juniors can do now is use AI to rapidly get up to the speed with the new skill floor. Learn like crazy. Self learning is empowered by AI. Engineers > developers > coders.
94.
▲
by
danieltanfh95
10mo ago
Why not just let the product manager use some no-code tool? I think software engineers are having an identity disconnect from their roles as engineers vs coders. Engineering is about solving problems via tools and knowledge through constrai
95.
▲
by
danieltanfh95
10mo ago
I hate that he is right. It speaks deeply about how broken the incentives are for humanity and labour and why AI will ultimately destroy jobs, because AI won't need to deal with all the sacred rituals around politics and control and hu
96.
▲
by
danieltanfh95
10mo ago
they are 8 months old. there is no proof of 100m arr.
97.
▲
by
danieltanfh95
10mo ago
Please. Manus had a live demo in Google Expo 2025 in Singapore and they blew it. It was such bad taste. Manus had 1 marketing gimmick with the agents. That is no longer anything novel.
98.
▲
by
danieltanfh95
10mo ago
> Cynics feel smart but optimists win. survivorship bias.
99.
▲
by
danieltanfh95
10mo ago
context poisoning is a real problem that these memory providers only make worse.
100.
▲
by
danieltanfh95
11mo ago
The reason is quite straightforward. LLMs excel at mapping tasks but suck at first principles reasoning and validation. When you are working on the AI map app, you are mapping your new idea to code. When people are working with legacy code
101.
▲
by
danieltanfh95
11mo ago
https://danieltan.weblog.lol/2025/08/function-colors-represe... the core problem is that language/library authors need to provide some way to bridge between different execution contexts, like containing these
102.
▲
Unpaid Labour in Productive Capacity
(danieltan.weblog.lol)
5 points
by
danieltanfh95
11mo ago
|
1 comments
103.
▲
Why Conventional Price Theory Fails
(danieltan.weblog.lol)
2 points
by
danieltanfh95
11mo ago
|
0 comments
104.
▲
People as Foundation: The Productive Capacity Theory of Money – Part 1
(danieltan.weblog.lol)
2 points
by
danieltanfh95
11mo ago
|
0 comments
105.
▲
by
danieltanfh95
11mo ago
This would generally just discourage open software in general. Rebble is a non-profit and should not pretend to "own" any software or content. Eric didn't do things the polite way, but either way there's nothing to discu
106.
▲
by
danieltanfh95
11mo ago
> young person complains about jobs because automation, outsourcing and immigration > looks at resume > garbage formatting that only AI would love, with little substantial content beyond the sea of candidates would offer. All the t
107.
▲
by
danieltanfh95
1y ago
This isn't dismissing, this is respecting that this is a risk factor in involving Japanese contributors.
108.
▲
by
danieltanfh95
1y ago
Because given the nature and scope of the complaint, they should have disclosed prior communication. It is clear here that they probably attempted, poorly, to communicate but ultimately chose to nuke the relationship instead, claiming that
109.
▲
by
danieltanfh95
1y ago
It's funny how Japanese contributors often go nuclear whenever things don't go their way instead of communicating etc. Bugs happen. this is tech. open communication is always the way to go before escalation. we see the same phenom
110.
▲
The Longevity Trap: We're Building Cyberpunk Economics Without Trying
(danieltan.weblog.lol)
1 points
by
danieltanfh95
1y ago
|
0 comments
111.
▲
by
danieltanfh95
1y ago
It is really just BS. These are just basic DSA stuff. We deployed a real world solution by doing of all of that on our side. It's not magic. It's engineering.
112.
▲
by
danieltanfh95
1y ago
This is honestly not better than the LLM-powered double booking system where i just record in plain text, and have the LLM convert it into journal entries. the entire thing is in plain text and backed by git+remote. Recording finances is th
113.
▲
by
danieltanfh95
1y ago
No, there aren't enough "smart CS grads". I think American talent tend to overestimate their ability vs their actual skill level.
114.
▲
by
danieltanfh95
1y ago
Unless your application is relatively trivial you would always want consistent behaviour as much as possible than some random metric that is used to proxy as "performance", routing is NOT the solution.
115.
▲
by
danieltanfh95
1y ago
my comment is not about preventing crawling, its stating that with how much revenue AI is bringing (real or not), the value of crawling repeatedly >>> the cost of running these flimsy coin mining algorithms. At the very least captc
116.
▲
by
danieltanfh95
1y ago
its bad because they are mixing what was supposed to just be execution boundaries into the overall runtime engine without making it explicit how to bridge between one and another.
117.
▲
by
danieltanfh95
1y ago
clojure exists.
118.
▲
by
danieltanfh95
1y ago
this only holds through if the data to be accessed is less valuable than the computational cost. in this case, that is false and spending a few dollars to scrape data is more than worth. reducing the problem to a cost issue is bound to be s
119.
▲
by
danieltanfh95
1y ago
wtf? how is this then better than a captcha or something similar?!
120.
▲
by
danieltanfh95
1y ago
https://danieltan.weblog.lol/2025/06/agentic-ai-is-a-bubble-... We should be working to make HITL tools, not HOTL workflows where the humans are expected to just work with the final output. At some point the abstr
More ›