HN user

esikich

196 karma
Posts0
Comments124
View on HN
No posts found.

Is this what you do? Because I'm at least an intermediate with astrophotography with a camera, and even airplanes are a total non issue. If you're so deep into the sky that you actually need many minutes or hours on the same spot, the teeny tiny time that satellite is there is a non issue and easy to remove with math.

That's what I don't understand, how are they ruined? If you're so deep that you need minutes or hours of exposures, that satellite will blip past the frame so fast it's not going to matter. And if the exposure time is less than that, you stack.

My grandpa used to say "we're not building a piano" when doing things like building a quick shelf or something in the basement and be done after a quick measure and a few cuts. My other grandpa would spend an entire day measuring, sanding, pulling out a router etc. Both valid, but if you just need something to put some paint cans on, it doesn't require a day of work.

This is a demo. It's like taking the first shitty picture or making the first shit sounding "analog electronic instrument" played by the guy who doesn't know how to play music but is an electronic savant. It's the concept that matters, not this specific execution of it.

If you're talking consumer, there are a plethora of solutions already that are much simpler. If you're talking enterprise, there's no way the cost will make sense for TBs of data as enterprise backup solutions have existed since forever.

As a sysadmin I'm in the same boat. I've unfortunately never worked with security folks that seemed to have any sysadmin or dev experience. Whether or not this is universal, idk, and I have no idea what they are teaching in these security courses. But I'm tired of security teams telling me "you need to implement these 230 group policies this quarter" or whatever. They don't seem to grasp the externalities of a request like that and how much fucking work it is to vet, test, deploy, monitor, verify, etc. 80% of the time, they don't even know what they do or if it's even impactful for us.

If you're trying to get it to write it in your voice, just dump some stuff you've written into the context. You need to think about other voices and be able to describe what makes yours different as well.

Use examples and learn about writing. If you're not a good writer, or at least have a passing interest, I'm not sure why anyone would expect it to nail their style any more than you would expect it to architect software in something you're not familiar with.

Give it some paragraphs of writing you like, authors, writers, whatever. Also don't expect to one shot long papers. Have it write out a table of contents and write it in small chunks.

Typical things I'll say is avoid purple prose, avoid common cliches and tropes, "show don't tell", avoid wild metaphors and similes, etc. But it all depends on what you like. Look at things you do like and try to think about what it is about that writing that is different than a middle schooler or an AI writing it. Theres no formula for it.

It's absolutely fair unless you believe in magic. "Make it sound like a human and not AI" is never going to get you good results just due to information theory. You're not giving it enough to work with or what the hell that even means.

He's 72 years old, I'm sure he has the best brains and everyone's best interests in mind. This is exactly what I want to see. I'm sure he will have very good opinions on technology and it's implications.