Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ram_rar
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
1.
▲
SecIT Bench A frontier benchmark for AI agents in IT and security workflows
(secitbench.cribl.io)
3 points
by
ram_rar
29d ago
|
0 comments
2.
▲
by
ram_rar
8mo ago
This advice only works at the team level. Beyond that, it’s borderline fantasy. At senior and leadership levels, promotions aren’t rewards for effort, they’re forward looking bets made by people above you, and those people have incentives,
3.
▲
by
ram_rar
11mo ago
I’ve spent a decent chunk of my career wrestling with time sync — NTP/PTP, GPS, timezones, all that fun stuff. For real world network time infrastructure, where do we actually hit diminishing returns with clock precision? Like, at what
4.
▲
by
ram_rar
1y ago
The article makes a fair case for sticking with OTel, but it also feels a bit like forcing a general purpose tool into a domain where richer semantics might genuinely help. “Just add attributes” sounds neat until you’re debugging a multi-ag
5.
▲
by
ram_rar
1y ago
I bought into the “leader vs. manager” Kool-Aid for years—until I actually had to manage. Spoiler: the dichotomy is a myth. Once you’re in the seat, it’s all gray area. You’re not just “inspiring people,” you’re stuck between upper leadersh
6.
▲
by
ram_rar
1y ago
Out of curiosity, what's keeping you in slack ecosystem? Why not leverage Discord and run on your own server? Wouldn't that be a much economical alternative to begin with?
7.
▲
by
ram_rar
1y ago
Is this deeply coupled with Chroma or something we can fork out for other applications? I would love to explore this for lightweight change data capture on S3.
8.
▲
by
ram_rar
1y ago
I’m a bit underwhelmed by the quality of articles coming out of Netflix. 100 Million records / entity is nothing for Redis — even without RAW hollow-style compression techniques used (bit-packing, dedup, dict encoding is pretty standar
9.
▲
by
ram_rar
1y ago
Unpopular opinion: in 2025, nobody should be reaching for an ORM first. They’re an anti-pattern at this point. The “abstraction” it promises rarely delivers—what you actually get is leaky, slow, and a nightmare to operate at scale. The sane
10.
▲
by
ram_rar
1y ago
I have a ton of respect for José Valim and the Elixir core team, I have to say: Elixir just doesn’t mesh well with the kind of infrastructure tooling that’s become standard today. The ecosystem has been growing impressively and there’s a lo
11.
▲
by
ram_rar
1y ago
As a non-native English speaker, I’ve often struggled to communicate nuance or subtlety in writing—especially when addressing non-technical audiences. LLMs have been a game-changer for me. They’ve significantly improved my writing and made
12.
▲
by
ram_rar
1y ago
Can someone help me understand how many companies are generally needed for healthy competition, as opposed to a market being considered fragmented or monopolistic? To the untrained eye, having 5 players might seem like a reasonable level of
13.
▲
by
ram_rar
1y ago
I'm curious what led to the lack of demand for this—was it the friction involved in moving brokerage accounts, or do ETFs already meet the needs of most retail investors? A post-mortem on the limited traction would be quite insightful.
14.
▲
by
ram_rar
1y ago
What uses cases would this be effective compared to using replacing merge tree (RMT) in clickhouse that eventually (usually in a short period of time) can handle dups itself? We had issues with dups that we solved using RMT and query time
15.
▲
by
ram_rar
1y ago
Great to see Elixir gaining traction in mission-critical broadcast systems! I wonder, how much of Cyanview's reliability comes from Elixir specifically versus just good implementation of MQTT? and is there any specific Elixir features
16.
▲
by
ram_rar
1y ago
All jobs converge to sales at some point.
17.
▲
by
ram_rar
2y ago
While dollar cost averaging and index investing are solid strategies, this article overlooks an important consideration: the Realistic Rate of Return (RoR) needed for retirement planning. Yes, US markets historically recover (lately that no
18.
▲
by
ram_rar
2y ago
Kudo to author and Cpython team to reckon this. Nevertheless, its still a very important improvement in +Ve direction. Thats all matters. This a great story as to why benchmarking are soo hard to get right. I always tell my team to benchmar
19.
▲
by
ram_rar
2y ago
Starting today in what scenario would RoR would be a better option than Next.js for building web app? Assuming one has to start from 0 -> 1 .
20.
▲
by
ram_rar
2y ago
>The other reason is that you cannot split up a large established codebase without first understanding it. I have seen large codebases successfully split up, but I have never seen that done by a team that wasn’t already fluent at shippin
21.
▲
by
ram_rar
2y ago
As much as I love to use your product, the challenge from my perspective is why switch for 0.03% in fees? Especially when you compare it to likes of fidelity, vanguard , schwab. Those 3 are too big to fail. The point I am accentuating is, t
22.
▲
by
ram_rar
2y ago
https://archive.md/1SA7c
23.
▲
by
ram_rar
2y ago
While cell-based services make sense for critical applications, not all services require this approach from a Cost of Goods Sold (COGS) perspective. In practice, I've observed that companies often adopt an all-or-nothing approach to ce
24.
▲
by
ram_rar
2y ago
> The reality was that these tools were unmaintainable by the rest of the company. Only the author "knew" Rust and it was hard to justify a new hire Rust developer to maintain this small set of tools. Only If I had a dollar for
25.
▲
by
ram_rar
2y ago
A limited job market, considerably smaller ecosystem (compared to java/python), and lack of support from major tech corporations (unlike Go or Rust) makes it challenging to adopt Elixir. At my company , we inherited a legacy Elixir ser
26.
▲
by
ram_rar
2y ago
Kudos to htmx for their refreshingly honest blog post! I hope many other open-source tools especially Databases can do similar things. >> while it’s important to consider lightweight alternatives, it’s equally crucial to choose techn
27.
▲
by
ram_rar
2y ago
I appreciated the paper's effort to highlight data analysis techniques, but I was hoping for a more forward-thinking perspective. The inclusion of pipe syntax or data processing using pipe-structured data flow syntax is not very novel
28.
▲
by
ram_rar
2y ago
Articles like these need TL;DR Testing in prod is a tale as old as time. It would have been more insightful to cover the underlying infra/tech that enables this seamlessly.
29.
▲
by
ram_rar
2y ago
Can someone with a background in contract negotiation, vendor onboarding, and business continuity risk management share their expertise? We'd love to hear about typical vendor contract provisions that protect customers in situations li
30.
▲
by
ram_rar
2y ago
> after really grokking topological sort I used it countless times for fairly mundane problems like creating plots. I'm interested in learning more - in what scenario was topological sorting essential for generating plots, and what
More ›