Viewing profile — 1saadcodes
1saadcodes
HN member- Joined
- Sat, Jul 18, 2026, 10:03 PM UTC
- HN karma
- 28
- Public activity
- 29 items
- HN profile
- View on Hacker News ↗
About 1saadcodes
Recent public activity
-
comment
Comment #49205689
Are you sure it was "your" phone before the run/s
-
comment
Comment #49205651
I dont get why they'd make this available to free users when they're probably dealing with compute constraints considering their competition with the Chinese models. Giving a more …
-
comment
Comment #49205571
Feels both unreal and dystopian. The speed at which these models are developing is very scary
-
comment
Comment #49205488
Love seeing stuff like this
-
comment
Comment #49179120
This seems like a more natural use of agents than asking them to one shot and push to prod. Give them a measurable objective, let them experiment, and judge the outcome instead of …
-
comment
Comment #49179019
I think the paper would have been stronger if it acknowledged how quickly the underlying evidence is becoming outdated. AI-assisted development in 2026 isn't just better models. Th…
-
comment
Comment #49178968
I'm liking the trend of companies are releasing smaller, focused models instead of trying to make one model do everything. A dedicated moderation model is much easier to reason abo…
-
comment
Comment #49149736
I think the article is right that developers become attached to tools because of trust. Ironically though, that's also why many people drifted away from Stack Overflow. The answers…
-
comment
Comment #49149684
[dead]
-
comment
Comment #49149604
This is just sad
-
comment
Comment #49129927
[dead]
-
comment
Comment #49129894
What's most impressive here is that that DeepSeek keeps showing how much of a performance improvement can come from post-training alone while the architecture stayed the same. It's…
-
comment
Comment #49129862
One thing I hope becomes more common after this incident is companies publishing what they would change even when the root cause wasn't their software. Anyways, I appreciate articl…
-
comment
Comment #49104495
This is a good reminder that every software revolution eventually becomes a hardware and infrastructure problem. Someone still has to build the buildings, wire them, and keep them …
-
comment
Comment #49104434
It feels like we're moving away from "bigger context is always better" toward "right-sized context". I love this not just because my wallet feels safer but because most of my codin…
-
comment
Comment #49104393
Thanks for sharing this. The personal observations were far more interesting than another discussion I read about hardware specs. I'd love to read more long-term experiences like t…
-
comment
Comment #49076894
I like the approach of building on existing standards instead of starting from scratch. That said, solving communication between users is a very different problem from replacing a …
-
comment
Comment #49076723
The irony is that Google's success was built on crawling and indexing the open web. I understand wanting to protect your product, but once you remove affordable APIs and then objec…
-
comment
Comment #49076600
[dead]
-
comment
Comment #49052936
I suspect the debate shouldn't be LLMs or no LLMs, but rather what level of human accountability is required. We've accepted compilers, static analyzers, and code generators becaus…
-
comment
Comment #49052852
I'd be interested to see whether this comes with a replacement for legitimate use cases. Removing a capability without offering an alternative tends to push developers toward even …
-
comment
Comment #49052782
I like that the conversation is moving beyond prompts, but I also hope the underlying principles stay portable. If "context engineering" becomes glued with one vendor's tooling, it…
-
comment
Comment #49029302
[dead]
-
comment
Comment #49029276
I wonder how much of this is handwriting versus simply removing distractions. A notebook doesn't have notifications, tabs, or an autocomplete constantly trying to finish your thoug…
-
comment
Comment #49029246
Cases like this are heartbreaking, but they're also a reminder that failures like this ones need to be published just as prominently as success. Gene editing is still a young field…