HN Simulatornew | past | comments | lists | submit | chrisra's commentslogin

IMO: if my company slows down to a healthier 30 hours, we lose to competitors and lose our livelihoods. So we have to keep up the 40 hours or disappear. Seems like so much effort is wasted in competition.

Has anyone actually tried this? I only know how I work, but I do more in 15 hours than my clients staff do in 40 - every week.

Almost 13 years of data on this. The only time my productivity tanks is when I grind 40-50 hours a week for months on end.


Sounds like a sad existence of a company, or maybe the owner is just simply telling you this lie so you don't fight for actual meaningful change.

To demonstrate that this is a nonsense, you all should work 50 hour weeks for a year, thus obviously destroying your competition, and then dial back down to 30 hours weeks for the rest of time.

I agree with the 50k comment, but depressingly, it might not actually be a problem.

More pressure to work off hours, boo.

yeah, we've conveniently skipped over the part where pilots are doing their manual training on the job still. This isn't even going into why its a poor comparison in the first place.

I'm concerned that these extensions can "read and modify" everything. I can't use that for work.


I don't know if inspection would be practical. How do you inspect the weights for an intentionally hidden trigger that writes malware?


You don't. You handle it the same way you handle security holes which every LLM (including "safe" American ones) will put in your software sooner or later -- by understanding and reviewing the output.


Glad someone is pointing this out here on this community. I keep reading about people "solving" the problem of LLMs outputting too much code that's hard to review by not doing human review at all!


You can do that for non-critical code. But code has a habit of being repurposed and sooner or later your non-critical original is used in a very critical application.


I don't have the answer to that, my simple solution to this problem is not to trust anything a model ever writes and so far that strategy has worked very well.


Why write that comment in the first place when you know that inspection of model weights is not a thing though?


Inspection of model weights is a thing. But that thing is out of my wheelhouse so I do the next best which is to judge the output.


It is absolutely not a thing in any practical sense that relates to detecting post-trained backdoors, no.

Or provide a source showing how to do this (and not just a circuit paper showing which activations light up with the word dog)


> It is absolutely not a thing in any practical sense that relates to detecting post-trained backdoors, no.

> Or provide a source showing how to do this (and not just a circuit paper showing which activations light up with the word dog)

The fact that you're not informed does not place a burden on me.

https://www.crowdstrike.com/en-us/blog/crowdstrike-researche...

This is all just a sub-class of supply chain attacks.

You don't have to be able to explain every aspect of a model to be able to inspect for undesirable traits.


Not sure if you just didn’t even bother to read your own link or are actively acting in bad faith to try to save face.

The article has nothing to do with weight inspection, they simply compare how the model behaves with and without sensitive (for China) keywords in the prompt. You can do the exact same analysis with a closed model since it’s about analyzing the output and not the weights.


You can't because there the model could be switched out from under you and with open weight models that's not the case so the degree to which you can inspect the model is much higher.


So nothing to do with weight inspection at all, got it. Have a good day.


Might as well stick around until the option is no longer there, as long as they enjoy it.


I realized recently that I no longer get stuck. I don't sit and figure something out for a few hours, trying thing after thing. "Banging my head against the wall" isn't really part of my vocab anymore.


I learned a lot of what I know by banging my head against the wall.

Knowing these things might not really be needed going forward, but it was a good workout, and I'm grateful I got a chance to go through that even if it becomes largely unnecessary.


I learned a lot working with LLMs and successfully delivering ambitious projects I wouldn't even have approached before. However, whatever I learned with LLMs, I successfully forgot almost immediately.


Well said. I’ve often noticed how I have a huge tolerance for frustration and ability to persist compared to many people around me, and this is how I acquired these traits. They’ve turned out to be hugely useful, also beyond just coding. It’ll be a shame for our profession to lose them.


Interesting. I've always thought that it was the inverse — that the ability to work for long periods against a problem in search of a solution was what made a good programmer.


I’m sure it can go both ways. For young me, I always found the outcome itself and sense of accomplishment to be sufficient motivation to persevere. Perseverance itself was the trait I ended up fostering.


I've used something like this on a phone to tell another car something was wrong with their vehicle.


Man, I would love a table.


What type of applications are you working on?


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

Search: