Love the constraint you gave yourself with the zero asset files. Would love to see how you went about doing that.

Amusingly our insurance's captive/preferred pharmacy wants to mail us the generic for $40 + 25 S+H instead of us buying it locally for $150. Except that they can't climate control the shipment and it's 20F over the rated temp of the inhaler here today, in the shade. So their in house pharmacist allowed an override.

Still a royal PITA.

I'm coming to modern software development late. My experience was in things which were in the mini-computer and COBOL genre of machines, or on things that were so tightly controlled that the review process for one change could take a year (combat aircraft and drones).

So CI/CD is something I'm actually trying to grasp because it feels so alien to me.

All that to say: Don't currently have any.

Cofounder is using agents, I'm directly interacting with Claude and Codex. Self hosted forgejo due to Github issues.

I'm trying my hand at a startup right now, just to see if I can make a go of it.

My son was diagnosed with cancer at 3, then during chemo it became abundantly clear that he had far more severe autism than we originally thought. Could have been made worse by the chemo and trauma; no real way to know.

Now my wife and I have had to give up all the dreams we had for when I retired from the military. A few good moves means that I actually retired at 40, though more modestly than I planned. But we will forever be taking care of him.

So we struggle with the unlived dreams often.

The Qwen3.6-35B model has, in my testing, been decent but not nearly as good as the Qwen3.6-27B. Running that with a less quantized cache is going to be "better" for anyone using it for software dev in my limited testing.

I only have one lens tight now (I tend to stay small on my system but this is a low point) but I'll keep it in mind.

Thanks for the info!

Sigma has a dock that allows updates to their lenses in this fashion however.

Different people grasp things at different rates.

You shouldn't just have a toolbox of things you've picked up from your best examples, that you've been taught, etc. It's possibly more important to have another toolbox of broken tools from all the terrible bosses, reactions to situations you've witnessed, etc.

This way when you go to do something and it's not in your toolbox, you can pull out that box of broken/bad tools and see if it's there. Otherwise we perpetuate bad leadership (and teaching IS leadership) through intentional ignorance (forgetting the lessons those bad situations gave us).

Relative SQL neophyte building out an app and learning it from the ground up. Interested in recommendations.

https://news.ycombinator.com/item?id=31311845 has a few recommendations. Anything else to look for/at?

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

Points: 5

# Comments: 3

I can't vouch for it from any perspective except as an SQL neophyte but for me it has been teaching me a lot.

I'm by no means a senior dev, but I don't know if I fit in the box of a junior either.

Regardless, SQL is proving enjoyable. But I really like logic, so it fits.