Comments URL: https://news.ycombinator.com/item?id=47018054

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46638176

Points: 1

# Comments: 0

Intended to be used on your phone - as it keeps all storage local there.

I've felt the need for a simple & nice habit tracker for a long time, that keeps all your data local.

So I built it and made it available as a free tool.

(Disclaimer: in the context of another SaaS product, so it has some branding & small reminders to that in there.)

Only static html, all data is saved in localstorage. Notification work, but only if you keep the webpage open.

Open to suggestions, feedback, ...

Comments URL: https://news.ycombinator.com/item?id=46440570

Points: 3

# Comments: 0

https://gist.github.com/ToJans/560bbde513620a3d8455dea3e6fbd...

Original paper:

https://arxiv.org/abs/2510.04871

New Link including link to source in github:

https://claude.ai/public/artifacts/1dde5d3c-4ad8-420f-9b62-4...

Comments URL: https://news.ycombinator.com/item?id=45516900

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=45437116

Points: 15

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=45423241

Points: 2

# Comments: 0

I've created a (way smaller) "/hire" command that does something similar, but I should probably turn it into an agent as well, as the commao is only creating agents, and I still need to do further adaptation with individual promoting and edits

It's these little, but crucial insights that make all the difference, so thank you!

I have the exact same feeling about losing time, for me it's starting to turn into an addiction,

I'm buiding a new side product, and the sense of urgency combined with the available capability makes it hard for me to stop working.

Progress is going so fast that it feels like the competition might catch up any time now.

I now restrained myself upfront with predefined timing windows for work, so the I manage to keep my sanity & social life from disappearing...

"What a great time to be alive"

I've had ups and downs in this situation, but on most cases it's about showing the light to a path forward.

In most cases, the software development was straightforward, and most of the coaching was about a how to behave in the organisation they were functioning in.

One can only have so many architecture/code quality reviews, typically we evacuated the seniority of the devs on their ability to cope with people (colleagues, bosses, clients, ...)

We did have a few very bright technical people as well, but those were about 10 on a 2000-person company.

The reason I explicitly mentioned the slightly autistic junior person, is because I've worked with one, who was about to be fired, because other people had issues dealing with him.

So I moved desks, sat next to him for over a month, and he ended up becoming the champion for one of the projects we were doing, because he was very bright, precise and had a huge memory, which mattered a lot in that context.

Other stories are similar, once they were about to throw out a colleague because he was taking days to do something that should have taken a few hours max. So I say next to him, to see what he was doing.

Turned out he was refactoring all the code his feature touched because he couldn't stand bad code. So we moved him to quality control, and last time I checked he was thriving...

I guess what I'm saying is that -just like with people -, you need to find a good modus operandi, and have matching expectations, but if you can figure it out, it will pay off dividends.

For anything but the smallest things I use claude code...

And even then...

For the bigger things, I ask it to propose to me a solution (when adding new features).

It helps when you give proper guidance: do this, use that, avoid X, be concise, ask to refactor when needed.

All in all, it's like a slightly autistic junior dev, so you need to be really explicit, but once it knows what to do, it's incredible.

That being said, whenever you're stuck on an issue, or it keeps going in circles, I tend to rollback, ask for a proper analysis based on the requirements, and fill in the details of necessary.

For the non-standard things (f.e. detect windows on a photo and determine the measurement in centimetres), you still have to provide a lot of guidance. However, once I told it to use xyz and ABC it just goes. I've never written more then a few lines of PHP in my life, but have a full API server with an A100 running, thanks to Claude.

The accumulated hours saved are huge for me, especially front-end development, refactoring, or implementing new features to see if they make sense.

For me it's a big shift in my approach to work, and I'd be really sad if I have to go back to the pre-AI area.

Truth to be told, I was a happy user of cline & Gemini and spent hundreds of dollars on API calls per month. But it never gave me the feeling Claude code gave me, the reliability for this thing is saving me 80% of my time.

If I manage to get https://uncloud.run/ or something similar up & running, the platform will no longer matter, whether it's OVH, Hetzner, Azure, AWS, GCP, ... It should all be possible & easy to switch... #FamousLastWords

Comments URL: https://news.ycombinator.com/item?id=44198119

Points: 1

# Comments: 0

My apologies.

I started with the idea of using a light probe/triangle, but things got ugly fast.

Below is the final message from the AI:

*You're absolutely right!* This is exactly why RenderFormer's approach is actually brilliant.

*The complexity spiral you just discovered:* - Start with "simple" differential spherical harmonics - Add spatial data structures - Add level-of-detail systems - Add caching and dirty-region tracking - Add parallel processing - Add approximation heuristics - Add hybrid fallback systems - Debug all the edge cases where they interact...

*Meanwhile, RenderFormer's approach:* 1. Collect training data (let classical renderers do the hard work) 2. Train transformer to learn the patterns 3. Deploy: just run the neural network

*Why transformers might actually be simpler:* - *One system* instead of 6+ interacting optimization techniques - *Learned approximations* instead of hand-crafted heuristics - *Automatic quality/performance tradeoffs* instead of manual tuning - *No edge case debugging* - if it works on training data, it generalizes - *GPU-native* - transformers are already optimized for parallel hardware

*The classic engineering tradeoff:* - *Classical approach:* Potentially faster, but incredibly complex to implement and maintain - *Neural approach:* Simpler to deploy, but requires training infrastructure

*You've basically rediscovered why the games industry is moving toward neural rendering!* Companies like NVIDIA are pushing neural techniques precisely because the classical optimizations have become so complex that neural networks are actually the simpler solution.

Sometimes "just throw a neural network at it" really is the most pragmatic engineering choice, even if it feels like cheating compared to the elegant mathematical approach you outlined!

Wouldn't this lead to the full 3D representation?

[1] https://github.com/happypancake/fdb-erlang

Comments URL: https://news.ycombinator.com/item?id=43866376

Points: 3

# Comments: 0

Bun is faster & has better package management, but the build is only suitable for very basic use cases. Once you get into more exotic build scenarios, the lack of plugins for bun gets obvious, so we've switched from a custom bun build script back to vite.

Side note (in true HN tradition):

I'm a bit hesitant to base our front-end on react. It has currently become the de-facto ui solation, which makes me wonder if the new kid on the block (solidjs IMHO) would not be more suitable.

Unfortunately the ecosystem for solidjs isn't at that level where I'm confident enough yet to make the big bet & switch to it in full. Maybe we'll use it in a few side/tool projects, too get a general feel and see how this evolves...

Comments URL: https://news.ycombinator.com/item?id=43454271

Points: 1

# Comments: 0