Hacker Newsnew | past | comments | ask | show | jobs | submit | OptionOfT's commentslogin

Also, don't buy 89 or 91 if your car doesn't require it. My previous car said: 91, at a minimum 89.

Current car says: 93, at a minimum 91. I don't have 93 here. So 91 it is.

But going the other way is just wasteful.


1 thing to know about with Immich:

It has botched slow motion uploading. It uploads an export at 30fps instead of maintaining 120/240fps.


do you mean it loses the original fps rate, or just that you can’t easily view it?

It loses the original FPS, akin to flattening a PSD to JPG.

From what I was reading immich should preserve your original media. I saw this bug report[0] but it’s not clear if it’s an app upload bug, iOS bug or maybe depends on the device??

I don’t use immich (yet) but this is the kind of stuff I worry about. I’m planning to use it in read only mode though and sync my photos using PhotoSync rather than rely on the app.

[0] https://github.com/immich-app/immich/issues/17576


So many years of work in Software and Hardware Engineering to separate instructions from data. NX bit, ASLR, prepared statements etc.

All out the door.


Do you run Docker? Because I remember having to VPN out to a client that used that range, and it caused conflicts where our docker containers couldn't reach the client side to fetch data.

Docker defaults to 172.16.0.0/16.


We chose Go as the development language. Go produces statically compiled binaries that include all dependencies. The only external deps are wireguard, nftables, nmap, etc. All easy stuff. So we have no need for Docker. We publish binaries for ARM64 and AMD64. Avoiding Docker has made it much easier to work with.

I had this happen at home. I'm not convinced it was a good idea to choose default subnets as /20.

It was pretty easy to cause myself problems with Docker compose. Eventually I run out of subnets in the 172.16 range and it happily created subnets in the 192.168. range. Some of them overlapped with subnets on my LAN.


Yes, we use Docker (or podman) but generally never rely on Docker’s internal address ranges.

Because when your code is handwritten, it's supposed to be a translation of you parsing business requirements to code.

Using AI adds a non-deterministic layer in between, and a lot of code now is there that you probably didn't need.

The prompt is helpful to figure out what is needed and what isn't.


The correct thing to do is to annotate the code and the PR with comments. You shouldn't be submitting code you don't understand in the first place. These comments will contain the reasoning in the prompts. Giving me a list of prompts would just be annoying and messy, not informative.

Also, we should not be submitting huge PRs in general. It is difficult to be thorough in such cases. Changes will be less well understood and more bugs will sneak their way into the code base.


The AI velocity comes from large PRs that no-one reviews.

I thought like you 5 months ago.

I've come to the conclusion that we won't be replaced, because a majority of our work is to split up business questions, probe, ask around for other people's knowledge, assemble, build a plan etc.

AI only knows what it knows, it doesn't go after the unknowns. It is reactionary in its nature.

Now, let's say something happens and I'm wrong: let's think about that. The AI can do stuff like that. I think when that happens the economy as we know it collapses, and we've got bigger fish to fry. I would say, if this happens, nearly all white-collar jobs are disappearing.


This is also been my cope.

By the time software engineers are fully automated, then executive assistants, accountants, business development people, marketers, administrative staff, researchers, and HR will also have been fully automated. At that point we have a revolution on our hands and not having a coding job will be the least of your worries.

(or it happens slowly enough that we have time to adjust)


This is a great question. I saw this and first thing I thought was:

Am I a part of this?

If this is a collection of stealer logs, no, but if it is Google & Facebook that have been hacked / had data leaked, then yes.

So far I've not heard anything from either, so I'm gonna assume that it didn't happen through those services until I hear otherwise.


I wish there was more customizability with regards to captures.

the move keywords captures everything. Sometimes I want a little bit more flexibility, like C++ lambdas.


This article discusses making captures more flexible: https://smallcultfollowing.com/babysteps/blog/2025/10/22/exp...

I agree it would be nice, in particular to make it easier to understand when learning the concept.


Multiline autocomplete is very disruptive. It's overly verbose, and it constantly pulls me out of my flow, because it's not what I want.

I know what I want before I type it. Having to parse the auto-completion disrupts the thought process of what I _wanted_ to write.


No, I'm tired of AI being pushed as this amazing way to make everybody go 100% faster, while being able to lay off 90% of the people.

And for some reason the CxO suite and upper management has completely drunk the cool-aid.

In the past new technology was adopted sparingly, to figure out whether the juice was worth the squeeze.

However with AI it feels like a lot of places are (trying to go|going) all in, both in their work, and integrating it into the products, regardless of whether it makes sense.

But most importantly, I think pushback is needed because if AI succeeds in the way it is currently advertised and sold, it's a lot more people than 'just' the Software Engineers that are going to lose their jobs.

Which is great for all those companies who currently have a lot less people on payroll.

But on the other hand, a lot of the money spent on these companies is discretionary spending. Guess what's the first thing to be cut when you lose your job?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: