I hate my HP inkjet printer with a passion. Feels like the ink lasts less than 100 pages of light printing. And the ink is expensive.

I was under the impression that Brother was a good brand, but it seems they are also following the HP playbook.

What printer do you actually use? Would you recommend it for regular home printing (mostly b/w, occasional color printing. Scanning, copying, etc. would be ideal)?

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

Points: 20

# Comments: 24

A question to advance the discussion. What I am wondering is, if you can remember to go back to your time tracking system, why can you not remember to go back to your main goals?

More structure/checklist to force you to focus will have other side-effects like you found out. When you get rid of the structure, you still need to have a rough map in your mind of where you want to go.

To me, this is similar to being honest. You don't want to depend on a system or checklist for being honest. It is something you always need, as a policy. Focus is like that. If you want to focus seriously on something, just make it a policy, and don't use all these tricks as crutches.

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

Points: 1

# Comments: 1

- More "sub-reddits". We already have Ask/Show HN. We probably can add a couple more to keep everything organized.

- Option to auto-collapse comments threads deeper than X levels by default. When they are all open by default like today, only the top comment and its children get more of the eyeballs.

2025: Stopped writing so much Java, so used VSCode exclusively for Python, TS etc, with Claude Code or Cline.

2026: Time is split between Codex App (40%), Claude App (30%) and VSCode with Claude Code (30%).

Some other thoughts:

* Overall I feel like opening an IDE in the traditional sense is coming to an end.

* Tech-stack wise I am much more open to trying out new things than before since LLMs will help with the setup and debugging.

* For small teams like ours, code reviews are the bottleneck, and we constantly have to decide what code we review vs what we don't.

* Building seems easy these days, but (1) so much competition no in every field, (2) much more product polish is expected than before, and (3) most products compete with Claude if they realize this or not.

Our thesis is that a lot of Data Engineering practiced today is non-differentiated across companies and they'd rather spend that time on differentiated tasks. What if we can abstract away a lot of the tedious parts of DE work and let companies focus on just the data they want to store, and the questions they have on their data?

So today, we have an MVP that manages the compute, storage, lineage, versioning and pipeline building for datasets. Would LOVE to get feedback on this or your early thoughts!

I don't have a midi piano. Wondering if it is easy for you to support my inputs using microphone. I think there will be several noobs like me with the same problem.

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

Points: 3

# Comments: 0

As others have mentioned, adding account integrations will make this much easier to use.

I would also love to hear more of your story, and motivations around this project.

Feature request: Please create an apple TV app for this. I'd love my kids to play this on the TV together. I'd pay for this.

EXACTLY what was missing in many tools, and exactly what is required for reducing the time from quick prototype to production quality code.

Congrats on the launch. Looking forward to trying this out. Please add support for AWS Bedrock based models.

Given YC asks founders to apply for a batch just a few weeks (or months) before each batch starts, I am wondering if you run into issues with timing. Do you see issues with visa delays etc, that can cause founders to miss their batch?

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

Points: 4

# Comments: 0

Here is what I am struggling with: I am not able to grasp the programming model with Hooks. I am not able to read the code easily, nor am I able to easily understand the interactions in the app. "easily" being the keyword here. I can understand what is happening if I put in the effort, but every time, it is a struggle. I switch between languages and platforms all the time, but react code is where I have to take a real pause to understand what is going on.

My suspicion is that this has to do mostly with the names of the Hooks, and how they are used in the code.

* Why are they named useState, useEffect etc? Are there better names if used will make it easier for me to read this code? Are there any other systems/languages (even in JS) where similar constructs are present? What are their names?

* If JSX is anyway getting compiled to JS, why do I have to still deal with strange looking useState and useEffect declarations? Is there a way to get cleaner syntax and make React code read like regular code?

This is mostly a cry for help, and not a criticism of React. I have used React in the past (several years ago, before Hooks) and I used to "get" React.